[Desktop-packages] [Bug 2007281] Re: Quicklists / right-click on LibreOffice to see recent documents not working
I can report that: - i installed Dash to Panel, quicklists are also not working there, things seem to be even worse as now they are also not working for the file manager. So now getting quicklists (recent items) on none of the items in the Dash. I do get other items when I right click, such as currently open items + some fixed items such as Home, Computer and Wastebasket for the file manager -- 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/2007281 Title: Quicklists / right-click on LibreOffice to see recent documents not working Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Quicklists / right-clicking on a dash item to see recent documents (or other items) is not working on my install of Ubuntu, with the exception of the File Manager. Not working for Libre Office and Okular. See image. Ubuntu 22.10, Gnome 43.1 Initially reported to GNOME but they indicated this is an UBUNTU issue (https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/6398#note_1671815) --> See for more images this link. Also asked on AskUbuntu but no reply there (https://askubuntu.com/questions/1454381/no-quicklists-recent-files- on-rightclicking-dash-apps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2007281/+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 2008428] Re: xdg-desktop-portal-gnome fails to startup after upgrading to 44~beta-1
This bug was fixed in the package xdg-desktop-portal-gnome - 44~beta-1ubuntu1 --- xdg-desktop-portal-gnome (44~beta-1ubuntu1) lunar; urgency=medium * Revert commit that is incompatible with mutter 43 (LP: #2008165, #2008428) -- Jeremy Bicha Thu, 23 Feb 2023 19:50:07 -0500 ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2008428 Title: xdg-desktop-portal-gnome fails to startup after upgrading to 44~beta-1 Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Bug description: Since upgrading xdg-desktop-portal-gnome to 44~beta-1, it fails to startup (along with xdg-desktop-portal as well) - downgrading to 43.1-2 fixes the issue. As a result of this launching any GTK application seems to take ~25 seconds - I assume that GTK or some such is trying to contact the portal backend over dbus and then eventually timing out. Relevant excerpts from journalctl: [amurray:~] 3 $ systemctl status --user xdg-desktop-portal-gnome.service × xdg-desktop-portal-gnome.service - Portal service (GNOME implementation) Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gnome.service; static) Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 57s ago Process: 52457 ExecStart=/usr/libexec/xdg-desktop-portal-gnome (code=killed, signal=TERM) Main PID: 52457 (code=killed, signal=TERM) CPU: 11ms Feb 24 09:37:33 graphene systemd[7592]: Starting Portal service (GNOME implementation)... Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal-gnome.service: start operation timed out. Terminating. Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal-gnome.service: Failed with result 'timeout'. Feb 24 09:39:03 graphene systemd[7592]: Failed to start Portal service (GNOME implementation). [amurray:~] 1 $ systemctl status --user xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 53s ago Process: 52453 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 52453 (code=killed, signal=TERM) CPU: 15ms Feb 24 09:37:33 graphene systemd[7592]: Starting Portal service... Feb 24 09:38:23 graphene xdg-desktop-por[52453]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached Feb 24 09:38:48 graphene xdg-desktop-por[52453]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached Feb 24 09:38:48 graphene xdg-desktop-por[52453]: No skeleton to export Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal.service: start operation timed out. Terminating. Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal.service: Failed with result 'timeout'. Feb 24 09:39:03 graphene systemd[7592]: Failed to start Portal service. [amurray:~] $ systemctl status --user xdg-desktop-portal-gtk.service ○ xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation) Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gtk.service; static) Active: inactive (dead) Feb 24 09:36:22 graphene systemd[7592]: Starting Portal service (GTK/GNOME implementation)... Feb 24 09:36:22 graphene systemd[7592]: Started Portal service (GTK/GNOME implementation). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 09:36:16 2023 InstallationDate: Installed on 2021-08-03 (569 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-01-27 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2008428/+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 2008165] Re: GTK apps take ~25 seconds to load in lunar Wayland sessions
This bug was fixed in the package xdg-desktop-portal-gnome - 44~beta-1ubuntu1 --- xdg-desktop-portal-gnome (44~beta-1ubuntu1) lunar; urgency=medium * Revert commit that is incompatible with mutter 43 (LP: #2008165, #2008428) -- Jeremy Bicha Thu, 23 Feb 2023 19:50:07 -0500 ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2008165 Title: GTK apps take ~25 seconds to load in lunar Wayland sessions Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Bug description: Settings takes ~25 seconds to load on lunar So long that you think it's broken. But being 25 seconds is suspicious because that's the default DBus timeout. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 23 13:31:22 2023 InstallationDate: Installed on 2022-11-28 (86 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2008165/+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 2008453] [NEW] Two different trash icons on screen at once
Public bug reported: Two different trash icons on screen at once; one for desktop-icons-ng and one for ubuntu-dock. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-2 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 24 14:47:25 2023 InstallationDate: Installed on 2022-11-28 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Medium Status: New ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar third-party-packages ** Attachment added: "Screenshot from 2023-02-24 14-46-27.png" https://bugs.launchpad.net/bugs/2008453/+attachment/5649708/+files/Screenshot%20from%202023-02-24%2014-46-27.png ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2008453 Title: Two different trash icons on screen at once Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Two different trash icons on screen at once; one for desktop-icons-ng and one for ubuntu-dock. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-2 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 24 14:47:25 2023 InstallationDate: Installed on 2022-11-28 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2008453/+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 2003024] Re: Dock prevents Search switching to some apps in different workspaces
Marco is saying the fix is in version 75. Assuming that's correct, this bug should be closed as fixed in Ubuntu 23.04 already. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Fix Released -- 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/2003024 Title: Dock prevents Search switching to some apps in different workspaces Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. Edit: After some more testing, it only happens if either "Include applications from the current workspace only" or "Include applications from each monitor only" options are activated in Control Center > Multitasking > Application Switching I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003024/+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 2003024] Re: Dock prevents Search switching to some apps in different workspaces
This should have been fixed upstream by https://github.com/micheleg/dash-to- dock/pull/1848/commits/d1ad84841765faae698e316854b98d1e05ec3f1c -- 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/2003024 Title: Dock prevents Search switching to some apps in different workspaces Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. Edit: After some more testing, it only happens if either "Include applications from the current workspace only" or "Include applications from each monitor only" options are activated in Control Center > Multitasking > Application Switching I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003024/+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 1730201] Re: Show Nautilus bookmarks when right clicking on its dock icon
Well, it used to work all the times in the past because nautils was always running to provide the desktop, but that's not the case anymore. The only way to get this always working would be to ensure nautilus service is always alive... Or add another daemon for that. -- 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/1730201 Title: Show Nautilus bookmarks when right clicking on its dock icon Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Hi… Don't know if it's related to nautilus or dock. Bookmarks - default ones like documents, videos, pictures… or manually added ones through ctrl+d - are not displayed on right click on nautilus icon. Only [ new window | remove from favorites | details ] appear. ( I'm a little dubious about the details usefulness here, too ) I expected all the bookmarks to be displayed on right click, like in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730201/+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 1936734] Re: All app icons are missing
I see, for sure the original bug was due to problems with the initial locations icons implementation, which was causing loading not to happen. So this has to be another bug, maybe related maybe not :( -- 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/1936734 Title: All app icons are missing Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The Favorite applications on Gnome's launcher pane on the left sporadically disappear for significant amounts of time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-16 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Tags: hirsute wayland-session Uname: Linux 5.11.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1936734/+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 2007281] Re: Quicklists / right-click on LibreOffice to see recent documents not working
libreoffice has to provide such information to the dock, I don't thin this is the case. -- 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/2007281 Title: Quicklists / right-click on LibreOffice to see recent documents not working Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Quicklists / right-clicking on a dash item to see recent documents (or other items) is not working on my install of Ubuntu, with the exception of the File Manager. Not working for Libre Office and Okular. See image. Ubuntu 22.10, Gnome 43.1 Initially reported to GNOME but they indicated this is an UBUNTU issue (https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/6398#note_1671815) --> See for more images this link. Also asked on AskUbuntu but no reply there (https://askubuntu.com/questions/1454381/no-quicklists-recent-files- on-rightclicking-dash-apps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2007281/+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 1910938] Re: Text is missing from shell panel and menus
NVIDIA desktop owners: Please subscribe to bug 1876632 instead of this one. ** Description changed: + If you are using NVIDIA as your primary GPU then please subscribe to bug + 1876632 instead of this one. + + --- + Hello [happy new year :) ! ] Text information in the Ubuntu dialogs aren't displayed, or some times just a part of it. I don't see the hours, but i see the icons like Firefox actually opened, my battery etc. and notifications are empty (just the "!" icon). Text normally displayed when mouse-hover the applications icons is not displayed, when Ubuntu ask for my password the frame display only 3 or 4 characters, when i put the computer in standby and reopen it doesn't change anything, and the bullets of my password aren't displayed when i login. The text normally displayed on the menus aren't displayed too, same for the application menu (when hitting the bottom left corner button) and icons of applications (like Discord options on the top right of the screen). The only text from xorg that is displayed (if it's from xorg…) is the window's title (like "#Room - Discord" for Discord application, or "me@computer: ~/" above the terminal). What is left works : Firefox can display text, and text is displayed in settings for example. P.S: a reboot solved the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 02:26:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (56 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1910938 Title: Text is missing from shell panel and menus Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: If you are using NVIDIA as your primary GPU then please subscribe to bug 1876632 instead of this one. --- Hello [happy new year :) ! ] Text information in the Ubuntu dialogs aren't displayed, or some times just a part of it. I don't see the hours, but i see the icons like Firefox actually opened, my battery etc. and notifications are empty (just the "!" icon). Text normally displayed when mouse-hover the applications icons is not displayed, when Ubuntu ask for my password the frame display only 3 or 4 characters, when i put the computer in standby and reopen it doesn't change anything, and the bullets of my password aren't displayed when i login. The text normally displayed on the menus aren't displayed too, same for the
[Desktop-packages] [Bug 929447] Re: gnome-shell freezes when entering "overview"
Jon, This bug has been closed for 11 years... What you describe sounds like a gnome-shell crash in a Xorg session so please create a new bug and follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/929447 Title: gnome-shell freezes when entering "overview" Status in gnome-shell package in Ubuntu: Fix Released Bug description: This is new as of today's updates in precise. Every so often (but frequently) gnome-shell with hang when accessing "overview". Dropping down to console and killing gnome-shell restarts it and I'm able to carry on. But it's damn frustrating ;) Happy to provide additional info, please just let me know what and how to get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/929447/+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 1955579] Re: Text disappears in GNOME Shell 3.36.9
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 Make that bug 1876632... ** This bug is no longer a duplicate of bug 1910938 Text is missing from shell panel and menus ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- 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/1955579 Title: Text disappears in GNOME Shell 3.36.9 Status in gnome-shell package in Ubuntu: New Bug description: This bug occurs when staying in one of the voice channels on Discord for prolonged periods of time. I have also reported the bug in [here](https://github.com/linuxmint/cinnamon/issues/3442#issuecomment-997984435) and [here](https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4889) OS Information: Linux Kernel version: 5.4.0-91-generic Distribution release: Ubuntu 20.04 Distribution version: 20.04.3 LTS DE Information: GNOME version: 3 GNOME Shell version: 3.36.9 Display Server Information: Display Server: X11 Display Server Version: X.Org 1.20.11 Display Manager Information: Display Manager: gdm3 Processor Information: Hardware: Intel(R) Core(TM) i3-6100 CPU @3.70GHz Cores: 2 Threads: 4 Video Card Information: Hardware: NVIDIA Corporation: GM206 [GeForce GTX 950] Driver: nvidia-driver-470 (proprietary, tested) Here's one of the best ways to reproduce this issue: 1. Open Discord 2. Enter into any voice channel on Discord and just stay there for a day, it may range from 30 minutes to 24 hours for it to occur. Expected results: The text shouldn't vanish from the desktop environment and it shouldn't cause any graphical issues. Instead, if anything stops working, it should reload! And the Settings app should open without crashing. Actual results: The text vanishes from the desktop environment and/or other graphical errors occur, and the GNOME settings app crashes upon attempting to open. Here's the screenshots (copied from Github):    To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955579/+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 2008444] [NEW] "Language Support Is Incomplete" notification after each boot
Public bug reported: Each time I boot Kubuntu 22.04 LTS, I get a KDE Daemon notification that "Language Support Is Incomplete". This is similar to several other bugs here, but acts differently for me. I can click on the notification box but nothing happens if I do - there is no offered method to correct the problem (it doesn't even ask for authorization, as reported elsewhere). AFAIK I'm running US English only. (I did set the Time format to en_CA.UT-8 to get ISO 8601 date format.) dave@MONOLITH:~$ check-language-support hunspell-en-au hunspell-en-ca hunspell-en-gb hunspell-en-za hyphen-en-ca hyphen-en-gb hyphen-en-us libreoffice-help-en-gb libreoffice-help-en-us libreoffice-l10n-en-gb libreoffice-l10n-en-za mythes-en-au mythes-en-us thunderbird-locale-en thunderbird-locale-en-gb thunderbird-locale-en-us dave@MONOLITH:~$ lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2008444 Title: "Language Support Is Incomplete" notification after each boot Status in language-selector package in Ubuntu: New Bug description: Each time I boot Kubuntu 22.04 LTS, I get a KDE Daemon notification that "Language Support Is Incomplete". This is similar to several other bugs here, but acts differently for me. I can click on the notification box but nothing happens if I do - there is no offered method to correct the problem (it doesn't even ask for authorization, as reported elsewhere). AFAIK I'm running US English only. (I did set the Time format to en_CA.UT-8 to get ISO 8601 date format.) dave@MONOLITH:~$ check-language-support hunspell-en-au hunspell-en-ca hunspell-en-gb hunspell-en-za hyphen-en-ca hyphen-en-gb hyphen-en-us libreoffice-help-en-gb libreoffice-help-en-us libreoffice-l10n-en-gb libreoffice-l10n-en-za mythes-en-au mythes-en-us thunderbird-locale-en thunderbird-locale-en-gb thunderbird-locale-en-us dave@MONOLITH:~$ lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2008444/+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 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1+1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1936734] Re: All app icons are missing
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1522 https://github.com/micheleg/dash-to-dock/issues/1522 ** Changed in: dash-to-dock Status: New => Unknown ** Changed in: dash-to-dock Remote watch: github.com/micheleg/dash-to-dock/issues #1852 => github.com/micheleg/dash-to-dock/issues #1522 -- 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/1936734 Title: All app icons are missing Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The Favorite applications on Gnome's launcher pane on the left sporadically disappear for significant amounts of time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-16 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Tags: hirsute wayland-session Uname: Linux 5.11.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1936734/+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 2008433] Re: Request to enable WidevineCDM checking on ARM64
The attachment "widevine-enable-all-architectures.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/2008433 Title: Request to enable WidevineCDM checking on ARM64 Status in chromium-browser package in Ubuntu: New Bug description: If possible, could you please include a patch to enable widevinecdm checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get set for arm64 linux (but does on amd64 linux) so chromium does not even check for widevine even if we have it available and placed in the directory manually. I am currently using the attached patch of my making when testing locally to correct this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008433/+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 2008433] [NEW] Request to enable WidevineCDM checking on ARM64
Public bug reported: If possible, could you please include a patch to enable widevinecdm checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get set for arm64 linux (but does on amd64 linux) so chromium does not even check for widevine even if we have it available and placed in the directory manually. I am currently using the attached patch of my making when testing locally to correct this issue. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "widevine-enable-all-architectures.patch" https://bugs.launchpad.net/bugs/2008433/+attachment/5649663/+files/widevine-enable-all-architectures.patch -- 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/2008433 Title: Request to enable WidevineCDM checking on ARM64 Status in chromium-browser package in Ubuntu: New Bug description: If possible, could you please include a patch to enable widevinecdm checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get set for arm64 linux (but does on amd64 linux) so chromium does not even check for widevine even if we have it available and placed in the directory manually. I am currently using the attached patch of my making when testing locally to correct this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008433/+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 2008428] [NEW] xdg-desktop-portal-gnome fails to startup after upgrading to 44~beta-1
Public bug reported: Since upgrading xdg-desktop-portal-gnome to 44~beta-1, it fails to startup (along with xdg-desktop-portal as well) - downgrading to 43.1-2 fixes the issue. As a result of this launching any GTK application seems to take ~25 seconds - I assume that GTK or some such is trying to contact the portal backend over dbus and then eventually timing out. Relevant excerpts from journalctl: [amurray:~] 3 $ systemctl status --user xdg-desktop-portal-gnome.service × xdg-desktop-portal-gnome.service - Portal service (GNOME implementation) Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gnome.service; static) Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 57s ago Process: 52457 ExecStart=/usr/libexec/xdg-desktop-portal-gnome (code=killed, signal=TERM) Main PID: 52457 (code=killed, signal=TERM) CPU: 11ms Feb 24 09:37:33 graphene systemd[7592]: Starting Portal service (GNOME implementation)... Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal-gnome.service: start operation timed out. Terminating. Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal-gnome.service: Failed with result 'timeout'. Feb 24 09:39:03 graphene systemd[7592]: Failed to start Portal service (GNOME implementation). [amurray:~] 1 $ systemctl status --user xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 53s ago Process: 52453 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 52453 (code=killed, signal=TERM) CPU: 15ms Feb 24 09:37:33 graphene systemd[7592]: Starting Portal service... Feb 24 09:38:23 graphene xdg-desktop-por[52453]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached Feb 24 09:38:48 graphene xdg-desktop-por[52453]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached Feb 24 09:38:48 graphene xdg-desktop-por[52453]: No skeleton to export Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal.service: start operation timed out. Terminating. Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal.service: Failed with result 'timeout'. Feb 24 09:39:03 graphene systemd[7592]: Failed to start Portal service. [amurray:~] $ systemctl status --user xdg-desktop-portal-gtk.service ○ xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation) Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gtk.service; static) Active: inactive (dead) Feb 24 09:36:22 graphene systemd[7592]: Starting Portal service (GTK/GNOME implementation)... Feb 24 09:36:22 graphene systemd[7592]: Started Portal service (GTK/GNOME implementation). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 09:36:16 2023 InstallationDate: Installed on 2021-08-03 (569 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-01-27 (27 days ago) ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2008428 Title: xdg-desktop-portal-gnome fails to startup after upgrading to 44~beta-1 Status in xdg-desktop-portal-gnome package in Ubuntu: New Bug description: Since upgrading xdg-desktop-portal-gnome to 44~beta-1, it fails to startup (along with xdg-desktop-portal as well) - downgrading to 43.1-2 fixes the issue. As a result of this launching any GTK application seems to take ~25 seconds - I assume that GTK or some such is trying to contact the portal backend over dbus and then eventually timing out. Relevant excerpts from journalctl: [amurray:~] 3 $ systemctl status --user xdg-desktop-portal-gnome.service × xdg-desktop-portal-gnome.service - Portal service (GNOME implementation) Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gnome.service; static) Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 57s ago Process: 52457 ExecStart=/usr/libexec/xdg-desktop-portal-gnome (code=killed, signal=TERM) Main PID: 52457 (code=killed, signal=TERM) CPU: 11ms Feb 24 09:37:33 graphene systemd[7592]:
[Desktop-packages] [Bug 1947920] Re: tracker-miner-f 100% CPU and slows system down
My problem was with the CPU being throttled to 500Mhz if I turned the power supply on at the wrong time during boot up. Nothing to do with tracker-miner-f. Please delete my bug report! ** This bug is no longer a duplicate of bug 1961540 tracker-miner-fs-3 massive CPU usage and system slowdown ** Changed in: tracker (Ubuntu) Status: New => Invalid ** Description changed: - tracker-miner-f has been using 100% CPU and my system making it almost - unresponsive. This happens around once a month or so when I boot up. It - sometimes lasts for a number of days (or a number of resets) until the - system becomes responsive again. - - The command "tracker status" always shows the same thing: "Estimated - less than one second left" although it appears that everything is - already indexed because the file and folder counts do not increase. - - Even so tracker-miner-f is still showing 100% CPU - - - - inspiron@Inspiron-7348:~$ tracker status - Currently indexed: 101154 files, 16046 folders - Remaining space on database partition: 160.5 GB (64.11%) - Data is still being indexed: Estimated less than one second left - - - - inspiron@Inspiron-7348:~$ tracker status - Currently indexed: 101155 files, 16045 folders - Remaining space on database partition: 161.1 GB (64.31%) - Data is still being indexed: Estimated 01h 19m 03s left - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: tracker 2.3.6-0ubuntu1 - ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 - Uname: Linux 5.11.0-37-generic x86_64 - ApportVersion: 2.20.11-0ubuntu27.20 - Architecture: amd64 - CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - Date: Thu Oct 21 08:25:58 2021 - InstallationDate: Installed on 2021-06-28 (114 days ago) - InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) - SourcePackage: tracker - UpgradeStatus: No upgrade log present (probably fresh install) - - - - UPDATE - - I have now reset the tracker and it seems to be going through and - indexing everything again. - - tracker reset --hard - - Now tracker-miner-f has re-indexed everything and tracker-extract and - tracker-store are running. - - - - UPDATE 2 - - The tracker reset completed indexing everything and the went into idle - state. However when rebooting, tracker-miner-f went to 100% CPU once - again. + Invalid. ** Information type changed from Public to Private -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1947920 Title: tracker-miner-f 100% CPU and slows system down Status in tracker package in Ubuntu: Invalid Bug description: Invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1947920/+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 1525628] Re: tracker needs to be killed on every boot
I originally thought I had this problem but it turns out it was nothing to do with tracker. My problem was with the CPU being throttled to 500Mhz if I turned the power supply on at the wrong time during boot up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1525628 Title: tracker needs to be killed on every boot Status in tracker package in Ubuntu: Confirmed Bug description: At every boot, tacker-miner-fs and tracker-extract uses all of the processor and needs to be killed manually for computer to work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker 1.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 13 13:02:58 2015 InstallationDate: Installed on 2015-04-24 (232 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1525628/+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 1754125] Re: Rhythmbox stays running in the background after quit
I'm experiencing this issue too. I do not understand why closing an app does not actually close it. That's quite frustrating to me. If I want to minimize and leave it running in the background, I'd do that instead. Maybe this is my Windows background, but X means close to me. When I close Rhythmbox while it's playing then Rhythmbox is removed from the dock. That leaves me with no obvious way to turn the music off and I have to re-open Rhythmbox in order to press stop. At a minimum, can there be a setting in rhythmbox to control which type of close we want? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: Triaged Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1969315] Re: text in torrent info tabs change after opening it to gibberish
There is a new transmission version available. Hope it reach Ubuntu repo soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 2006982] Re: Update to version 4.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/2006982 Title: Update to version 4.0 Status in transmission package in Ubuntu: Confirmed Status in transmission package in Debian: Unknown Bug description: Transmission recently released a new version. please update the version in the repository. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2006982/+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 2008420] Re: '/usr/share/applications/default.list' content outdated
Here is the concerned file: ** Attachment added: "defaults.list" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008420/+attachment/5649647/+files/defaults.list -- 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/2008420 Title: '/usr/share/applications/default.list' content outdated Status in nautilus package in Ubuntu: New Bug description: For Ubuntu 22.10 and 23.04, the contents of file /usr/share/applcations/default.list has file associations for audio file set as 'rhythmbox.desktop' as the application startup file to associate files to... That file was updated and changed names to 'org.gnome.Rhythmbox3.desktop'... File '/usr/share/applications/defaults.list' needs to be updated to reflect that change. I know that the system that file belongs to, is underlying to nautilus, but I was unsure on what to file this issue against. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 13:08:55 2023 GsettingsChanges: InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008420/+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 2008420] [NEW] '/usr/share/applications/default.list' content outdated
Public bug reported: For Ubuntu 22.10 and 23.04, the contents of file /usr/share/applcations/default.list has file associations for audio file set as 'rhythmbox.desktop' as the application startup file to associate files to... That file was updated and changed names to 'org.gnome.Rhythmbox3.desktop'... File '/usr/share/applications/defaults.list' needs to be updated to reflect that change. I know that the system that file belongs to, is underlying to nautilus, but I was unsure on what to file this issue against. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 13:08:55 2023 GsettingsChanges: InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/2008420 Title: '/usr/share/applications/default.list' content outdated Status in nautilus package in Ubuntu: New Bug description: For Ubuntu 22.10 and 23.04, the contents of file /usr/share/applcations/default.list has file associations for audio file set as 'rhythmbox.desktop' as the application startup file to associate files to... That file was updated and changed names to 'org.gnome.Rhythmbox3.desktop'... File '/usr/share/applications/defaults.list' needs to be updated to reflect that change. I know that the system that file belongs to, is underlying to nautilus, but I was unsure on what to file this issue against. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 13:08:55 2023 GsettingsChanges: InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008420/+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 1988836] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-67.74~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-67.74~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
Btw, im-config 0.55-1 is not in Debian testing yet, which might be the reason why you didn't see the issue there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+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 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
Wow.. This is "interesting". Compare this with bug #2007379, where we work around the problem which the now reversed upstream g-s-d commit tries to address. (I wasn't aware of this upstream move.) im-config 0.55-1 is already in lunar-release. Can the fact that im- config now sets GTK_IM_MODULE=ibus be the reason why the upstream commit didn't work out well? Would that g-s-d commit possibly work for us with GTK_IM_MODULE unset? I think this is worth to investigate. At least the g-s-d commit is the right idea. As regards the recent im-config change, I suppose it's motivated in both jammy and Debian 12. (And also in lunar unless we figure out how to avoid the regression you describe in this bug.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+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 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
** Description changed: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- - daemon/-/commit/baeeed + daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+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 929447] Re: gnome-shell freezes when entering "overview"
This is probably caused by something different than the described issue, but I'm experiencing this symptom periodically on 22.04. I can still move my mouse around, but I can't exit the overview. I can ssh into the box, so it is some issue with gnome getting stuck. I submitted a report. -- 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/929447 Title: gnome-shell freezes when entering "overview" Status in gnome-shell package in Ubuntu: Fix Released Bug description: This is new as of today's updates in precise. Every so often (but frequently) gnome-shell with hang when accessing "overview". Dropping down to console and killing gnome-shell restarts it and I'm able to carry on. But it's damn frustrating ;) Happy to provide additional info, please just let me know what and how to get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/929447/+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 2008355] [NEW] Unable to set fractional scaling on three monitor setup
Public bug reported: I have three monitors: one 4K (3840x2160) display and two 2560x1440. I've tried setting fractional scaling to 150% on the 4K display in gnome control center (ubuntu 22.10), but it does not work. It works fine when I disconnect some displays, leaving only the 4K or 4k and one 2560. However, when all three are connected the apply button is disabled and the following message appears: "Changes Cannot be Applied. This could be due to hardware limitations." When gnome-control-center is started from terminal it shows the following warning: ``` (gnome-control-center:12235): display-cc-panel-WARNING **: 18:42:27.389: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent ``` thought it doesn't seem to be the case. After some digging I've found a workaround, executing the following commands seems to do what the control panel does: ``` xrdb -m
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.15.0-67.74)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-67.74) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.15/5.15.0-67.74~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.15 (5.15.0-67.74~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525/525.85.05-0ubuntu0.20.04.1 (amd64) nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Autopkgtest regression report (linux-restricted-modules/5.15.0-67.74)
All autopkgtests for the newly accepted linux-restricted-modules (5.15.0-67.74) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437819 -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+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 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437819 -- 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/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+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 2008279] [NEW] xsettings ibus commit broke text input for Firefox & Chromium snaps
Public bug reported: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: Triaged ** Tags: lunar snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+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 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: In Progress => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: In Progress => Triaged -- 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/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Kinetic: In Progress Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). ===
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Description changed: + [ Impact ] + + * The introduction of the -open NVIDIA drivers requires a change in the + way we detect driver series and flavours. Failing to do so, causes the + ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open + drivers over the non-open ones (LP: #1988836). + + * Furthermore, calling the ubuntu-drivers tool where the alsa-utils + package is not installed (mainly on servers), ubuntu-drivers (through + the sl-modem plugin) complains, unnecessarily about the missing aplay + binary. + + [ Test Plan ] + + * Install the new ubuntu-drivers-common from -proposed on a system + where the GPU is compatible with the 515 series (or higher). + + * Run the ubuntu-drivers list command, and make sure that the 515 + driver series (or higher) is listed. + + * Try installing the driver using the following command: +sudo ubuntu-drivers install + + * Check which driver series was installed (you can use the "sudo + ubuntu-drivers debug" command), and make sure that the installation does + not cause ubuntu-drivers to crash. + + [ Where problems could occur ] + + * A problem in the ubuntu-drivers tool can cause it to install a driver which +is not recommended for the detected hardware, or even cause the package +installation to fail, and prevent users from logging in through the +graphics interface. + + + [ Other Info ] + + * To prevent failures of the test-suite on architectures such as armhf (as seen +in Lunar), we are skipping the tests for any architectures other than amd64 +and arm64 (which are the only ones actually using ubuntu-drivers). +This was already the case with riscv, and we now have an easier way +to do so in the debian/rules file. + + + == Changelogs == + + === Kinetic and Jammy === + + [ Alberto Milone ] + * New upstream release: + * UbuntuDrivers/detect.py: + - Make sure all -open drivers have a lower priority, regardless + of whether the --server parameter is passed in or not. + - Update regex in nvidia_desktop_pre_installation_hook. This prevents + ubuntu-drivers from crashing when dealing with the -open NVIDIA + drivers (LP: #1993019). + * tests/test_ubuntu_drivers.py: + - Add tests so we make sure to keep preferring non-open NVIDIA + modules over the -open ones, at least until the open modules catch up + feature wise and performance wise. + + [ gongzhengyang ] + * UbuntuDrivers/detect.py: + - Fix local variable 'version' being referenced before assignment + when catching ValueError (LP: #1993019). + + [ Jeff Lane ] + * detect-plugins/sl-modem.py: + - Add some error trapping when aplay is not installed (on servers). + + === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === + +* UbuntuDrivers/detect.py: + - Make sure -open drivers have a lower priority (LP: #1988836). + + == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === -* UbuntuDrivers/detect.py: - - Make sure -open drivers have a lower priority (LP: #1988836). + * UbuntuDrivers/detect.py: + - Make sure -open drivers have a lower priority (LP: #1988836). Hello, we received a drive-by complaint about the ubuntu-drivers autoinstall tool: < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command < Fhazal> this error appear when i try to auto install recommended driver < Fhazal> https://pastebin.com/ydZVFT24 The contents of the pastebin: Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 513, in greet() File
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Description changed: - Hello, we received a drive-by complaint about the ubuntu-drivers - autoinstall tool: + == Changelogs == + + === Kinetic and Jammy === + + [ Alberto Milone ] + * debian/rules: + - Limit the tests to the selected architectures (amd64, arm64). + This prevents armhf builds from failing. + * UbuntuDrivers/detect.py: + - Make sure all -open drivers have a lower priority, regardless + of whether the --server parameter is passed in or not. + - Update regex and unify package name parsing in the following + functions by using the new NvidiaPkgNameInfo class: + nvidia_desktop_pre_installation_hook, + _get_headless_no_dkms_metapackage, + nvidia_desktop_pre_installation_hook, + get_linux_modules_metapackage, + This prevents ubuntu-drivers from crashing when dealing with + the -open NVIDIA drivers (LP: #1993019). + * tests/test_ubuntu_drivers.py: + - Add tests so we make sure to keep preferring non-open NVIDIA + modules over the -open ones, at least until the open modules catch up + feature wise and performance wise. + + [ gongzhengyang ] + * UbuntuDrivers/detect.py: + - Fix local variable 'version' being referenced before assignment + when catching ValueError (LP: #1993019). + + [ Jeff Lane ] + * detect-plugins/sl-modem.py: + - Add some error trapping when aplay is not installed (on servers). + + + Hello, we received a drive-by complaint about the ubuntu-drivers autoinstall tool: < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command < Fhazal> this error appear when i try to auto install recommended driver < Fhazal> https://pastebin.com/ydZVFT24 The contents of the pastebin: Traceback (most recent call last): - File "/usr/bin/ubuntu-drivers", line 513, in - greet() - File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__ - return self.main(*args, **kwargs) - File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main - rv = self.invoke(ctx) - File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke - return _process_result(sub_ctx.command.invoke(sub_ctx)) - File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke - return ctx.invoke(self.callback, **ctx.params) - File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke - return __callback(*args, **kwargs) - File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in new_func - return ctx.invoke(f, obj, *args, **kwargs) - File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke - return __callback(*args, **kwargs) - File "/usr/bin/ubuntu-drivers", line 432, in autoinstall - command_install(config) - File "/usr/bin/ubuntu-drivers", line 187, in command_install - UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install) - File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in nvidia_desktop_pre_installation_hook - with_nvidia_kms = version >= 470 + File "/usr/bin/ubuntu-drivers", line 513, in + greet() + File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__ + return self.main(*args, **kwargs) + File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main + rv = self.invoke(ctx) + File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke + return _process_result(sub_ctx.command.invoke(sub_ctx)) + File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke + return ctx.invoke(self.callback, **ctx.params) + File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke + return __callback(*args, **kwargs) + File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in new_func + return ctx.invoke(f, obj, *args, **kwargs) + File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke + return __callback(*args, **kwargs) + File "/usr/bin/ubuntu-drivers", line 432, in autoinstall + command_install(config) + File "/usr/bin/ubuntu-drivers", line 187, in command_install + UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install) + File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in nvidia_desktop_pre_installation_hook + with_nvidia_kms = version >= 470 UnboundLocalError: local variable 'version' referenced before assignment - Skimming the version on my system it sure feels plausible: def nvidia_desktop_pre_installation_hook(to_install): - '''Applies changes that need to happen before installing the NVIDIA drivers''' - with_nvidia_kms = False + '''Applies changes that need to happen before installing the NVIDIA drivers''' + with_nvidia_kms = False - # Enable KMS if nvidia >= 470 - for package_name in to_install: - if
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-66.73~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-66.73~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2007124] Re: Move available config files from /etc to /usr
This was uploaded to lunar after a brief IRC conversation: https://irclogs.ubuntu.com/2023/02/23/%23ubuntu-desktop.html#t14:18 ** Changed in: fontconfig (Ubuntu) Status: New => Fix Committed ** Changed in: fontconfig (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2007124 Title: Move available config files from /etc to /usr Status in fontconfig package in Ubuntu: Fix Committed Bug description: At the upgrade to fontconfig 2.10 a decade ago, the directory for storing available config files was changed from /etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail. It was done upstream as well as in Debian, but Ubuntu delayed the transition for some reason. I think we should do that transition in Ubuntu too. That will get Ubuntu in sync with the upstream documentation and the delta to Debian gets reduced a little. The changes needed are straightforward. I put a proposed upload in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig and I would appreciate someone's eyes on it. So, what's the caveat? The only thing I can think of is that distros, system admins and individual users may have tweaked the font configuration by including symlinks which point to the moved files. While I don't have the impression that such symlinks are very frequent — custom conf files put directly in /etc/fonts/conf.d or equivalent places in $HOME seem to be more common — to the extent they exist, they will be silently disabled. Bug #2005124 revealed an example of a symlink which pointed to a file which will be moved if we do this. OTOH, in that case upstream added a symlink with the very same name, so we had to deal with that conflict. If the name of Kubuntu's link had been something else, we might not be aware of it yet. The changelog for this upload: https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1 states that the transition will be done "later with another upload once the details are sorted". Are there other details which I have missed? If not, I suppose that the potential inconvenience is approximately as big today as it was 2012. And since next LTS release is more than one year ahead, this ought to be an appropriate time to make the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2007124/+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 1910938] Re: Text is missing from shell panel and menus
This bugs affects me too. In my case it is triggered by running DIGIStorage or Koofr (same codebase) apps for a long time. If I stop using these app then there is no issue. I think it happens more frequently when the computer is idle for a while or the screen is blank and then you start using the computer again. -- 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/1910938 Title: Text is missing from shell panel and menus Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hello [happy new year :) ! ] Text information in the Ubuntu dialogs aren't displayed, or some times just a part of it. I don't see the hours, but i see the icons like Firefox actually opened, my battery etc. and notifications are empty (just the "!" icon). Text normally displayed when mouse-hover the applications icons is not displayed, when Ubuntu ask for my password the frame display only 3 or 4 characters, when i put the computer in standby and reopen it doesn't change anything, and the bullets of my password aren't displayed when i login. The text normally displayed on the menus aren't displayed too, same for the application menu (when hitting the bottom left corner button) and icons of applications (like Discord options on the top right of the screen). The only text from xorg that is displayed (if it's from xorg…) is the window's title (like "#Room - Discord" for Discord application, or "me@computer: ~/" above the terminal). What is left works : Firefox can display text, and text is displayed in settings for example. P.S: a reboot solved the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 02:26:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (56 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910938/+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 2003331] Re: Can't log in to lunar x11 session
The above observations are with virtualbox 6.1.38-dfsg-3~ubuntu1.22.04.1 on jammy. ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2003331 Title: Can't log in to lunar x11 session Status in ubuntu-meta package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: On a freshly installed and updated lunar in VirtualBox it doesn't let me log in to Ubuntu on Xorg. I'm just bumped back to the login screen. journalctl extract attached. On my regular (updated) lunar install, logging in to Ubuntu on Xorg works fine. But that's anything but a fresh install. Missing dependency? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003331/+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 1949637] Re: Libreoffice crash
conferm to swmeier (comment #4) this was good for me too: | Deleting my user profile fixed the problem: | | mv ~/.config/libreoffice/4/user ~/.config/libreoffice/4/user-old The error was generated launching libre from root prompt. After that only root could open libre. the mv solve problem. Tks ! Marco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1949637 Title: Libreoffice crash Status in libreoffice package in Ubuntu: Confirmed Bug description: Libreoffice crashed on startup: sven@:~/$ libreoffice terminate called after throwing an instance of 'com::sun::star::lang::IllegalArgumentException' Unspecified Application Error I've removed Libreoffice completely, installed it again via the Software-Center and it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 3 21:25:16 2021 InstallationDate: Installed on 2019-10-03 (762 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) SourcePackage: libreoffice UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949637/+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 2008165] Re: GTK apps take ~25 seconds to load in lunar Wayland sessions
Another lunar system was free of the bug a moment ago, until I installed: https://launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/44~beta-1 ** No longer affects: xdg-desktop-portal (Ubuntu) ** No longer affects: libadwaita-1 (Ubuntu) ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2008165 Title: GTK apps take ~25 seconds to load in lunar Wayland sessions Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Bug description: Settings takes ~25 seconds to load on lunar So long that you think it's broken. But being 25 seconds is suspicious because that's the default DBus timeout. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 23 13:31:22 2023 InstallationDate: Installed on 2022-11-28 (86 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2008165/+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 1976554] Re: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend
@Giampiero an easier way to fix the orientation rather than using the mouse: Log in first (that doesn't need the mouse) and then open a terminal (CTRL+ALT+T) and type in `xrandr -o normal`. This works despite the screen rotation being set to locked. -- 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/1976554 Title: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+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 2008165] Re: GTK apps take ~25 seconds to load on lunar
Same issue in gnome-text-editor. ** Attachment added: "gnome-text-editor.txt" https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2008165/+attachment/5649496/+files/gnome-text-editor.txt ** Changed in: libadwaita-1 (Ubuntu) Importance: Undecided => High ** Also affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => High ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided => High ** Summary changed: - GTK apps take ~25 seconds to load on lunar + GTK apps take ~25 seconds to load in lunar Wayland sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2008165 Title: GTK apps take ~25 seconds to load in lunar Wayland sessions Status in libadwaita-1 package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Status in xdg-desktop-portal-gnome package in Ubuntu: New Bug description: Settings takes ~25 seconds to load on lunar So long that you think it's broken. But being 25 seconds is suspicious because that's the default DBus timeout. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 23 13:31:22 2023 InstallationDate: Installed on 2022-11-28 (86 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2008165/+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 2008165] Re: GTK apps take ~25 seconds to load on lunar
Here's the backtrace from gnome-control-center but now I realize it's all GTK(4) apps that have the issue. ** Summary changed: - Settings takes ~25 seconds to load on lunar + GTK apps take ~25 seconds to load on lunar ** Attachment added: "bt.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2008165/+attachment/5649494/+files/bt.txt ** Package changed: gnome-control-center (Ubuntu) => libadwaita-1 (Ubuntu) ** Changed in: libadwaita-1 (Ubuntu) Status: Incomplete => 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/2008165 Title: GTK apps take ~25 seconds to load in lunar Wayland sessions Status in libadwaita-1 package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Status in xdg-desktop-portal-gnome package in Ubuntu: New Bug description: Settings takes ~25 seconds to load on lunar So long that you think it's broken. But being 25 seconds is suspicious because that's the default DBus timeout. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 23 13:31:22 2023 InstallationDate: Installed on 2022-11-28 (86 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2008165/+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 2008165] Re: Settings takes ~25 seconds to load on lunar
Thanks Daniel, could you get a backtrace during that time? it could tell us where it's hanging ** 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/2008165 Title: Settings takes ~25 seconds to load on lunar Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Settings takes ~25 seconds to load on lunar So long that you think it's broken. But being 25 seconds is suspicious because that's the default DBus timeout. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 23 13:31:22 2023 InstallationDate: Installed on 2022-11-28 (86 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2008165/+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
