[Desktop-packages] [Bug 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
Submitted a fix: https://code.launchpad.net/~aleasto/chromium- browser/+git/snap-from-source/+merge/470118 -- 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/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: In Progress Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
Can confirm it's fixed in latest/candidate -- 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/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 2064698] Re: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extens
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2064698 Title: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extensions/ubuntu- appindicat...@ubuntu.com/dbusProxy.js:89:33] Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Every session I see those errors in the attached log file. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 3 08:54:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (41 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2064698/+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 2072395] Re: [snap] Chromium with core24 base won't start: desktop-launch not found
This might not end up being related, but interesting nonetheless: I was hacking on the stable Firefox snap using https://snapcraft.io/overlay After mounting the overlay `sudo /snap/overlay/current/overlay $(realpath /snap/firefox/current)` I tried to start firefox and it did not launch. I haven't seen this happening with other snaps. The journal contains: Aug 01 10:40:59 thinkpad kernel: audit: type=1400 audit(1722501659.347:4687): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/proc/379042/maps" pid=379042 comm="5" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Aug 01 10:40:59 thinkpad firefox_firefox.desktop[379021]: Content snap command-chain for /snap/firefox/4630/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Do we know if this bug also came with the AppArmor denial? -- 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/2072395 Title: [snap] Chromium with core24 base won't start: desktop-launch not found Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Today I was prompted to update my chromium snap, so I closed it down and the auto-refresh happened. When I tried to launch it, it did not come up. Running `chromium` from the command line resulted in the following error: $ chromium Content snap command-chain for /snap/chromium/2905/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Browsing the internet, I found people saying that gnome needed to be connected. Running `sudo snap connect chromium:gnome-46-2404 gnome-46-2404:gnome-46-2404` did not fix the problem. I'm not sure it matters for a snap, but this is (very recently updated) ubuntu 22.04 running KDE on x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2072395/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
** Changed in: ubuntu-drivers-common (Ubuntu Noble) Status: In Progress => Fix Committed ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Triaged => Fix Committed -- 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/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Noble: Fix Committed Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+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 2072395] Re: [snap] Chromium with core24 base won't start: desktop-launch not found
No we don't know, or no it did not have an AppArmor denial? :P -- 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/2072395 Title: [snap] Chromium with core24 base won't start: desktop-launch not found Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Today I was prompted to update my chromium snap, so I closed it down and the auto-refresh happened. When I tried to launch it, it did not come up. Running `chromium` from the command line resulted in the following error: $ chromium Content snap command-chain for /snap/chromium/2905/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Browsing the internet, I found people saying that gnome needed to be connected. Running `sudo snap connect chromium:gnome-46-2404 gnome-46-2404:gnome-46-2404` did not fix the problem. I'm not sure it matters for a snap, but this is (very recently updated) ubuntu 22.04 running KDE on x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2072395/+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 2065294] Re: Diagnostics settings flips to Never without any user action
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: gnome-control-center (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu Noble) Importance: Undecided Status: 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/2065294 Title: Diagnostics settings flips to Never without any user action Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: New Status in gnome-control-center source package in Noble: New Bug description: steps to reproduce. 1. Open Gnome Settings 2. Go to Privacy -> Diagnostics 3. You should see `Send error reports to Canonical` set to Manual by default. 4. Stay on the settings page for some time (maybe <2 mins), the setting will slip to Never. You could also try to change the settings to Automatic and stay on the page, it will also flip to Never within a couple of minutes. I noticed this on Jammy, Mantic, and Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+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 2072395] Re: [snap] Chromium with core24 base won't start: desktop-launch not found
Actually I see `apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/proc/379042/maps" pid=379042 comm="5" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0` in my journal for all snaps, so might not be the cause afterall. -- 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/2072395 Title: [snap] Chromium with core24 base won't start: desktop-launch not found Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Today I was prompted to update my chromium snap, so I closed it down and the auto-refresh happened. When I tried to launch it, it did not come up. Running `chromium` from the command line resulted in the following error: $ chromium Content snap command-chain for /snap/chromium/2905/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Browsing the internet, I found people saying that gnome needed to be connected. Running `sudo snap connect chromium:gnome-46-2404 gnome-46-2404:gnome-46-2404` did not fix the problem. I'm not sure it matters for a snap, but this is (very recently updated) ubuntu 22.04 running KDE on x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2072395/+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 2065294] Re: Diagnostics settings flips to Never without any user action
** Description changed:
+ [ Impact ]
+
+ In GNOME Settings' Diagnostics page, the switch to control automatic bug
+ reporting to Canonical automatically flips to "Never" after 1 minute of
+ the page being open without interaction
+
+ The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
+ We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
+
+ A further change should be applied to the whoopsie-preferences service
+ to avoid quitting when there are clients still listening for potential
+ settings changes.
+
+ [ Test Plan ]
+
+ * Open GNOME Settings -> Privacy & Security -> Diagnostics
+
+ * You should see `Send error reports to Canonical` set to `Manual` by
default.
+> If instead it is set to Never, change it now to another option.
+
+ * Stay on the settings page for more than 60 seconds
+
+ * The setting should have remained the same and *not* have
+ automatically changed to `Never`.
+
+ [ Where problems could occur ]
+
+ This patch also tries to re-start the "whoopsie-preferences" daemon when
+ it automatically stops after 60 seconds, because GNOME Settings should
+ keep listening for settings changes from external factors. This should
+ not present any issues, but it's the most "intrusive" part of the patch.
+
+
+ [ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.
I noticed this on Jammy, Mantic, and Noble.
** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New
** Changed in: whoopsie-preferences (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: whoopsie-preferences (Ubuntu)
Status: New => Triaged
** Changed in: gnome-control-center (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: gnome-control-center (Ubuntu Noble)
Status: New => Confirmed
--
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/2065294
Title:
Diagnostics settings flips to Never without any user action
Status in gnome-control-center package in Ubuntu:
Fix Committed
Status in whoopsie-preferences package in Ubuntu:
Triaged
Status in gnome-control-center source package in Jammy:
Confirmed
Status in whoopsie-preferences source package in Jammy:
New
Status in gnome-control-center source package in Noble:
Confirmed
Status in whoopsie-preferences source package in Noble:
New
Bug description:
[ Impact ]
In GNOME Settings' Diagnostics page, the switch to control automatic
bug reporting to Canonical automatically flips to "Never" after 1
minute of the page being open without interaction
The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
A further change should be applied to the whoopsie-preferences service
to avoid quitting when there are clients still listening for potential
settings changes.
[ Test Plan ]
* Open GNOME Settings -> Privacy & Security -> Diagnostics
* You should see `Send error reports to Canonical` set to `Manual` by
default.
> If instead it is set to Never, change it now to another option.
* Stay on the settings page for more than 60 seconds
* The setting should have remained the same and *not* have
automatically changed to `Never`.
[ Where problems could occur ]
This patch also tries to re-start the "whoopsie-preferences" daemon
when it automatically stops after 60 seconds, because GNOME Settings
should keep listening for settings changes from external factors. This
should not present any issues, but it's the most "intrusive" part of
the patch.
[ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
[Desktop-packages] [Bug 2072771] Re: Update gnome-remote-desktop to 46.3
Verified gnome-remote-desktop=46.3-0ubuntu1 on Ubuntu 24.04 LTS against the test plans "Basic RDP Test Case" and "Basic Remote Login Test Case (For Ubuntu 24.04 LTS and later only)" ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2072771 Title: Update gnome-remote-desktop to 46.3 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Noble: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 46 series It includes a crash fix Changes since the current Ubuntu 24.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/46.2...46.3 Test Cases -- Complete the Basic RDP Test Case and Basic Remote Login Test Case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2072771/+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 2072596] Re: long delay when first installing version 46
On Ubuntu 24.04 LTS: - Verified using the Test Case that I could reproduce the issue with version 46.2-1~ubuntu24.04.2 - Verified using the Test Case that the issue is fixed with version 46.3-0ubuntu1 ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2072596 Title: long delay when first installing version 46 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Noble: Fix Committed Status in gnome-remote-desktop package in Debian: Fix Released Bug description: Impact -- There is a 90 second timeout delay during the upgrade to gnome-remote-desktop (as in the upgrade from Ubuntu Desktop 22.04 LTS or 23.10 to 24.04 LTS) More Details This SRU replaces the "automatic" postinst rules from dh_installsysusers and dh_installtmpfiles with custom postint rules that ensure that the sysusers and tmpfiles commands are run before dbus is reloaded. This is similar to what polkitd.postinst does but the new gnome-remote-desktop postinst is much simpler than what polkitd does. dh_installsysusers also adds Depends: systemd | systemd-standalone-sysusers | systemd-sysusers. (It appears like dh_installtmpfiles does not add similar dependencies). Because we only support systemd, I have manually added: Depends: systemd | systemd-sysusers, systemd | systemd-tmpfiles Test Case - From Ubuntu Desktop 24.04 LTS: 1. sudo apt remove gnome-remote-desktop 2. sudo systemctl stop gnome-remote-desktop 3. sudo deluser gnome-remote-desktop 4. sudo rm -fr /etc/gnome-remote-desktop /var/lib/gnome-remote-desktop Those steps will undo adding the user that systemd-sysusers is configured to add and undo adding the directories that systemd- tmpfiles adds. Then install the update. Verify that the update happens at normal speed without a long delay before completion. Alternate Test Case (Not Required) --- You could do an upgrade from 23.10 to 24.04 LTS but it requires much more time and attention to verify that there isn't an arbitrary delay while apt configures gnome-remote-desktop. Therefore, the other test case is recommended. What Could Go Wrong --- If a postinst command fails, then the system can be unable to finish installing gnome-remote-desktop. This can be a pain to clean up. In this case, the commands are protected by " || true". Other Info -- This issue is a follow-up for LP: #206 In that bug, gnome-remote-desktop wouldn't work at all for upgraders. This bugfix is being bundled with a new upstream release with more testing LP: #2072771 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2072596/+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 2072782] Re: Update gnome-online-accounts to 3.50.4
Verified version 3.50.4-0ubuntu2 of: libgoa-1.0-common:amd64 libgoa-1.0-0b:amd64 libgoa-backend-1.0-2:amd64 gnome-online-accounts:amd64 in Ubuntu 24.04 LTS ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2072782 Title: Update gnome-online-accounts to 3.50.4 Status in gnome-online-accounts package in Ubuntu: Fix Committed Status in gnome-online-accounts source package in Noble: Fix Committed Bug description: Impact == This is a new bugfix release in the stable 3.50.x series. It significantly improves the usability of the new "Microsoft 365" provider. However, that UI improvement changed translatable strings. See Other Info below. https://gitlab.gnome.org/GNOME/gnome-online- accounts/-/blob/3.50.4/NEWS It also improves the new WebDAV account type for Fastmail users. LP: #2072775 Test Cases == The autopkgtests for gnome-online-accounts should complete successfully Complete Test Case 2 (Google) from https://wiki.ubuntu.com/DesktopTeam/TestPlans/OnlineAccounts What Could Go Wrong === gnome-online-accounts is included by default in Ubuntu Desktop, Edubuntu, Ubuntu Budgie & Ubuntu Cinnamon. If gnome-online-accounts is broken, people using Ubuntu may not receive notifications for emails and calendar appointments. This can be mitigated somewhat by using online services via a web browser and enabling notifications in their web browser. Before Ubuntu 24.04 LTS, gnome-online-accounts used webkit2gtk to handle authentication. By using the browser, gnome-online-accounts can handle many additional types of authentication and is more resilient to API changes and restrictions from the online service providers. GNOME Online Accounts is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info == This update includes changes to translatable strings. This package uses Ubuntu language packs. Because language packs are only updated shortly before each Ubuntu LTS point release, ideally this update will be included before the language packs are updated. The Ubuntu Desktop team considers the effect of changing translatable strings to be low because the changed strings were very new and weren't translated much. The strings are part of the Microsoft 365 feature that is new in GNOME 46. The updated strings have been available upstream since late May and the translation coverage is better although still incomplete. We will likely do another SRU to include another upstream bugfix release (with updated translations) before Ubuntu 24.04.2. An update to translatable strings like this after a GNOME .0 release is very unusual. However, it was approved by the GNOME Release Team. Screenshots and more info at https://gitlab.gnome.org/Teams/Translation/Coordination/-/issues/158 The backend library .symbols file indicates one removed symbol. It has been upstream's opinion for many years that the backend library is internal API and is subject to change. gnome-control-center is the only user of the backend API for Ubuntu 24.04 LTS and it never used that symbol. There is a separate frontend library, libgoa-1.0-0b, where it would be a serious issue if symbols were removed without the soname being bumped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072782/+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 2075553] Re: gnome-text-editor crashed with SIGSEGV in editor_text_buffer_spell_adapter_invalidate_all() from editor_document_load_notify_completed_cb() from g_closure_invoke()
** Also affects: gnome-text-editor (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2075553 Title: gnome-text-editor crashed with SIGSEGV in editor_text_buffer_spell_adapter_invalidate_all() from editor_document_load_notify_completed_cb() from g_closure_invoke() from g_hash_table_lookup_node() from g_hash_table_lookup() Status in gnome-text-editor package in Ubuntu: Fix Released Status in gnome-text-editor source package in Noble: Triaged Status in gnome-text-editor source package in Oracular: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-text-editor. This problem was most recently seen with package version 46.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/063173db77d5a1e75861c722c17d8b76b960 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2075553/+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 2064656] Re: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` mul
Verified the Test Case in Ubuntu 24.04 LTS by installing package "gsettings-desktop-schemas:amd64" version "46.1-0ubuntu1" and manually updating the language files from https://translations.launchpad.net/ubuntu/noble/+source/gsettings- desktop-schemas/ ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2064656 Title: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every second for users using the lt_LT , ru_RU, Indonesian (id) and maybe other locales Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Status in gsettings-desktop-schemas source package in Noble: Fix Committed Bug description: Impact -- The systemd journal gets a lot of warnings about an incorrect translation for the default Ubuntu Desktop when used with certain languages including Georgian, Indonesian, Lithuanian, and Russian. This issue is much worse if someone has enabled the show Seconds option in the top bar clock. This issue is being fixed by packaging the new bugfix release of gsettings-desktop-schemas 46.1. There were only translation updates in this release. https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/-/compare/46.0...46.1 Test Case - 1. Open a terminal and run sudo apt install language-pack-gnome-lt 2. Close the terminal 3. Open the Settings app (gnome-control-center) 4. In the side bar, click System, then Date & Time. Turn on Seconds. 5. Close the Settings app. 6. Open the Language Support app. You can click Remind me later if you see a warning that says "The language support is not installed completely." 7. Drag Lietuvių to the top of the list. 8. Log out 9. Log back in. 10. Open a terminal and run journalctl -f. You should not see any of the clock-format warnings mentioned in the Original Bug Report below. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for gsettings-desktop-schemas. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Because gsettings-desktop-schemas is included in Ubuntu language packs, this issue is actually only fixed with a language pack update. Ubuntu currently only updates language packs shortly before Ubuntu LTS point releases. Therefore, we will need to push this update without being able to verify the Test Case first. Original Bug Report --- After upgrading to Ubuntu 24.04 LTS I ran journalctl -f and noticed that gnome-shell was spamming errors at the rate of 12 lines every second: geg. 02 18:29:19 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:19 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. My locale is lt_LT.UTF-8, but this issue appears also in ru_RU, id (Indonesian) and maybe other locales. This is caused by a mistaken translation of the quote characters in "'24h'" which is used as the default value for a particular gse
[Desktop-packages] [Bug 2072574] Re: Drop obsolete evolution-data-server notify-with-tray override
Verified ubuntu-settings=24.04.4 on Ubuntu Desktop 24.04 (Test Case 1) and Ubuntu Unity 24.04 (Test Case 2). In both cases, the Reminders window does not open until invoked through the notification. In Unity the notification is a bit weird, because it still pops up as a full window since apparently `notify-osd` spawns full windows when the notification timeout is 0. In any case the effect is that the user still gets notified, and it's in both cases less intrusive. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2072574 Title: Drop obsolete evolution-data-server notify-with-tray override Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Committed Bug description: Impact -- Calendar notifications currently pop up a full app window instead of as a normal notification. The normal notifications respect the Do Not Disturb setting, but the full app window does not. Test Case 1 --- From Ubuntu Desktop… 1. Add your Google account to GNOME Settings > Online Accounts 2. Add a calendar event to Google Calendar with a notification in advance 3. When it is time for the notification, you should see a GNOME Shell notification. You can click on the notification to see the full Reminders window. Test Case 2 --- From Ubuntu Unity 24.04 LTS… 1. Open a terminal and run this command: sudo apt install gnome-online-accounts-gtk 2. Close the terminal 3. Add a calendar event to Google Calendar with a notification in advance 4. When it is time for the notification, you should see a notification pop-up. You can click OK on the notification to see the full Reminders window. What Could Go Wrong --- The ubuntu-settings package is shipped by default with Ubuntu Desktop, Ubuntu Unity, and Edubuntu. Edubuntu is practically the same as Ubuntu Desktop as far as the desktop experience goes with one additional GNOME Shell extension to sort the Show Apps view alphabetically. This is a small default change that can be easily changed (see Revert instructions below). I guess this could go bad if someone counts on getting event notifications even though they have turned on Do Not Disturb. I'm sorry but it is intended that Do Not Disturb not show notifications like this. Other Info -- I believe this override was originally added in 2011 for Unity's benefit LP: #757805 It was also helpful for GNOME in early GNOME 3 days with the unusual messaging tray that was later dropped. These days, GNOME Shell notifications work well, better than a separate popup window. Revert to Previous Behavior --- If you prefer the original Ubuntu 24.04 LTS behavior, do one of the following: 1. Run this in a terminal: gsettings set org.gnome.evolution-data-server.calendar notify-with-tray false 2. Or install Evolution. In ☰ > Edit > Preferences > Calendar and Tasks, turn on "Display Reminder window with notifications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2072574/+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 2076977] [NEW] udisks2 failing autopkgtest with exfatprogs 1.2.5
Public bug reported: The exfatprogs 1.2.5 update cannot migrate from proposed because it's causing a regression in udisks2 autopkgtests. The udisks2 autopkgtests try to set a label that is invalid for EXFAT filesystems (according to microsoft's spec), but which exfatprogs allowed until version 1.2.5 Now that exfatprogs refuses to set an invalid label, we should fix udisks2 tests to not use an invalid label when testing EXFAT. This has already been forwarded upstream and to debian: https://github.com/storaged-project/udisks/pull/1306 https://salsa.debian.org/utopia-team/udisks2/-/merge_requests/7 ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Patch added: "udisks2_2.10.1-9ubuntu2.debdiff" https://bugs.launchpad.net/bugs/2076977/+attachment/5805695/+files/udisks2_2.10.1-9ubuntu2.debdiff ** Tags added: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2076977 Title: udisks2 failing autopkgtest with exfatprogs 1.2.5 Status in udisks2 package in Ubuntu: New Bug description: The exfatprogs 1.2.5 update cannot migrate from proposed because it's causing a regression in udisks2 autopkgtests. The udisks2 autopkgtests try to set a label that is invalid for EXFAT filesystems (according to microsoft's spec), but which exfatprogs allowed until version 1.2.5 Now that exfatprogs refuses to set an invalid label, we should fix udisks2 tests to not use an invalid label when testing EXFAT. This has already been forwarded upstream and to debian: https://github.com/storaged-project/udisks/pull/1306 https://salsa.debian.org/utopia-team/udisks2/-/merge_requests/7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2076977/+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 2076975] Re: switcherooctl and "Launch using Discrete Graphics Card" don't work in Wayland sessions with Nvidia GPUs
> it looks like it only knows how to switch GLX (Xorg sessions) and not EGL (Wayland sessions) Then why is this specific to nvidia? -- 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/2076975 Title: switcherooctl and "Launch using Discrete Graphics Card" don't work in Wayland sessions with Nvidia GPUs Status in Switcheroo Control: Unknown Status in gnome-shell package in Ubuntu: New Status in switcheroo-control package in Ubuntu: New Bug description: switcherooctl and "Launch using Discrete Graphics Card" don't work in Wayland sessions with Nvidia GPUs. Judging by the output of `switcherooctl`, it looks like it only knows how to switch GLX (Xorg sessions) and not EGL (Wayland sessions). This seems to be confirmed by the fact that GLX apps like Google Chrome are correctly launched on the discrete GPU. Just not native Wayland EGL apps. To manage notifications about this bug go to: https://bugs.launchpad.net/switcheroo-control/+bug/2076975/+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 2076975] Re: switcherooctl and "Launch using Discrete Graphics Card" don't work in Wayland sessions with Nvidia drivers
Ah well, because for mesa drivers you don't need to fiddle with glvnd. -- 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/2076975 Title: switcherooctl and "Launch using Discrete Graphics Card" don't work in Wayland sessions with Nvidia drivers Status in Switcheroo Control: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in switcheroo-control package in Ubuntu: Triaged Bug description: switcherooctl and "Launch using Discrete Graphics Card" don't work in Wayland sessions with Nvidia drivers. Judging by the output of `switcherooctl`, it looks like it only knows how to switch GLX (Xorg sessions) and not EGL (Wayland sessions). This seems to be confirmed by the fact that GLX apps like Google Chrome are correctly launched on the discrete GPU. Just not native Wayland EGL apps. To manage notifications about this bug go to: https://bugs.launchpad.net/switcheroo-control/+bug/2076975/+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 2064698] Re: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extens
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Confirmed => In Progress ** Also affects: gnome-shell-extension-appindicator (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-appindicator (Ubuntu Oracular) Importance: Undecided Assignee: Alessandro Astone (aleasto) Status: In Progress ** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble) Status: New => Triaged ** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-appindicator (Ubuntu Oracular) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2064698 Title: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extensions/ubuntu- appindicat...@ubuntu.com/dbusProxy.js:89:33] Status in gnome-shell-extension-appindicator package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator source package in Noble: Triaged Status in gnome-shell-extension-appindicator source package in Oracular: In Progress Bug description: Every session I see those errors in the attached log file. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 3 08:54:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (41 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2064698/+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 2064698] Re: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extens
** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2064698 Title: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extensions/ubuntu- appindicat...@ubuntu.com/dbusProxy.js:89:33] Status in gnome-shell-extension-appindicator package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator source package in Noble: In Progress Status in gnome-shell-extension-appindicator source package in Oracular: In Progress Bug description: Every session I see those errors in the attached log file. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 3 08:54:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (41 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2064698/+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 2064698] Re: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extens
** Description changed: + [ Impact ] + + Chromium and Electron apps implement the KStatusNotifierItem spec without exposing some DBus properties that the spec describes. + The app-indicator feature can work without those properties, but gnome-shell-extension-appindicator will log a big error message to the system journal every time the app refreshes the indicator. + + Because failing to access those properties is not fatal, we can avoid dumping an error to the system journal. Instead, we'll only print a debug message, not visible by default unless enabled with G_MESSAGES_DEBUG="Ubuntu-AppIndicators" + in the shell's environment. + + [ Test Plan ] + + Reproducing the issue involves using an Electron-based application that + uses AppIndicators. I'm going to use Mattermost as an example of one. + + * Install the mattermost-desktop snap + + * Log in + + * Click the 3-dots button on the top-left + + * Navigate to File > Settings + + * Tick `Show icon in the notification area` + + * Restart the app + + * In a terminal window start printing journal logs with `journalctl -f` + + * Get someone to send a message to any channel that you participate in. + + * Verify that the error was not logged to the journal + + [ Where problems could occur ] + + The AppIndicator extension is an important feature of Ubuntu Desktop. + If misconfigured, the extension may crash the desktop. + + The patch only touches printing logs, so should not affect the well + behavior of the extension. + + Problems can be detected by using applications that expose app- + indicators. + + [ Original Description ] + Every session I see those errors in the attached log file. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 3 08:54:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (41 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (22 days ago) ** Description changed: [ Impact ] Chromium and Electron apps implement the KStatusNotifierItem spec without exposing some DBus properties that the spec describes. The app-indicator feature can work without those properties, but gnome-shell-extension-appindicator will log a big error message to the system journal every time the app refreshes the indicator. Because failing to access those properties is not fatal, we can avoid dumping an error to the system journal. Instead, we'll only print a debug message, not visible by default unless enabled with G_MESSAGES_DEBUG="Ubuntu-AppIndicators" in the shell's environment. + The full error message can be seen in comment #3 + [ Test Plan ] Reproducing the issue involves using an Electron-based application that uses AppIndicators. I'm going to use Mattermost as an example of one. - * Install the mattermost-desktop snap + * Install the mattermost-desktop snap - * Log in + * Log in - * Click the 3-dots button on the top-left + * Click the 3-dots button on the top-left - * Navigate to File > Settings + * Navigate to File > Settings - * Tick `Show icon in the notification area` + * Tick `Show icon in the notification area` - * Restart the app + * Restart the app - * In a terminal window start printing journal logs with `journalctl -f` + * In a terminal window start printing journal logs with `journalctl -f` - * Get someone to send a message to any channel that you participate in. + * Get someone to send a message to any channel that you participate in. - * Verify that the error was not logged to the journal + * Verify that the error (comment #3) was not logged to the journal [ Where problems could occur ] The AppIndicator extension is an important feature of Ubuntu Desktop. If misconfigured, the extension may crash the desktop. The patch only touches printing logs, so should not affect the well behavior of the extension. Problems can be detected by using applications that expose app- indicators. [ Original Description ] Every session I see those errors in the attached log file. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 3 08:54:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (41 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.
[Desktop-packages] [Bug 2065294] Re: Diagnostics settings flips to Never without any user action
** Changed in: whoopsie-preferences (Ubuntu Jammy)
Status: New => Triaged
** Changed in: whoopsie-preferences (Ubuntu Noble)
Status: New => Triaged
--
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/2065294
Title:
Diagnostics settings flips to Never without any user action
Status in gnome-control-center package in Ubuntu:
Fix Released
Status in whoopsie-preferences package in Ubuntu:
Triaged
Status in gnome-control-center source package in Jammy:
Confirmed
Status in whoopsie-preferences source package in Jammy:
Triaged
Status in gnome-control-center source package in Noble:
Confirmed
Status in whoopsie-preferences source package in Noble:
Triaged
Bug description:
[ Impact ]
In GNOME Settings' Diagnostics page, the switch to control automatic
bug reporting to Canonical automatically flips to "Never" after 1
minute of the page being open without interaction
The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
A further change should be applied to the whoopsie-preferences service
to avoid quitting when there are clients still listening for potential
settings changes.
[ Test Plan ]
* Open GNOME Settings -> Privacy & Security -> Diagnostics
* You should see `Send error reports to Canonical` set to `Manual` by
default.
> If instead it is set to Never, change it now to another option.
* Stay on the settings page for more than 60 seconds
* The setting should have remained the same and *not* have
automatically changed to `Never`.
[ Where problems could occur ]
This patch also tries to re-start the "whoopsie-preferences" daemon
when it automatically stops after 60 seconds, because GNOME Settings
should keep listening for settings changes from external factors. This
should not present any issues, but it's the most "intrusive" part of
the patch.
[ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.
I noticed this on Jammy, Mantic, and Noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+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 2065294] Re: Diagnostics settings flips to Never without any user action
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5616
--
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/2065294
Title:
Diagnostics settings flips to Never without any user action
Status in gnome-control-center package in Ubuntu:
Fix Released
Status in whoopsie-preferences package in Ubuntu:
Triaged
Status in gnome-control-center source package in Jammy:
Confirmed
Status in whoopsie-preferences source package in Jammy:
Triaged
Status in gnome-control-center source package in Noble:
Confirmed
Status in whoopsie-preferences source package in Noble:
Triaged
Bug description:
[ Impact ]
In GNOME Settings' Diagnostics page, the switch to control automatic
bug reporting to Canonical automatically flips to "Never" after 1
minute of the page being open without interaction
The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
A further change should be applied to the whoopsie-preferences service
to avoid quitting when there are clients still listening for potential
settings changes.
[ Test Plan ]
* Open GNOME Settings -> Privacy & Security -> Diagnostics
* You should see `Send error reports to Canonical` set to `Manual` by
default.
> If instead it is set to Never, change it now to another option.
* Stay on the settings page for more than 60 seconds
* The setting should have remained the same and *not* have
automatically changed to `Never`.
[ Where problems could occur ]
This patch also tries to re-start the "whoopsie-preferences" daemon
when it automatically stops after 60 seconds, because GNOME Settings
should keep listening for settings changes from external factors. This
should not present any issues, but it's the most "intrusive" part of
the patch.
[ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.
I noticed this on Jammy, Mantic, and Noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+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 2076652] Re: Mouse cursor is oversized in GTK4 apps
No, it's included in the latest 4.15 dot release (4.15.5) which we're working on -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2076652 Title: Mouse cursor is oversized in GTK4 apps Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Confirmed Bug description: In Oracular in the past day or so, the mouse cursor in GTK4 apps has become too large. This happens with all cursor themes I've tried. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2076652/+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 2077313] Re: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
Did you try adding a dependency on `mesa-vulkan-drivers`?
It includes a software-only vulkan implementation which should help in testing
these code paths.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2077313
Title:
GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
Status in gtk4 package in Ubuntu:
In Progress
Bug description:
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21s killed by signal 5 SIGTRAP
gtk:gsk / scaling
ERROR0.25s killed by signal 5 SIGTRAP
<---
as per
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/16394764/+listing-
archive-extra.
The full log of memorytexture is [1]. Its backtrace is
--->
#0 0x77ecf5fa in g_log_writer_default () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x77ec6d64 in g_log_structured_array () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x77ec6fb8 in g_log_structured_standard () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x778c0db7 in gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:68
#4 gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:63
#5 gdk_display_create_vulkan_instance (display=0x555a14f0,
error=)
at ../../../gdk/gdkvulkancontext.c:1675
#6 0x77961ef3 in gdk_display_init_vulkan (display=0x555a14f0,
error=0x0)
at ../../../gdk/gdkvulkancontext.c:1771
#7 gsk_vulkan_device_get_for_display (display=0x555a14f0, error=0x0)
at ../../../gsk/gpu/gskvulkandevice.c:421
#8 0x7794c717 in gsk_gpu_renderer_realize
(renderer=0x60defa00, display=0x555a14f0, surface=0x0, error=0x0)
at ../../../gsk/gpu/gskgpurenderer.c:213
#9 0x778d863b in gsk_renderer_do_realize
(renderer=0x60defa00, display=display@entry=0x555a14f0,
surface=surface@entry=0x0, error=error@entry=0x0) at
../../../gsk/gskrenderer.c:271
#10 0x778df4c5 in gsk_renderer_realize_for_display
(renderer=, display=display@entry=0x555a14f0,
error=error@entry=0x0)
at ../../../gsk/gskrenderer.c:357
#11 0x6a41 in main (argc=, argv=)
at ../../../testsuite/gdk/memorytexture.c:1587
<---
gdkvulkancontextprivate.h:68 at #3 is nothing but the warning:
g_warning ("%s(): %s (%d)", called_function, gdk_vulkan_strerror
(res), res);
So I must conclude the test is failing because the warning is being
called, as if G_DEBUG=fatal-warnings had been passed, which it is
however not. Open questions are:
1. Why is this causing a SIGTRAP if no fatal-warnings is enabled?
2. Why do other tests (e.g. 511 gtk:reftest / reftest actionbar.ui)
that raise the same warning not fail?
Anyway, those three tests pass with vulkan-disable (number of skipped
remains unaltered) as a matter of fact. I'm proposing that as a merge
request[2] in Debian's bug tracking system.
[1] https://l.termbin.com/a0e2
[2] https://salsa.debian.org/gnome-team/gtk4/-/merge_requests/25
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077313/+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 2077530] Re: Gnome-shell suddenly doesn't load, only black screen with cursor
Could you try downgrading `ubuntu-drivers-common` to see if it's a regression there? Here's a link to the previous build: https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.7.6ubuntu3/+build/28021470/+files/ubuntu-drivers- common_0.9.7.6ubuntu3_arm64.deb -- 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/2077530 Title: Gnome-shell suddenly doesn't load, only black screen with cursor Status in gnome-shell package in Ubuntu: New Bug description: I am running 24.10 since some time. A week ago or so suddenly (after a apt-get dist-upgrade) my pc doesn't boot into Gnome anymore, it opens a black screen with only a cursor (and I hear a new audio welcome sound that wasn't there earlier, but probably not related) When I boot an older kernel, everything is fine, but I have no Nvidia driver there, so when I install that with dkms autoinstall for that older kernel, I get the same black screen as well. So it seems to be some compatibility issue between Nvidia en Gnome- Shell. There are more people on the Ubuntu Forums that have the same issue. (https://ubuntuforums.org/showthread.php?t=2499944) I am running 24.10 with 6.8.0-35. AMD Ryzen 5950X, 32GB Rram, Nvidia 4070 Ti Super --- ProblemType: Bug ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass DisplayManager: DistroRelease: Ubuntu 24.10 GsettingsChanges: InstallationDate: Installed on 2022-12-10 (620 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 47~beta-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 RelatedPackageVersions: mutter-common 47~beta-3ubuntu1 ShellJournal: -- No entries -- Tags: oracular Uname: Linux 6.8.0-35-generic x86_64 UpgradeStatus: Upgraded to oracular on 2024-06-25 (57 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077530/+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 2077530] Re: Gnome-shell suddenly doesn't load, only black screen with cursor
Sorry for the link, arm64 and amd64 are too similar looking! Thanks for the test, it's good info. -- 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/2077530 Title: Gnome-shell suddenly doesn't load, only black screen with cursor Status in gnome-shell package in Ubuntu: Confirmed Bug description: I am running 24.10 since some time. A week ago or so suddenly (after a apt-get dist-upgrade) my pc doesn't boot into Gnome anymore, it opens a black screen with only a cursor (and I hear a new audio welcome sound that wasn't there earlier, but probably not related) When I boot an older kernel, everything is fine, but I have no Nvidia driver there, so when I install that with dkms autoinstall for that older kernel, I get the same black screen as well. So it seems to be some compatibility issue between Nvidia en Gnome- Shell. There are more people on the Ubuntu Forums that have the same issue. (https://ubuntuforums.org/showthread.php?t=2499944) I am running 24.10 with 6.8.0-35. AMD Ryzen 5950X, 32GB Rram, Nvidia 4070 Ti Super --- ProblemType: Bug ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass DisplayManager: DistroRelease: Ubuntu 24.10 GsettingsChanges: InstallationDate: Installed on 2022-12-10 (620 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 47~beta-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 RelatedPackageVersions: mutter-common 47~beta-3ubuntu1 ShellJournal: -- No entries -- Tags: oracular Uname: Linux 6.8.0-35-generic x86_64 UpgradeStatus: Upgraded to oracular on 2024-06-25 (57 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077530/+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 2077451] Re: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login
https://gitlab.gnome.org/GNOME/xdg-desktop-portal- gnome/-/merge_requests/173#note_2203262 @Daniel if you're seeing this depending on patches/extensions we might have something downstream that's launching Nautilus on login, but fundamentally this is a deadlock in x-d-p-gnome upstream. ** Also affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: New => Triaged ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Tags added: udeng-4100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2077451 Title: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login Status in dbus package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Triaged Bug description: Ubuntu 24.10 just installed, after graphic screen displayed click on an icon on dock the 1st application (any application also terminal or calculator) takes 10-15 seconds to start. Then after this short period all apps starts quickly as usual. note: this problem happens also on a system installed few days ago. attaching journal ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-shell 47~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 20 18:52:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-08-20 (0 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240820) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 47~beta-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2077451/+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 2077451] Re: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login
** Changed in: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2077451 Title: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login Status in dbus package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Triaged Bug description: Ubuntu 24.10 just installed, after graphic screen displayed click on an icon on dock the 1st application (any application also terminal or calculator) takes 10-15 seconds to start. Then after this short period all apps starts quickly as usual. note: this problem happens also on a system installed few days ago. attaching journal ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-shell 47~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 20 18:52:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-08-20 (0 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240820) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 47~beta-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2077451/+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 2077451] Re: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login
** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2077451 Title: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: In Progress Bug description: Ubuntu 24.10 just installed, after graphic screen displayed click on an icon on dock the 1st application (any application also terminal or calculator) takes 10-15 seconds to start. Then after this short period all apps starts quickly as usual. note: this problem happens also on a system installed few days ago. attaching journal ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-shell 47~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 20 18:52:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-08-20 (0 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240820) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 47~beta-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2077451/+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 2078254] Re: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163.
Hey, I'm OOO for the week but I think you can upload the temporary fixes. They're all correct per se. You'd have to first upload po4a and then build pppconfig against the new version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppconfig in Ubuntu. https://bugs.launchpad.net/bugs/2078254 Title: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163. Status in pppconfig package in Ubuntu: Triaged Status in pppconfig package in Debian: New Bug description: From the oracular archive rebuild ppa: https://launchpadlibrarian.net/745205685/buildlog_ubuntu-oracular- amd64.pppconfig_2.3.28_BUILDING.txt.gz ... UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xEA" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE8" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xA0" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353. make: *** [debian/rules:12: build-stamp] Error 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppconfig/+bug/2078254/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
Very early in the boot process SimpleDRM will claim card0 as a DRM device backed by the BIOS framebuffer, mostly useful to offer Wayland-friendly graphics on systems without a GPU. When the system loads a GPU driver that brings its own framebuffer, it will automatically unload SimpleDRM. The nvidia driver doesn't yet expose a framebuffer (it's changing soon), so SimpleDRM will stick around on nvidia-only systems. On single-GPU systems without nvidia, the GPU display will be at /dev/dri/card1 and card0 won't be present because SimpleDRM was unloaded. On single-GPU systems with nvidia, the GPU display will also be at /dev/dri/card1 but card0 will stick around, causing this bug. On multi-GPU systems, the presence of any non-nvidia GPUs should trigger the automatic removal of SimpleDRM. I'm not sure about this but I think it is possible that one of the real GPUs would end up as /dev/dri/card0. To address the bug, we cannot simply unload SimpleDRM on nvidia because it also provides the system's only framebuffer at /dev/fb0, which we need for VTs and comment #37 for example. But we can remove the SimpleDRM DRM node at /dev/dri/card0 which we don't need because an actual GPU card is available at /dev/dri/card1. > don't systems with multiple video cards exist, and couldn't one be using > /dev/dri/card0? There are two conditions that need to be satisfied in order for the `rm /dev/dri/card0` action to run: 1. The nvidia proprietary driver must be loaded. Note that the nvidia driver will refuse to probe unless a nvidia GPU is present, so this implies that the nvidia hardware is available. 2. The /dev/dri/card0 device must be owned by SimpleDRM. If /dev/dri/card0 is created by another driver, the action will not be run. > During boot, when does exactly "/bin/rm /dev/dri/card0" run Whenever the nvidia driver is loaded. I'm not sure when that normally is, but it shouldn't be relevant: when any other GPU DRM driver is present, we don't need a SimpleDRM DRM node. > Also, the test plan still does not cover non-nvidia platforms, and it sounds to me like that would be crucial. The two pre-conditions that i've illustrated above will cover the non- nvidia case. The crucial point there is that the nvidia driver must refuse to load without the underlying hardware. Since that is the case, the `rm` action is not triggered. The regression potential here is that on a system with the nvidia driver installed but no GPU hardware we would remove the only DRM driver, breaking Wayland compositors. I'll add a test-plan to ensure that the driver behaves as expected. I guess this would be where testing multiple nvidia driver versions is useful. > could /dev/dri/card0 be used for non-graphical things, like servers doing GPU calculations? And in that case, removing it could break that workload? No, SimpleDRM only allows drawing one buffer to the screen. ** Description changed: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init + Beware that this has side-effects: see comment #37 - [ Test Plan ] + [ Test Plan - Nvidia case ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. + [ Test Plan - Non-Nvidia case ] + + 1. Set up a single monitor desktop with one or more GPUs, all non-nvidia. +(a KVM virtual machine with VirtIO is an easy candidate for this) + 2. Run `apt install nvidia-driver-535`. + 3. Reboot. + 4. Verify that you are able to log into the Ubuntu Desktop Wayland session. + + [ Test Plan - No-GPU case ] + + 1. Set up a single monitor desktop without any GPU. +(a virtual machine without any graphics acceleration (vmware, virtio...) is an easy candidate for this. + 2. Run `sudo apt install nvidia-driver-535`. + 3. Reboot. + 4. Verify that you are able to log into the Ubuntu Desktop Wayland session. + 5. Go back to point 2, and try with another driver version: +[nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open, nvidia-driver-550, nvidia-driver-550-open] + + [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. + +
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
** Description changed: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Beware that this has side-effects: see comment #37 [ Test Plan - Nvidia case ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Test Plan - Non-Nvidia case ] - 1. Set up a single monitor desktop with one or more GPUs, all non-nvidia. -(a KVM virtual machine with VirtIO is an easy candidate for this) + 1. Set up a machine with one or more GPUs, all non-nvidia. + (a KVM virtual machine with VirtIO is an easy candidate for this) 2. Run `apt install nvidia-driver-535`. 3. Reboot. 4. Verify that you are able to log into the Ubuntu Desktop Wayland session. [ Test Plan - No-GPU case ] - 1. Set up a single monitor desktop without any GPU. -(a virtual machine without any graphics acceleration (vmware, virtio...) is an easy candidate for this. + 1. Set up a machine without any GPU. + (a virtual machine without any graphics acceleration (vmware, virtio...) is an easy candidate for this. 2. Run `sudo apt install nvidia-driver-535`. 3. Reboot. 4. Verify that you are able to log into the Ubuntu Desktop Wayland session. 5. Go back to point 2, and try with another driver version: -[nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open, nvidia-driver-550, nvidia-driver-550-open] - + [nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open, nvidia-driver-550, nvidia-driver-550-open] [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. One case where this could happen is if the Nvidia driver would allow being loaded even without any nvidia hardware present: if that is the case, "Test Plan - No-GPU case" would fail. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems -- 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/2060268 Title: Phantom "Unknown Display" sho
[Desktop-packages] [Bug 2078674] [NEW] Please merge lp-solve 5.5.2.11-2 (main) from Debian unstable (main)
Public bug reported: 08/06/17 version 5.5.2.6 (temp release) - Modified generating MPS file with some new options: - MPSLINDO: Write semi-continious variables in different order as required by LINDO - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format xli_MPS is modified to handle these new options. - Reading an lp file with a semi-cont variable failed if the minimum is larger than the maximum. This is allowed because if the semi-cont attribute on the variables in which case a 0 is also a valid solution. - Some models with degeneraracy returned a "Unacceptable accuracy found" error. 30/07/17 version 5.5.2.7 (temp release) - Lower/Upper objective sensitivity was sometimes not given for some variables. Was ok when scaling was disabled. xx/xx/xx version 5.5.2.8 - Modified PHP driver for PHP 5.4 - In some cases an accuracy error was given by check_solution which was not always true 13/03/20 version 5.5.2.9 - When a model is infeasible it can happen that the returned solution is not initialised and returning NAN values 15/11/20 version 5.5.2.10 - write_MPS doesn't generate an SC BOUND on a variable that is semi-continious and the upper bound is equal to the lower bound. - The VB.NET demo application wasn't adapted yet for 64-bit 29/12/20 version 5.5.2.11 - version 5.5.2.9 introduced a problem for some models. They give infeasible or let even lpsolve crash. ** Affects: lp-solve (Ubuntu) Importance: Undecided Assignee: Alessandro Astone (aleasto) Status: In Progress ** Merge proposal linked: https://code.launchpad.net/~aleasto/ubuntu/+source/lp-solve/+git/lp-solve/+merge/471906 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lp-solve in Ubuntu. https://bugs.launchpad.net/bugs/2078674 Title: Please merge lp-solve 5.5.2.11-2 (main) from Debian unstable (main) Status in lp-solve package in Ubuntu: In Progress Bug description: 08/06/17 version 5.5.2.6 (temp release) - Modified generating MPS file with some new options: - MPSLINDO: Write semi-continious variables in different order as required by LINDO - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format xli_MPS is modified to handle these new options. - Reading an lp file with a semi-cont variable failed if the minimum is larger than the maximum. This is allowed because if the semi-cont attribute on the variables in which case a 0 is also a valid solution. - Some models with degeneraracy returned a "Unacceptable accuracy found" error. 30/07/17 version 5.5.2.7 (temp release) - Lower/Upper objective sensitivity was sometimes not given for some variables. Was ok when scaling was disabled. xx/xx/xx version 5.5.2.8 - Modified PHP driver for PHP 5.4 - In some cases an accuracy error was given by check_solution which was not always true 13/03/20 version 5.5.2.9 - When a model is infeasible it can happen that the returned solution is not initialised and returning NAN values 15/11/20 version 5.5.2.10 - write_MPS doesn't generate an SC BOUND on a variable that is semi-continious and the upper bound is equal to the lower bound. - The VB.NET demo application wasn't adapted yet for 64-bit 29/12/20 version 5.5.2.11 - version 5.5.2.9 introduced a problem for some models. They give infeasible or let even lpsolve crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078674/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
** Description changed: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Beware that this has side-effects: see comment #37 [ Test Plan - Nvidia case ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Test Plan - Non-Nvidia case ] 1. Set up a machine with one or more GPUs, all non-nvidia. (a KVM virtual machine with VirtIO is an easy candidate for this) 2. Run `apt install nvidia-driver-535`. 3. Reboot. 4. Verify that you are able to log into the Ubuntu Desktop Wayland session. [ Test Plan - No-GPU case ] 1. Set up a machine without any GPU. (a virtual machine without any graphics acceleration (vmware, virtio...) is an easy candidate for this. 2. Run `sudo apt install nvidia-driver-535`. 3. Reboot. 4. Verify that you are able to log into the Ubuntu Desktop Wayland session. 5. Go back to point 2, and try with another driver version: [nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open, nvidia-driver-550, nvidia-driver-550-open] + + [ Test Plan - Nvidia+LUKS ] + + 1. Set up a machine with an Nvidia GPU and encrypted disk. + 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. + 3. Reboot + 4. Verify that you see the password prompt for decrypting the disk. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. One case where this could happen is if the Nvidia driver would allow being loaded even without any nvidia hardware present: if that is the case, "Test Plan - No-GPU case" would fail. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems -- 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/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-
[Desktop-packages] [Bug 2078715] Re: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular
sbuild targeting noble ** Attachment added: "lp-solve.sbuild.log" https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078715/+attachment/5812374/+files/lp-solve.sbuild.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lp-solve in Ubuntu. https://bugs.launchpad.net/bugs/2078715 Title: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular Status in lp-solve package in Ubuntu: New Bug description: [ Why ] The current version of lp-solve in Ubuntu fails to build with gcc 14 due to new warnings. The version in debian has already resolved this issue, but was not imported into Ubuntu automatically because it had deviated from debian. We can merge back with debian to achieve the following: * Many bugfixes from upstream * Fix the FTBFS with gcc 14 * Re-align with debian Attaching the upstream changelog diff. This is a new minor version, but a Freeze Exception might be necessary because two new options were added: +- Modified generating MPS file with some new options: + - MPSLINDO: Write semi-continious variables in different order as required by LINDO + - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format +xli_MPS is modified to handle these new options. Because the new options wouldn't be used by any existing projects, i believe it is safe to upgrade to the new version. However if this is rejected I will just propose backporting the FTBFS fix to the Ubuntu package, and we can backport more fixes as requested. [ Test ] $ cat
[Desktop-packages] [Bug 2078715] [NEW] [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular
Public bug reported: [ Why ] The current version of lp-solve in Ubuntu fails to build with gcc 14 due to new warnings. The version in debian has already resolved this issue, but was not imported into Ubuntu automatically because it had deviated from debian. We can merge back with debian to achieve the following: * Many bugfixes from upstream * Fix the FTBFS with gcc 14 * Re-align with debian Attaching the upstream changelog diff. This is a new minor version, but a Freeze Exception might be necessary because two new options were added: +- Modified generating MPS file with some new options: + - MPSLINDO: Write semi-continious variables in different order as required by LINDO + - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format +xli_MPS is modified to handle these new options. Because the new options wouldn't be used by any existing projects, i believe it is safe to upgrade to the new version. However if this is rejected I will just propose backporting the FTBFS fix to the Ubuntu package, and we can backport more fixes as requested. [ Test ] $ cat
[Desktop-packages] [Bug 2078715] Re: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular
** Attachment added: "lp-solve.install.log" https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078715/+attachment/5812375/+files/lp-solve.install.log ** Description changed: [ Why ] The current version of lp-solve in Ubuntu fails to build with gcc 14 due to new warnings. The version in debian has already resolved this issue, but was not imported into Ubuntu automatically because it had deviated from debian. We can merge back with debian to achieve the following: * Many bugfixes from upstream * Fix the FTBFS with gcc 14 * Re-align with debian Attaching the upstream changelog diff. This is a new minor version, but a Freeze Exception might be necessary because two new options were added: +- Modified generating MPS file with some new options: + - MPSLINDO: Write semi-continious variables in different order as required by LINDO + - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format +xli_MPS is modified to handle these new options. Because the new options wouldn't be used by any existing projects, i believe it is safe to upgrade to the new version. However if this is rejected I will just propose backporting the FTBFS fix to the Ubuntu package, and we can backport more fixes as requested. [ Test ] + $ cat
[Desktop-packages] [Bug 2078715] Re: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular
** Attachment added: "lp-solve.sbuild.log" https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078715/+attachment/5812376/+files/lp-solve.sbuild.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lp-solve in Ubuntu. https://bugs.launchpad.net/bugs/2078715 Title: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular Status in lp-solve package in Ubuntu: New Bug description: [ Why ] The current version of lp-solve in Ubuntu fails to build with gcc 14 due to new warnings. The version in debian has already resolved this issue, but was not imported into Ubuntu automatically because it had deviated from debian. We can merge back with debian to achieve the following: * Many bugfixes from upstream * Fix the FTBFS with gcc 14 * Re-align with debian Attaching the upstream changelog diff. This is a new minor version, but a Freeze Exception might be necessary because two new options were added: +- Modified generating MPS file with some new options: + - MPSLINDO: Write semi-continious variables in different order as required by LINDO + - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format +xli_MPS is modified to handle these new options. Because the new options wouldn't be used by any existing projects, i believe it is safe to upgrade to the new version. However if this is rejected I will just propose backporting the FTBFS fix to the Ubuntu package, and we can backport more fixes as requested. [ Test ] $ cat
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
** Description changed: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Beware that this has side-effects: see comment #37 [ Test Plan - Nvidia case ] 1. Set up a DESKTOP where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Regression Test Plan - Intel/AMD graphics ] 1. Set up a machine with integrated graphics only. 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. [ Regression Test Plan - Virtual machines ] 1. Set up a virtual machine without any graphics acceleration (vmware, virtio...) 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `sudo apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. 7. Optionally go back to point 4, and try with nvidia-driver-550. [ Regression Test Plan - Nvidia+LUKS ] 1. Set up a desktop machine (not a laptop) with an Nvidia GPU and encrypted disk. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot 4. Verify that you see the password prompt for decrypting the disk. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. One case where this could happen is if the Nvidia driver would allow being loaded even without any nvidia hardware present: if that is the - case, "Test Plan - No-GPU case" would fail. + case, "Regression Test Plan - Virtual machines" would fail. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems -- 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/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu:
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
Verified [ Regression Test Plan - Virtual Machines ] with ubuntu-drivers-common 1:0.9.7.6ubuntu3.1 on Ubuntu 24.04 LTS by using KVM: ``` ``` Even with nvidia-driver-535 or nvidia-driver-550 installed, the system has kept access to SimpleDRM and can still boot a Wayland session. -- 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/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Noble: Fix Committed Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Beware that this has side-effects: see comment #37 [ Test Plan - Nvidia case ] 1. Set up a DESKTOP where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Regression Test Plan - Intel/AMD graphics ] 1. Set up a machine with integrated graphics only. 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. [ Regression Test Plan - Virtual machines ] 1. Set up a virtual machine without any graphics acceleration (vmware, virtio...) 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `sudo apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. 7. Optionally go back to point 4, and try with nvidia-driver-550. [ Regression Test Plan - Nvidia+LUKS ] 1. Set up a desktop machine (not a laptop) with an Nvidia GPU and encrypted disk. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot 4. Verify that you see the password prompt for decrypting the disk. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. One case where this could happen is if the Nvidia driver would allow being loaded even without any nvidia hardware present: if that is the case, "Regression Test Plan - Virtual machines" would fail. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: In
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
Verified [ Regression Test Plan - Intel/AMD graphics ] with ubuntu- drivers-common 1:0.9.7.6ubuntu3.1 on Ubuntu 24.04.1 LTS on an AMD thinkpad. -- 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/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Noble: Fix Committed Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Beware that this has side-effects: see comment #37 [ Test Plan - Nvidia case ] 1. Set up a DESKTOP where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Regression Test Plan - Intel/AMD graphics ] 1. Set up a machine with integrated graphics only. 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. [ Regression Test Plan - Virtual machines ] 1. Set up a virtual machine without any graphics acceleration (vmware, virtio...) 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `sudo apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. 7. Optionally go back to point 4, and try with nvidia-driver-550. [ Regression Test Plan - Nvidia+LUKS ] 1. Set up a desktop machine (not a laptop) with an Nvidia GPU and encrypted disk. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot 4. Verify that you see the password prompt for decrypting the disk. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. One case where this could happen is if the Nvidia driver would allow being loaded even without any nvidia hardware present: if that is the case, "Regression Test Plan - Virtual machines" would fail. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.vers
[Desktop-packages] [Bug 2078812] [NEW] lerc: FTBFS with gcc-14
Public bug reported: >From the test rebuild, lerc failed to rebuild on ppc64el: https://launchpadlibrarian.net/745205771/buildlog_ubuntu-oracular- ppc64el.lerc_4.0.0+ds-4ubuntu2_BUILDING.txt.gz gcc-14 has introduced a regression which causes it to crash when compiling valid code: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116460 ** Affects: gcc Importance: Unknown Status: Unknown ** Affects: gcc-14 (Ubuntu) Importance: Undecided Assignee: Alessandro Astone (aleasto) Status: New ** Affects: lerc (Ubuntu) Importance: Undecided Assignee: Alessandro Astone (aleasto) Status: New ** Also affects: gcc-14 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GCC Bugzilla #116460 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116460 ** Also affects: gcc via https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116460 Importance: Unknown Status: Unknown ** Changed in: lerc (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: gcc-14 (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lerc in Ubuntu. https://bugs.launchpad.net/bugs/2078812 Title: lerc: FTBFS with gcc-14 Status in gcc: Unknown Status in gcc-14 package in Ubuntu: New Status in lerc package in Ubuntu: New Bug description: From the test rebuild, lerc failed to rebuild on ppc64el: https://launchpadlibrarian.net/745205771/buildlog_ubuntu-oracular- ppc64el.lerc_4.0.0+ds-4ubuntu2_BUILDING.txt.gz gcc-14 has introduced a regression which causes it to crash when compiling valid code: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116460 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/2078812/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
Verified [ Regression Test Plan - Virtual Machines ] with ubuntu- drivers-common 1:0.9.6.2~0.22.04.7 on Ubuntu 22.04.4 LTS -- 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/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Noble: Fix Committed Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Beware that this has side-effects: see comment #37 [ Test Plan - Nvidia case ] 1. Set up a DESKTOP where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Regression Test Plan - Intel/AMD graphics ] 1. Set up a machine with integrated graphics only. 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. [ Regression Test Plan - Virtual machines ] 1. Set up a virtual machine without any graphics acceleration (vmware, virtio...) 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `sudo apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. 7. Optionally go back to point 4, and try with nvidia-driver-550. [ Regression Test Plan - Nvidia+LUKS ] 1. Set up a desktop machine (not a laptop) with an Nvidia GPU and encrypted disk. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot 4. Verify that you see the password prompt for decrypting the disk. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. One case where this could happen is if the Nvidia driver would allow being loaded even without any nvidia hardware present: if that is the case, "Regression Test Plan - Virtual machines" would fail. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi
[Desktop-packages] [Bug 2080073] Re: 47rc: unable to resize mattermost, discord windows
Can you try https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3997 ? -- 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/2080073 Title: 47rc: unable to resize mattermost, discord windows Status in mutter package in Ubuntu: New Bug description: After installing gnome-shell & mutter 47~rc from Salsa and logging in, I am unable to resize or maximize my Mattermost and Discord windows. These are Snap apps. I am able to resize my Element and Telegram windows. Those are also Snap apps. This bug only affects the Wayland session. I do not experience this bug with the Ubuntu on Xorg session. The issue goes away if I revert to oracular's 47~beta packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2080073/+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 2078721] Re: nautilus crashed with SIGSEGV
** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/2078721 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Confirmed Bug description: This crash happened while trying to attach monitors.xml in bug 2078060, using the file portal I believe and searching in there ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: nautilus 1:47~beta.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Sep 2 18:41:28 2024 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-11-26 (646 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5922257b1ac9:mov(%rax),%rbx PC (0x5922257b1ac9) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SignalName: SIGSEGV SourcePackage: nautilus StacktraceTop: ?? () ?? () ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo separator: usr_lib_nautilus: file-roller 44.3-1 nautilus-extension-gnome-terminal 3.52.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2078721/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
> So the only real issue now is; why would GNOME default to launching apps on the discrete GPU instead of the integrated GPU? That's expected for EGL apps, because `/usr/share/glvnd/egl_vendor.d/10_nvidia.json` comes before `/usr/share/glvnd/egl_vendor.d/50_nvidia.json`. switcherooctl also does not support switching EGL vendor at the moment. -- 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/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2080282/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
> This needs verifying in Oracular to see if it's still the case. It is behaving as designed. Because NVIDIA has priority in EGL, it will always be tried first. Without libnvidia-egl-wayland1 it fails so the second driver is probed, MESA. > If the maintainer of the nvidia-graphics-drivers-550 source package could remove "libnvidia-egl-wayland1" as a dependency for the "libnvidia-gl-550" package in jammy (as was the case before), this issue should probably be resolved. > I believe that's the fix. Breaking the NVIDIA driver cannot be the fix ;) What we probably want is to fix switcheroo, and make gnome-shell always use switcheroo rather than only for "Launch Using Discrete GPU" -- 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/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in egl-wayland package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in switcheroo-control package in Ubuntu: New Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2080282/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
>From the GLVND documentation: > EGL can't rely on asking an X server for a vendor name like GLX can, so instead, it enumerates and loads every available vendor library. Loading every vendor is also needed to support extensions such as EGL_EXT_device_enumeration. > When the application calls eglGetPlatformDisplay, EGL will simply call into each vendor library until it finds one that succeeds. After that, whichever vendor succeeded owns that display. ** Also affects: switcheroo-control (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in egl-wayland package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in switcheroo-control package in Ubuntu: New Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2080282/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: switcheroo-control (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: switcheroo-control (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- 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/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in egl-wayland package in Ubuntu: New Status in gnome-shell package in Ubuntu: Triaged Status in switcheroo-control package in Ubuntu: Triaged Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2080282/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
** Tags added: udeng-1202 -- 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/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in egl-wayland package in Ubuntu: New Status in gnome-shell package in Ubuntu: Triaged Status in switcheroo-control package in Ubuntu: Triaged Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2080282/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
Right, as Daniel said in comment #2 the issue about apps failing to launch on NVIDIA+Wayland is tracked in bug 1965563 and already resolved in noble (but not in jammy). So this thread is now only tracking the bug which causes apps to be launched on the NVIDIA GPU by default in hybrid systems, rather than defaulting to the integrated GPU. -- 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/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in egl-wayland package in Ubuntu: New Status in gnome-shell package in Ubuntu: Triaged Status in switcheroo-control package in Ubuntu: Triaged Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2080282/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
egl-wayland >= 1.1.10 basically just disables itself on hybrid systems: the driver refuses to use a GPU that is not the compositor's primary GPU; so this bug does not happen when bug 1965563 is fixed. -- Note that this means that "Launch using Discrete GPU" wouldn't work even if switcheroo-control was changed to configure EGL like it does GLX. NVIDIA does intend to eventually allow egl-wayland to work on hybrid systems, but I don't see any time commitment. MESA instead should already default to using the compositor's primary GPU when DRI_PRIME is unset; so this bug should not be present on hybrid systems with non-NVIDIA discrete GPUs either. For now, lowering the priority. ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low ** Changed in: switcheroo-control (Ubuntu) Importance: Medium => Low -- 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/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in egl-wayland package in Ubuntu: New Status in gnome-shell package in Ubuntu: Triaged Status in switcheroo-control package in Ubuntu: Triaged Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2080282/+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 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU
*** This bug is a duplicate of bug 1965563 *** https://bugs.launchpad.net/bugs/1965563 > NVIDIA does intend to eventually allow egl-wayland to work on hybrid systems, but I don't see any time commitment. Scratch that, it seems supported by setting __NV_PRIME_RENDER_OFFLOAD. Which switcheroo-control already does correctly. So I guess there isn't much to fix here. It barely works, but it still works. Finally, this bug was indeed a duplicate of bug 1965563 ** This bug has been marked a duplicate of bug 1965563 GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions -- 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/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in egl-wayland package in Ubuntu: New Status in gnome-shell package in Ubuntu: Triaged Status in switcheroo-control package in Ubuntu: Triaged Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2080282/+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 2080838] [NEW] No option to change session type to Wayland in KVM since kernel 6.8
Public bug reported: My Jammy install in KVM does not offer the option to log-in to the GNOME Wayland session when booting kernel 6.8.0-44-generic. Kernel 6.5.0 instead gives the option. I've tried to use both QXL and Virtio as video drivers, both of which offer KMS capabilities, and neither works. `/dev/dri/card1` exists. `/run/udev/gdm-machine-has-hardware-gpu` `/run/udev/gdm-machine-has-hybrid-graphics` `/run/udev/gdm-machine-has-virtual-gpu` all exist, which is not right. This is likely due to the new SimpleDRM driver included in kernel 6.8.0, which causes the primary GPU device to show up as `card1` rather than `card0`. https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/198 looks like it should fix the issue of misdetecting this system as a hybrid graphics system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7.22.04.4 ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 16 12:11:26 2024 InstallationDate: Installed on 2024-08-08 (39 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: gdm3 (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Affects: gdm3 (Ubuntu Oracular) Importance: Undecided Status: Fix Released ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2080838 Title: No option to change session type to Wayland in KVM since kernel 6.8 Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: New Status in gdm3 source package in Noble: Fix Released Status in gdm3 source package in Oracular: Fix Released Bug description: My Jammy install in KVM does not offer the option to log-in to the GNOME Wayland session when booting kernel 6.8.0-44-generic. Kernel 6.5.0 instead gives the option. I've tried to use both QXL and Virtio as video drivers, both of which offer KMS capabilities, and neither works. `/dev/dri/card1` exists. `/run/udev/gdm-machine-has-hardware-gpu` `/run/udev/gdm-machine-has-hybrid-graphics` `/run/udev/gdm-machine-has-virtual-gpu` all exist, which is not right. This is likely due to the new SimpleDRM driver included in kernel 6.8.0, which causes the primary GPU device to show up as `card1` rather than `card0`. https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/198 looks like it should fix the issue of misdetecting this system as a hybrid graphics system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7.22.04.4 ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 16 12:11:26 2024 InstallationDate: Installed on 2024-08-08 (39 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2080838/+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 2080838] Re: No option to change session type to Wayland in KVM since kernel 6.8
** Attachment added: "drm_info" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2080838/+attachment/5817864/+files/drm.info ** Also affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Oracular) Importance: Undecided Status: New ** No longer affects: gdm3 (Ubuntu Focal) ** Changed in: gdm3 (Ubuntu Noble) Status: New => Fix Released ** Changed in: gdm3 (Ubuntu Oracular) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2080838 Title: No option to change session type to Wayland in KVM since kernel 6.8 Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: New Status in gdm3 source package in Noble: Fix Released Status in gdm3 source package in Oracular: Fix Released Bug description: My Jammy install in KVM does not offer the option to log-in to the GNOME Wayland session when booting kernel 6.8.0-44-generic. Kernel 6.5.0 instead gives the option. I've tried to use both QXL and Virtio as video drivers, both of which offer KMS capabilities, and neither works. `/dev/dri/card1` exists. `/run/udev/gdm-machine-has-hardware-gpu` `/run/udev/gdm-machine-has-hybrid-graphics` `/run/udev/gdm-machine-has-virtual-gpu` all exist, which is not right. This is likely due to the new SimpleDRM driver included in kernel 6.8.0, which causes the primary GPU device to show up as `card1` rather than `card0`. https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/198 looks like it should fix the issue of misdetecting this system as a hybrid graphics system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7.22.04.4 ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 16 12:11:26 2024 InstallationDate: Installed on 2024-08-08 (39 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2080838/+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 2078721] Re: nautilus crashed with SIGSEGV
** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released -- 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/2078721 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Fix Released Bug description: This crash happened while trying to attach monitors.xml in bug 2078060, using the file portal I believe and searching in there ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: nautilus 1:47~beta.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Sep 2 18:41:28 2024 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-11-26 (646 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5922257b1ac9:mov(%rax),%rbx PC (0x5922257b1ac9) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SignalName: SIGSEGV SourcePackage: nautilus StacktraceTop: ?? () ?? () ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo separator: usr_lib_nautilus: file-roller 44.3-1 nautilus-extension-gnome-terminal 3.52.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2078721/+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 2083593] Re: Settings portal reports enable-animations as false when they are enabled in GSettings
> When I'm at the machine, I'll try to check whether it thinks there's
no hardware acceleration.
$ gdbus introspect --session --dest org.gnome.Shell.Introspect --object-path
/org/gnome/Shell/Introspect --only-properties
node /org/gnome/Shell/Introspect {
interface org.gnome.Shell.Introspect {
properties:
readonly b AnimationsEnabled = true;
readonly (ii) ScreenSize = (1920, 1080);
readonly u version = 3;
};
};
That shows animations enabled so the issue is somewhere else, possibly
between the synchronization of gnome-shell with the portal.
--
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/2083593
Title:
Settings portal reports enable-animations as false when they are
enabled in GSettings
Status in xdg-desktop-portal package in Ubuntu:
New
Bug description:
Last week, I did a clean install of Ubuntu 24.04 LTS on a relatively
beefy Thinkpad. This is going to be my Linux build machine (for a game
I'm working on) so I installed only a few things: VSCode, Steam,
Caffeine, Timeshift, and the requirements for building the game
(Flutter SDK, development libraries).
While testing the game, I noticed that all animations in the game are
skipped. I checked what the app thinks about the environment and it
reports animations in the OS as disabled. I double-checked that
they're not.
1. They are not disabled in Settings > Accessibility.
2. `gsettings get org.gnome.desktop.interface enable-animations`
returns `true`
3. `dconf read /org/gnome/desktop/interface/enable-animations` returns
`true`
Yet, I get this when using `gdbus`:
```
$ gdbus call --session --dest org.freedesktop.portal.Desktop --object-path
/org/freedesktop/portal/desktop --method org.freedesktop.portal.Settings.Read
org.gnome.desktop.interface enable-animations
(<>,)
```
Apparently, `gdbus` is where some applications are looking when trying
to figure out whether animations are enabled. From what I understand,
this is _the_ correct way, even.
Yesterday, I tried installing Ubuntu from scratch and I reproduced the
issue on the clean OS install as well, so it's not something I botched
along the way. You can see my screenshot gallery here:
https://github.com/flutter/flutter/issues/155982#issuecomment-2387958637
. This issue seems to not appear in installations of Ubuntu that were
upgraded from version 22.04, only in clean installations of Ubuntu
24.04.
Another person on Mastodon was able to reproduce this issue, too:
https://mastodon.social/@sesiv...@vivaldi.net/113238290862309705
I also asked this as a question on askubuntu
(https://askubuntu.com/questions/1528661/clean-ubuntu-install-reports-
enable-animations-as-false-when-theyre-enabled) but, in retrospect, I
think this is a bug in the system, not a support question. I know I
can fix this for myself but I want this to work as expected for
others.
System:
```
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04.1 LTS
Release: 24.04
```
## Expected
gdbus (or whatever the subsystem that gdbus uses) returns the correct
value for animations enabled/disabled state
## What happens instead
gdbus returns false while everything else returns true
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libglib2.0-bin 2.80.0-6ubuntu3.1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 3 11:18:41 2024
InstallationDate: Installed on 2024-10-02 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: glib2.0
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/+bug/2083593/+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 2083869] Re: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings
Thank you for the bug report. I've verified the issue and understand the cause. ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Milestone: None => ubuntu-24.04.1 ** Also affects: gnome-control-center (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: gnome-control-center (Ubuntu) Milestone: ubuntu-24.04.1 => oracular-updates ** Changed in: gnome-control-center (Ubuntu Noble) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: gnome-control-center (Ubuntu Noble) Status: New => Triaged ** Tags added: udeng-4903 -- 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/2083869 Title: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center source package in Noble: Triaged Bug description: Context: I usually set the lock delay to 30 minutes, and do it via gsettings since GNOME Settings allows values of 15 min max. Problem: This value is reset to "uint32 0" (zero) when I click the tab Privacy & Security in GNOME Settings. Since the change happens silently the user will not be aware of it. Example to replicate: 1. Open terminal and set a custom delay value (30 min in this case): $ gsettings set org.gnome.desktop.session idle-delay 1800 2. Monitor the key for change: $ gsettings monitor org.gnome.desktop.session idle-delay 3. Open GNOME Settings and click "Privacy & Security" 4. The key is changed, on step 3, to "uint32 0" as seen in the terminal monitoring the key: $ gsettings monitor org.gnome.desktop.session idle-delay idle-delay: uint32 0 More info: The option to lock the screen after a delay can be set in (at least) three different locations: 1. Settings -> Power -> Screen Blank 2. Settings -> Privacy & Security -> Screen Lock -> Blank Screen Delay 3. $ gsettings set org.gnome.desktop.session idle-delay 1800 (1 and 2 are drop-down lists going from "Never" up to "15 minutes". In 3, I used "1800" = 30 min.) The issue only happens when I click the tab "Privacy & Settings" (I believe this tab is new in Ubuntu 24.04, I don't recall seeing it in 20.04 or 22.04). I can click all other tabs, including the tab "Power", without problem. I was able to replicate the issue in another laptop, also with Ubuntu 24.04. Machine details: $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 46.0-0ubuntu6~24.04.5 Candidate: 46.0-0ubuntu6~24.04.5 Version table: *** 46.0-0ubuntu6~24.04.5 500 500 http://pt.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 46.0-0ubuntu6~24.04.3 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 46.0-0ubuntu5 500 500 http://pt.archive.ubuntu.com/ubuntu noble/main amd64 Packages $ apt-cache policy gnome-screensaver gnome-screensaver: Installed: (none) Candidate: 3.6.1-13ubuntu4 Version table: 3.6.1-13ubuntu4 500 500 http://pt.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Note I thought the idle-delay was part of package gnome-screensaver but it turns out I don't even have it installed. The package description says "This package is not necessary in the GNOME desktop environment, because GNOME Shell contains its own screen lock implementation. (...)" so I filled this bug under gnome-shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2083869/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Changed in: nautilus (Ubuntu) Status: Fix Released => In Progress ** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: Won't Fix Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Jammy: New Status in nautilus source package in Noble: In Progress Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Description changed: Can't move file/directory by drag and drop by using a touch monitor + + As of 24.10 you can drag a file around but you cannot drop it into a + directory. OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: Won't Fix Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Jammy: New Status in nautilus source package in Noble: In Progress Bug description: Can't move file/directory by drag and drop by using a touch monitor As of 24.10 you can drag a file around but you cannot drop it into a directory. OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 2084554] [NEW] touchscreen drag-select is interrupted by context menu
Public bug reported: After 0.5s of starting a multi-file selection by dragging from an empty space, the action is interrupted by the context menu opening. ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: nautilus (Ubuntu Noble) Importance: Undecided Assignee: Alessandro Astone (aleasto) Status: In Progress ** Tags: udeng-4891 ** Also affects: nautilus (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: New => Fix Released ** Changed in: nautilus (Ubuntu Noble) Status: New => In Progress ** Changed in: nautilus (Ubuntu Noble) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: nautilus (Ubuntu Noble) Milestone: None => noble-updates ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2872 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872 Importance: Unknown Status: Unknown -- 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/2084554 Title: touchscreen drag-select is interrupted by context menu Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Noble: In Progress Bug description: After 0.5s of starting a multi-file selection by dragging from an empty space, the action is interrupted by the context menu opening. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2084554/+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 2084554] Re: touchscreen drag-select is interrupted by context menu
** Tags added: udeng-4891 -- 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/2084554 Title: touchscreen drag-select is interrupted by context menu Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Noble: In Progress Bug description: After 0.5s of starting a multi-file selection by dragging from an empty space, the action is interrupted by the context menu opening. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2084554/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags removed: udeng-4073 ** Tags added: udeng-4959 -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: Won't Fix Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Jammy: New Status in nautilus source package in Noble: In Progress Bug description: Can't move file/directory by drag and drop by using a touch monitor As of 24.10 you can drag a file around but you cannot drop it into a directory. OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Also affects: nautilus (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: mutter (Ubuntu Noble) ** No longer affects: mutter (Ubuntu Jammy) ** Changed in: nautilus (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: mutter (Ubuntu) Status: New => Won't Fix ** Changed in: nautilus (Ubuntu) Status: Won't Fix => Fix Released ** Changed in: nautilus (Ubuntu Noble) Status: New => In Progress ** Changed in: nautilus (Ubuntu Noble) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: nautilus (Ubuntu) Importance: Low => High ** Changed in: nautilus (Ubuntu Noble) Importance: Undecided => High -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: Won't Fix Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: New Status in nautilus source package in Noble: In Progress Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 2058444] Re: appchooserdialog Failed to start software when launching gnome-software
** Changed in: xdg-desktop-portal-gtk (Ubuntu) Status: Triaged => In Progress ** Changed in: xdg-desktop-portal-gtk (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2058444 Title: appchooserdialog Failed to start software when launching gnome- software Status in xdg-desktop-portal-gnome package in Ubuntu: In Progress Status in xdg-desktop-portal-gtk package in Ubuntu: In Progress Bug description: App chooser triggered non exist gnome-software when press "Find more in Software" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230510-27 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-29 (295 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230510-27 Package: xdg-desktop-portal-gtk 1.14.0-1build1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Tags: wayland-session jammy uec-images Uname: Linux 6.5.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2058444/+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 2058444] Re: appchooserdialog Failed to start software when launching gnome-software
** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: Triaged => In Progress ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2058444 Title: appchooserdialog Failed to start software when launching gnome- software Status in xdg-desktop-portal-gnome package in Ubuntu: In Progress Status in xdg-desktop-portal-gtk package in Ubuntu: Triaged Bug description: App chooser triggered non exist gnome-software when press "Find more in Software" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230510-27 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-29 (295 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230510-27 Package: xdg-desktop-portal-gtk 1.14.0-1build1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Tags: wayland-session jammy uec-images Uname: Linux 6.5.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2058444/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
Indeed installing mesa 24.2 in the snap resolves the issue. However the patch that was linked in the mesa bug alone does not: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29124 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in firefox package in Ubuntu: New Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2083538/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
I don't think there's interest in upgrading mesa in jammy at this point so here comes a 4-versions-across bisect 😰 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in firefox package in Ubuntu: New Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2083538/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
** Also affects: mesa (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Jammy) Status: New => In Progress ** Changed in: mesa (Ubuntu Jammy) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: mesa (Ubuntu Noble) Status: New => In Progress ** Changed in: mesa (Ubuntu Noble) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: mesa (Ubuntu) Status: In Progress => Fix Released ** No longer affects: firefox (Ubuntu Jammy) ** No longer affects: firefox (Ubuntu Noble) ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Noble) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in Linux: Unknown Status in Mesa: Unknown Status in firefox package in Ubuntu: Triaged Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Status in mesa source package in Noble: In Progress Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2083538/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
Proposing a backport to jammy ** Patch added: "mesa_23.2.1-1ubuntu3.1~22.04.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+attachment/5826285/+files/mesa_23.2.1-1ubuntu3.1~22.04.3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in Linux: Fix Released Status in Mesa: Fix Released Status in firefox package in Ubuntu: Triaged Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Status in mesa source package in Noble: In Progress Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2083538/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
Bisected: https://gitlab.freedesktop.org/mesa/mesa/-/commit/bceb2328c48a3eb8a9039911393fb2a7c23d5ad1 It fixes both green artifacts and crashing ** Changed in: mesa (Ubuntu) Status: New => In Progress ** Changed in: firefox (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11624 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11624 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/11624 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in Mesa: Unknown Status in firefox package in Ubuntu: Triaged Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: In Progress Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2083538/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
Yeah I'll handle the SRU template. Please coordinate the upload with tjaalton who's looking into the raspi enablement patches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in Linux: Fix Released Status in Mesa: Fix Released Status in firefox package in Ubuntu: Triaged Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Status in mesa source package in Noble: In Progress Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2083538/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
** Description changed: + [ Impact ] + + * amdgpu changes in kernel 6.11 make VAAPI video playback crash the GPU + and bring down the whole system. + + * A fix was shipped in mesa 24.2, which is already in Oracular - the + only version with kernel 6.11 currently, but snaps bundle their own + version of mesa so core22 snaps like Firefox are affected. Firefox has + VAAPI disabled by default, but it can be enabled by the user. + + [ Test Plan ] + + * Set up a system with an AMD GPU running Ubuntu 24.10 with kernel 6.11 + + * Open Firefox + + * Navigate to `about:config` + + * Search `media.ffmpeg.vaapi.enabled` + + * Enable the setting by clicking the toggle button + + * Restart Firefox + + * Play different videos on x.com or youtube.com +(I don't have a reliable reproducer unfortunately) + + * Ensure that there are no green artifacts on the video playback + + * Ensure that the system didn't lock up + + * 10 minutes of scrolling through videos was generally enough to trigger +the bug in my testing + + [ Where problems could occur ] + + * The scope of the change is limited to the VAAPI driver for AMD GPUs +( /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so ) +An issue with the change may break video playback. +But, as this bug demonstrated, a bug in the video acceleration driver +may also bring down the whole system... + + [ Original Description ] + It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: - linux-restricted-modules-6.11.0-8-generic N/A - linux-backports-modules-6.11.0-8-generic N/A - linux-firmware20240913.gita34e7a5f-0ubuntu2 + linux-restricted-modules-6.11.0-8-generic N/A + linux-backports-modules-6.11.0-8-generic N/A + linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO ** Description changed: [ Impact ] - * amdgpu changes in kernel 6.11 make VAAPI video playback crash the GPU + * amdgpu changes in kernel 6.11 make VAAPI video playback crash the GPU and bring down the whole system. - * A fix was shipped in mesa 24.2, which is already in Oracular - the + * A fix was shipped in mesa 24.2, which is already in Oracular - the only version with kernel 6.11 currently, but snaps bundle their own version of mesa so core22 snaps like Firefox are affected. Firefox has VAAPI disabled by default, but it can be enabled by the user. [ Test Plan ] - * Set up a system with an AMD GPU running Ubuntu 24.10 with kernel 6.11 + * Set up a system with an AMD GPU running Ubuntu 24.10 with kernel 6.11 - * Open Firefox + * Open Firefox - * Navigate to `about:config` + * Navigate to `about:config` - * Search `media.ffmpeg.vaapi.enabled` + * Search `media.ffmpeg.vaapi.enabled` - * Enable the setting by clicking the toggle
[Desktop-packages] [Bug 2083869] Re: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings
** Description changed: - Context: - - I usually set the lock delay to 30 minutes, and do it via gsettings since GNOME Settings allows values of 15 min max. + [ Impact ] - Problem: - - This value is reset to "uint32 0" (zero) when I click the tab Privacy & Security in GNOME Settings. Since the change happens silently the user will not be aware of it. + I usually set the lock delay to 30 minutes, and do it via gsettings + since GNOME Settings allows values of 15 min max. - Example to replicate: - + This value is reset to "uint32 0" (zero) when I click the tab Privacy & + Security in GNOME Settings. Since the change happens silently the user + will not be aware of it. - 1. Open terminal and set a custom delay value (30 min in this case): + This is fixed by ensuring that custom idle-delay values, not listed in the + `Privacy & Security -> Screen Lock -> Blank Screen Delay` drop-down, are handled gracefully. If the value is not in the list, the drop-down will default to + showing no selection instead of falling back to zero. - $ gsettings set org.gnome.desktop.session idle-delay 1800 + [ Test Plan ] - 2. Monitor the key for change: + * Open terminal and set a custom delay value (30 min in this case): - $ gsettings monitor org.gnome.desktop.session idle-delay + $ gsettings set org.gnome.desktop.session idle-delay 1800 - 3. Open GNOME Settings and click "Privacy & Security" + * Open GNOME Settings and click "Privacy & Security" - 4. The key is changed, on step 3, to "uint32 0" as seen in the terminal - monitoring the key: + * Verify that the idle-delay value has remained the same - $ gsettings monitor org.gnome.desktop.session idle-delay - idle-delay: uint32 0 + $ gsettings get org.gnome.desktop.session idle-delay + uint32 1800 - More info: - - The option to lock the screen after a delay can be set in (at least) three different locations: + [ Where problems could occur ] + + The scope of the change is limited to the `Blank Screen Delay` and + `Automatic Screen Lock Delay` settings. A bug may prevent these options + to be set, or at worst crash the Settings app. + + [ Other Info ] + + The option to lock the screen after a delay can be set in (at least) + three different locations: 1. Settings -> Power -> Screen Blank 2. Settings -> Privacy & Security -> Screen Lock -> Blank Screen Delay 3. $ gsettings set org.gnome.desktop.session idle-delay 1800 (1 and 2 are drop-down lists going from "Never" up to "15 minutes". In 3, I used "1800" = 30 min.) The issue only happens when I click the tab "Privacy & Settings" (I believe this tab is new in Ubuntu 24.04, I don't recall seeing it in 20.04 or 22.04). I can click all other tabs, including the tab "Power", without problem. I was able to replicate the issue in another laptop, also with Ubuntu 24.04. Machine details: $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 46.0-0ubuntu6~24.04.5 Candidate: 46.0-0ubuntu6~24.04.5 Version table: *** 46.0-0ubuntu6~24.04.5 500 500 http://pt.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 46.0-0ubuntu6~24.04.3 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 46.0-0ubuntu5 500 500 http://pt.archive.ubuntu.com/ubuntu noble/main amd64 Packages $ apt-cache policy gnome-screensaver gnome-screensaver: Installed: (none) Candidate: 3.6.1-13ubuntu4 Version table: 3.6.1-13ubuntu4 500 500 http://pt.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Note I thought the idle-delay was part of package gnome-screensaver but it turns out I don't even have it installed. The package description says "This package is not necessary in the GNOME desktop environment, because GNOME Shell contains its own screen lock implementation. (...)" so I filled this bug under gnome-shell. -- 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/2083869 Title: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: Triaged Bug description: [ Impact ] I usually set the lock delay to 30 minutes, and do it via gsettings since GNOME Settings allows values of 15 min max. This value is reset to "uint32 0" (zero) when I click the tab Privacy & Security in GNOME Settings. Since the
[Desktop-packages] [Bug 2083869] Re: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings
** Changed in: gnome-control-center (Ubuntu Noble) Status: Triaged => In Progress -- 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/2083869 Title: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: In Progress Bug description: [ Impact ] I usually set the lock delay to 30 minutes, and do it via gsettings since GNOME Settings allows values of 15 min max. This value is reset to "uint32 0" (zero) when I click the tab Privacy & Security in GNOME Settings. Since the change happens silently the user will not be aware of it. This is fixed by ensuring that custom idle-delay values, not listed in the `Privacy & Security -> Screen Lock -> Blank Screen Delay` drop-down, are handled gracefully. If the value is not in the list, the drop-down will default to showing no selection instead of falling back to zero. [ Test Plan ] * Open terminal and set a custom delay value (30 min in this case): $ gsettings set org.gnome.desktop.session idle-delay 1800 * Open GNOME Settings and click "Privacy & Security" * Verify that the idle-delay value has remained the same $ gsettings get org.gnome.desktop.session idle-delay uint32 1800 [ Where problems could occur ] The scope of the change is limited to the `Blank Screen Delay` and `Automatic Screen Lock Delay` settings. A bug may prevent these options to be set, or at worst crash the Settings app. [ Other Info ] The option to lock the screen after a delay can be set in (at least) three different locations: 1. Settings -> Power -> Screen Blank 2. Settings -> Privacy & Security -> Screen Lock -> Blank Screen Delay 3. $ gsettings set org.gnome.desktop.session idle-delay 1800 (1 and 2 are drop-down lists going from "Never" up to "15 minutes". In 3, I used "1800" = 30 min.) The issue only happens when I click the tab "Privacy & Settings" (I believe this tab is new in Ubuntu 24.04, I don't recall seeing it in 20.04 or 22.04). I can click all other tabs, including the tab "Power", without problem. I was able to replicate the issue in another laptop, also with Ubuntu 24.04. Machine details: $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 46.0-0ubuntu6~24.04.5 Candidate: 46.0-0ubuntu6~24.04.5 Version table: *** 46.0-0ubuntu6~24.04.5 500 500 http://pt.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 46.0-0ubuntu6~24.04.3 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 46.0-0ubuntu5 500 500 http://pt.archive.ubuntu.com/ubuntu noble/main amd64 Packages $ apt-cache policy gnome-screensaver gnome-screensaver: Installed: (none) Candidate: 3.6.1-13ubuntu4 Version table: 3.6.1-13ubuntu4 500 500 http://pt.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Note I thought the idle-delay was part of package gnome-screensaver but it turns out I don't even have it installed. The package description says "This package is not necessary in the GNOME desktop environment, because GNOME Shell contains its own screen lock implementation. (...)" so I filled this bug under gnome-shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2083869/+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 2084232] Re: Screen Blank drop-down list shows the wrong value selected
** Also affects: gnome-control-center (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released ** Changed in: gnome-control-center (Ubuntu Noble) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu Noble) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: gnome-control-center (Ubuntu Noble) Milestone: None => noble-updates -- 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/2084232 Title: Screen Blank drop-down list shows the wrong value selected Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: In Progress Bug description: [ Impact ] In GNOME Settings, the `Power > Screen Blank` drop-down list shows the wrong value selected when the user has set a custom value from the command-line. The custom value is added to the list of pre-defined time options, but then the wrong entry is shown as selected. This is only a visual bug as the setting isn't actually getting modified. [ Test Plan ] * Open terminal and set a custom delay value (13 min in this case): $ gsettings set org.gnome.desktop.session idle-delay 780 * Open GNOME Settings and click "Power" * Verify that the "Screen Blank" setting shows "30 minutes" as the pre-selected option. * Expand the drop-down list * Verify that the "13 minutes" entry is correctly sorted in the list. [ Where problems could occur ] The scope of the change is limited to the "Blank Screen" and the "Power Button Behaviour" drop-down lists in the Power panel. It should have no impact on the latter, which only supports a limited number of options. If a new bug were introduced, the two settings might stop working, or at worst GNOME Settings may crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2084232/+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 2083869] Re: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings
** Description changed: [ Impact ] I usually set the lock delay to 30 minutes, and do it via gsettings since GNOME Settings allows values of 15 min max. This value is reset to "uint32 0" (zero) when I click the tab Privacy & Security in GNOME Settings. Since the change happens silently the user will not be aware of it. This is fixed by ensuring that custom idle-delay values, not listed in the - `Privacy & Security -> Screen Lock -> Blank Screen Delay` drop-down, are handled gracefully. If the value is not in the list, the drop-down will default to + `Privacy & Security -> Screen Lock -> Blank Screen Delay` drop-down, are handled + gracefully. If the value is not in the list, the drop-down will default to showing no selection instead of falling back to zero. [ Test Plan ] * Open terminal and set a custom delay value (30 min in this case): - $ gsettings set org.gnome.desktop.session idle-delay 1800 + $ gsettings set org.gnome.desktop.session idle-delay 1800 * Open GNOME Settings and click "Privacy & Security" * Verify that the idle-delay value has remained the same - $ gsettings get org.gnome.desktop.session idle-delay - uint32 1800 + $ gsettings get org.gnome.desktop.session idle-delay + uint32 1800 [ Where problems could occur ] - The scope of the change is limited to the `Blank Screen Delay` and - `Automatic Screen Lock Delay` settings. A bug may prevent these options - to be set, or at worst crash the Settings app. + The scope of the change is limited to the `Blank Screen Delay` and `Automatic + Screen Lock Delay` settings. A bug may prevent these options to be set, or at + worst crash the Settings app. [ Other Info ] The option to lock the screen after a delay can be set in (at least) three different locations: 1. Settings -> Power -> Screen Blank 2. Settings -> Privacy & Security -> Screen Lock -> Blank Screen Delay 3. $ gsettings set org.gnome.desktop.session idle-delay 1800 (1 and 2 are drop-down lists going from "Never" up to "15 minutes". In 3, I used "1800" = 30 min.) The issue only happens when I click the tab "Privacy & Settings" (I believe this tab is new in Ubuntu 24.04, I don't recall seeing it in 20.04 or 22.04). I can click all other tabs, including the tab "Power", without problem. I was able to replicate the issue in another laptop, also with Ubuntu 24.04. Machine details: $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 46.0-0ubuntu6~24.04.5 Candidate: 46.0-0ubuntu6~24.04.5 Version table: *** 46.0-0ubuntu6~24.04.5 500 500 http://pt.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 46.0-0ubuntu6~24.04.3 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 46.0-0ubuntu5 500 500 http://pt.archive.ubuntu.com/ubuntu noble/main amd64 Packages $ apt-cache policy gnome-screensaver gnome-screensaver: Installed: (none) Candidate: 3.6.1-13ubuntu4 Version table: 3.6.1-13ubuntu4 500 500 http://pt.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Note I thought the idle-delay was part of package gnome-screensaver but it turns out I don't even have it installed. The package description says "This package is not necessary in the GNOME desktop environment, because GNOME Shell contains its own screen lock implementation. (...)" so I filled this bug under gnome-shell. -- 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/2083869 Title: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: Triaged Bug description: [ Impact ] I usually set the lock delay to 30 minutes, and do it via gsettings since GNOME Settings allows values of 15 min max. This value is reset to "uint32 0" (zero) when I click the tab Privacy & Security in GNOME Settings. Since the change happens silently the user will not be aware of it. This is fixed by ensuring that custom idle-delay values, not listed in the `Privacy & Security -> Screen Lock -> Blank Screen Delay` drop-down, are handled gracefully. If the value is not in the list, the drop-down will default to showing no selection instead of falling back to zero. [ Test Plan ] * Open terminal and set a custom delay value (30 min in this case): $ gsettings set org.gnome.desktop.session idle-delay 1800 * Open GNOME Settings and click "Privacy & Security" * Verify that the idle-del
[Desktop-packages] [Bug 2084232] [NEW] Screen Blank drop-down list shows the wrong value selected
Public bug reported: [ Impact ] In GNOME Settings, the `Power > Screen Blank` drop-down list shows the wrong value selected when the user has set a custom value from the command-line. The custom value is added to the list of pre-defined time options, but then the wrong entry is shown as selected. This is only a visual bug as the setting isn't actually getting modified. [ Test Plan ] * Open terminal and set a custom delay value (13 min in this case): $ gsettings set org.gnome.desktop.session idle-delay 780 * Open GNOME Settings and click "Power" * Verify that the "Screen Blank" setting shows "30 minutes" as the pre-selected option. * Expand the drop-down list * Verify that the "13 minutes" entry is correctly sorted in the list. [ Where problems could occur ] The scope of the change is limited to the "Blank Screen" and the "Power Button Behaviour" drop-down lists in the Power panel. It should have no impact on the latter, which only supports a limited number of options. If a new bug were introduced, the two settings might stop working, or at worst GNOME Settings may crash. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gnome-control-center (Ubuntu Noble) Importance: Undecided Assignee: Alessandro Astone (aleasto) Status: In Progress -- 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/2084232 Title: Screen Blank drop-down list shows the wrong value selected Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: In Progress Bug description: [ Impact ] In GNOME Settings, the `Power > Screen Blank` drop-down list shows the wrong value selected when the user has set a custom value from the command-line. The custom value is added to the list of pre-defined time options, but then the wrong entry is shown as selected. This is only a visual bug as the setting isn't actually getting modified. [ Test Plan ] * Open terminal and set a custom delay value (13 min in this case): $ gsettings set org.gnome.desktop.session idle-delay 780 * Open GNOME Settings and click "Power" * Verify that the "Screen Blank" setting shows "30 minutes" as the pre-selected option. * Expand the drop-down list * Verify that the "13 minutes" entry is correctly sorted in the list. [ Where problems could occur ] The scope of the change is limited to the "Blank Screen" and the "Power Button Behaviour" drop-down lists in the Power panel. It should have no impact on the latter, which only supports a limited number of options. If a new bug were introduced, the two settings might stop working, or at worst GNOME Settings may crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2084232/+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 2083593] Re: Settings portal reports enable-animations as false when they are enabled in GSettings
In a virtual machine without 3d acceleration, such as Virtual Box, it is expected that gnome-shell disables animations, and as Robert said the portal will ask the shell before checking gsettings. If you see this happening on bare metal though, that possibly indicates that gnome-shell thinks you're running without hardware acceleration. -- 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/2083593 Title: Settings portal reports enable-animations as false when they are enabled in GSettings Status in xdg-desktop-portal package in Ubuntu: New Bug description: Last week, I did a clean install of Ubuntu 24.04 LTS on a relatively beefy Thinkpad. This is going to be my Linux build machine (for a game I'm working on) so I installed only a few things: VSCode, Steam, Caffeine, Timeshift, and the requirements for building the game (Flutter SDK, development libraries). While testing the game, I noticed that all animations in the game are skipped. I checked what the app thinks about the environment and it reports animations in the OS as disabled. I double-checked that they're not. 1. They are not disabled in Settings > Accessibility. 2. `gsettings get org.gnome.desktop.interface enable-animations` returns `true` 3. `dconf read /org/gnome/desktop/interface/enable-animations` returns `true` Yet, I get this when using `gdbus`: ``` $ gdbus call --session --dest org.freedesktop.portal.Desktop --object-path /org/freedesktop/portal/desktop --method org.freedesktop.portal.Settings.Read org.gnome.desktop.interface enable-animations (<>,) ``` Apparently, `gdbus` is where some applications are looking when trying to figure out whether animations are enabled. From what I understand, this is _the_ correct way, even. Yesterday, I tried installing Ubuntu from scratch and I reproduced the issue on the clean OS install as well, so it's not something I botched along the way. You can see my screenshot gallery here: https://github.com/flutter/flutter/issues/155982#issuecomment-2387958637 . This issue seems to not appear in installations of Ubuntu that were upgraded from version 22.04, only in clean installations of Ubuntu 24.04. Another person on Mastodon was able to reproduce this issue, too: https://mastodon.social/@sesiv...@vivaldi.net/113238290862309705 I also asked this as a question on askubuntu (https://askubuntu.com/questions/1528661/clean-ubuntu-install-reports- enable-animations-as-false-when-theyre-enabled) but, in retrospect, I think this is a bug in the system, not a support question. I know I can fix this for myself but I want this to work as expected for others. System: ``` $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 ``` ## Expected gdbus (or whatever the subsystem that gdbus uses) returns the correct value for animations enabled/disabled state ## What happens instead gdbus returns false while everything else returns true ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libglib2.0-bin 2.80.0-6ubuntu3.1 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 11:18:41 2024 InstallationDate: Installed on 2024-10-02 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: glib2.0 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/+bug/2083593/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
I'm hitting the same issue `amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:1 pasid:32785)` when playing twitter videos in the firefox snap through VAAPI -- media.ffmpeg.vaapi.enabled=true in about:config. The firefox snap uses mesa 23.2.1 from jammy and that hasn't changed in a while. I get no more crashes if I disable media.ffmpeg.vaapi.enabled in firefox (it's disabled by default). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
I cannot reproduce with the prebuilt firefox tarball from upstream, running on oracular with mesa 24.2.3 (and LLVM 19) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+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 2065294] Re: Diagnostics settings flips to Never without any user action
Verified the test plan with gnome-control-
center{,-data,-faces}=1:46.4-0ubuntu0.24.04.1 on Ubuntu 24.04.1 LTS
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
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/2065294
Title:
Diagnostics settings flips to Never without any user action
Status in gnome-control-center package in Ubuntu:
Fix Released
Status in whoopsie-preferences package in Ubuntu:
Invalid
Status in gnome-control-center source package in Jammy:
Fix Committed
Status in whoopsie-preferences source package in Jammy:
Invalid
Status in gnome-control-center source package in Noble:
Fix Committed
Status in whoopsie-preferences source package in Noble:
Invalid
Bug description:
[ Impact ]
In GNOME Settings' Diagnostics page, the switch to control automatic
bug reporting to Canonical automatically flips to "Never" after 1
minute of the page being open without interaction
The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
A further change should be applied to the whoopsie-preferences service
to avoid quitting when there are clients still listening for potential
settings changes.
[ Test Plan ]
* Open GNOME Settings -> Privacy & Security -> Diagnostics
* You should see `Send error reports to Canonical` set to `Manual` by
default.
> If instead it is set to Never, change it now to another option.
* Stay on the settings page for more than 60 seconds
* The setting should have remained the same and *not* have
automatically changed to `Never`.
[ Where problems could occur ]
This patch also tries to re-start the "whoopsie-preferences" daemon
when it automatically stops after 60 seconds, because GNOME Settings
should keep listening for settings changes from external factors. This
should not present any issues, but it's the most "intrusive" part of
the patch.
[ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.
I noticed this on Jammy, Mantic, and Noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+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 2065294] Re: Diagnostics settings flips to Never without any user action
Verified the test plan with gnome-control-
center{,-data,-faces}=1:41.7-0ubuntu0.22.04.9 on Ubuntu 22.04.5 LTS
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2065294
Title:
Diagnostics settings flips to Never without any user action
Status in gnome-control-center package in Ubuntu:
Fix Released
Status in whoopsie-preferences package in Ubuntu:
Invalid
Status in gnome-control-center source package in Jammy:
Fix Committed
Status in whoopsie-preferences source package in Jammy:
Invalid
Status in gnome-control-center source package in Noble:
Fix Committed
Status in whoopsie-preferences source package in Noble:
Invalid
Bug description:
[ Impact ]
In GNOME Settings' Diagnostics page, the switch to control automatic
bug reporting to Canonical automatically flips to "Never" after 1
minute of the page being open without interaction
The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
A further change should be applied to the whoopsie-preferences service
to avoid quitting when there are clients still listening for potential
settings changes.
[ Test Plan ]
* Open GNOME Settings -> Privacy & Security -> Diagnostics
* You should see `Send error reports to Canonical` set to `Manual` by
default.
> If instead it is set to Never, change it now to another option.
* Stay on the settings page for more than 60 seconds
* The setting should have remained the same and *not* have
automatically changed to `Never`.
[ Where problems could occur ]
This patch also tries to re-start the "whoopsie-preferences" daemon
when it automatically stops after 60 seconds, because GNOME Settings
should keep listening for settings changes from external factors. This
should not present any issues, but it's the most "intrusive" part of
the patch.
[ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.
You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.
I noticed this on Jammy, Mantic, and Noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2065294/+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 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in firefox package in Ubuntu: New Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2083538/+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 2085060] Re: gsd-power crashed with SIGSEGV in __GI___libc_free() from g_hash_table_unref() from g_hash_table_unref() from info_cache_free() from g_hash_table_remove_internal()
Very similar crash but when freeing `proxy->priv->properties` instead of `proxy->priv->expected_interface`: https://launchpad.net/bugs/2085143 ** Tags added: 1202 ** Tags removed: 1202 ** Tags added: udeng-5009 -- 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/2085060 Title: gsd-power crashed with SIGSEGV in __GI___libc_free() from g_hash_table_unref() from g_hash_table_unref() from info_cache_free() from g_hash_table_remove_internal() Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/40e180c1cf5f7e9657be6f796bd3b35b705c35b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2085060/+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 2085061] Re: gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from g_dbus_interface_info_lookup_signal() from on_signal_received() from e
** Tags added: 1202 ** Tags removed: 1202 ** Tags added: udeng-5009 -- 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/2085061 Title: gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from g_dbus_interface_info_lookup_signal() from on_signal_received() from emit_signal_instance_in_idle_cb() Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/a2c79b2516a7c235d7f1c9ccee92c2fdeb4d5e9f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2085061/+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 2085143] Re: /usr/libexec/gsd-power:11:__GI___libc_free:g_hash_table_unref:g_hash_table_unref:g_dbus_proxy_finalize:g_object_unref
** Tags added: udeng-5009 -- 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/2085143 Title: /usr/libexec/gsd- power:11:__GI___libc_free:g_hash_table_unref:g_hash_table_unref:g_dbus_proxy_finalize:g_object_unref Status in gnome-settings-daemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/7264c98132805a920c95de7bf217e3815cd44407 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2085143/+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 2085061] Re: gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from g_dbus_interface_info_lookup_signal() from on_signal_received() from e
This seems very related to https://launchpad.net/bugs/2085060, probably the same bug. But I really can't see anything wrong with how gsd-power uses gdbus... -- 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/2085061 Title: gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from g_dbus_interface_info_lookup_signal() from on_signal_received() from emit_signal_instance_in_idle_cb() Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/a2c79b2516a7c235d7f1c9ccee92c2fdeb4d5e9f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2085061/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Changed in: mutter (Ubuntu) Status: Won't Fix => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: In Progress Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Jammy: New Status in nautilus source package in Noble: In Progress Bug description: Can't move file/directory by drag and drop by using a touch monitor As of 24.10 you can drag a file around but you cannot drop it into a directory. OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
Not a bug in Nautilus. Mutter fix proposed upstream: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4091 Verified the backport for noble which requires 2 additional fixes from upstream ** No longer affects: nautilus (Ubuntu) ** No longer affects: nautilus (Ubuntu Jammy) ** No longer affects: nautilus (Ubuntu Noble) ** No longer affects: mutter (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu Noble) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: mutter (Ubuntu Noble) Assignee: (unassigned) => Alessandro Astone (aleasto) ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu Noble) Importance: Undecided => High -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: In Progress Status in mutter source package in Noble: In Progress Bug description: Can't move file/directory by drag and drop by using a touch monitor As of 24.10 you can drag a file around but you cannot drop it into a directory. OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 2083869] Re: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings
This was already fixed in GNOME 47 and thus it's not an issue in Oracular. ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-control-center (Ubuntu) Milestone: oracular-updates => None -- 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/2083869 Title: Screen Blank delay (idle-delay) is set to zero (uint32 0) on clicking Privacy & Security tab in Settings Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: Triaged Bug description: Context: I usually set the lock delay to 30 minutes, and do it via gsettings since GNOME Settings allows values of 15 min max. Problem: This value is reset to "uint32 0" (zero) when I click the tab Privacy & Security in GNOME Settings. Since the change happens silently the user will not be aware of it. Example to replicate: 1. Open terminal and set a custom delay value (30 min in this case): $ gsettings set org.gnome.desktop.session idle-delay 1800 2. Monitor the key for change: $ gsettings monitor org.gnome.desktop.session idle-delay 3. Open GNOME Settings and click "Privacy & Security" 4. The key is changed, on step 3, to "uint32 0" as seen in the terminal monitoring the key: $ gsettings monitor org.gnome.desktop.session idle-delay idle-delay: uint32 0 More info: The option to lock the screen after a delay can be set in (at least) three different locations: 1. Settings -> Power -> Screen Blank 2. Settings -> Privacy & Security -> Screen Lock -> Blank Screen Delay 3. $ gsettings set org.gnome.desktop.session idle-delay 1800 (1 and 2 are drop-down lists going from "Never" up to "15 minutes". In 3, I used "1800" = 30 min.) The issue only happens when I click the tab "Privacy & Settings" (I believe this tab is new in Ubuntu 24.04, I don't recall seeing it in 20.04 or 22.04). I can click all other tabs, including the tab "Power", without problem. I was able to replicate the issue in another laptop, also with Ubuntu 24.04. Machine details: $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 46.0-0ubuntu6~24.04.5 Candidate: 46.0-0ubuntu6~24.04.5 Version table: *** 46.0-0ubuntu6~24.04.5 500 500 http://pt.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 46.0-0ubuntu6~24.04.3 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 46.0-0ubuntu5 500 500 http://pt.archive.ubuntu.com/ubuntu noble/main amd64 Packages $ apt-cache policy gnome-screensaver gnome-screensaver: Installed: (none) Candidate: 3.6.1-13ubuntu4 Version table: 3.6.1-13ubuntu4 500 500 http://pt.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Note I thought the idle-delay was part of package gnome-screensaver but it turns out I don't even have it installed. The package description says "This package is not necessary in the GNOME desktop environment, because GNOME Shell contains its own screen lock implementation. (...)" so I filled this bug under gnome-shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2083869/+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 2085404] Re: No display after booting
Analysis from 201912_27623_journal_log.txt Early on during boot we see: kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is 61 kernel: [00] BAD 00 ff ff ff ff ff ff 00 04 69 c4 24 cc 83 03 00 kernel: [00] BAD 2c 18 01 03 80 35 1e 78 2a a0 a5 a6 56 52 9d 27 kernel: [00] BAD 0f 50 54 a0 00 00 00 00 00 00 00 07 ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff fe 00 00 00 00 00 00 00 kernel: [00] BAD 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: EDID has corrupt header kernel: i915 :00:02.0: [drm] Cannot find any crtc or sizes Then as GNOME Shell (Wayland) is starting up it suddenly terminates with SIGKILL. There's no clear indication of why, but just before we see "kernel: EDID has corrupt header" again. Oct 23 13:56:26 dell-precision-3440-c27623 kernel: EDID has corrupt header Oct 23 13:56:26 dell-precision-3440-c27623 systemd[1572]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL We are then kicked back to GDM which falls back to Xorg mode and keeps printing: kernel: EDID has corrupt header kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is ### kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND (You now see `Authorization required, but no authorization protocol specified` because Xorg is running as the GDM user and you did not specify an XAUTHORITY file -- that is expected) There seems to be something wrong with the connection to the monitor, although that probably should not be killing GNOME Shell...? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2085404 Title: No display after booting Status in linux package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: [Impact] No display is shown after booting the machine. [Reproduce] 1. connect a monitor to the machine and boot it. 2. ssh into the machine and check the display using the following commands: $ export DISPLAY=":0.0" $ xrandr [Fail rate] 5/5 (100% failure rate) [Expected result] Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384 DP-1 disconnected primary (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) [Actual result] Authorization required, but no authorization protocol specified Can't open display :0.0 [Additional information] https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202005-27944/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12 Uname: Linux 6.8.0-48-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) Date: Wed Oct 23 14:10:39 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/24.09.00: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-S GT2 [UHD Graphics 630] [1028:09aa] InstallationDate: Installed on 2024-05-31 (145 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard Bus 001 Device 003: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Precision 3440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-48-generic root=UUID=696f0fb9-b9c8-410a-abed-8efe16d0560a ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.vendor: Dell Inc. dmi.
[Desktop-packages] [Bug 2084435] Re: gnome-shell crashed with SIGSEGV in _cogl_journal_flush() from g_list_foreach() from _cogl_framebuffer_flush_dependency_journals() from _cogl_journal_flush() from
There's a stack explosion because of a cyclic loop of CoglFramebuffer* dependencies: framebuffer=0x606abb7a52f0 has priv->deps [framebuffer=0x606abf70fe20, ...] which has priv->deps [framebuffer=0x606abb7a52f0, ...] -- 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/2084435 Title: gnome-shell crashed with SIGSEGV in _cogl_journal_flush() from g_list_foreach() from _cogl_framebuffer_flush_dependency_journals() from _cogl_journal_flush() from g_list_foreach() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 47.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/ae6cccd546d8fd021eba10b2bb56273ecd7bd860 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2084435/+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 2083202] Re: /usr/libexec/gsd-power:11:up_client_get_devices2:engine_coldplug:gsd_power_manager_start:main
Currently upower is a required dependency of: gnome-applets gnome-session-bin gnome-power-manager It is also a Recommends for gnome-settings-daemon, through gnome- settings-daemon → libupower-glib3 → upower. The logic did not take into account that connecting to UPower might fail, so eventually gsd-power crashes. However, I don’t believe these crashes originate from upower being not installed. Instead, @paride found that his libimobiledevice6 package was corrupted so that upower couldn’t find the library and failed to start. That shouldn’t happen, but we should make gsd-power exit gracefully rather than crash when failing to connect to UPower. -- 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/2083202 Title: /usr/libexec/gsd- power:11:up_client_get_devices2:engine_coldplug:gsd_power_manager_start:main Status in gnome-settings-daemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4871bf360fcc371310fbdec244b42a054e3858e3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2083202/+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 2085795] Re: Gnome froze when opening file dialog in Firefox
Oct 29 15:23:39 drakkar gvfsd-wsdd[801574]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory) Oct 29 15:23:39 drakkar gvfsd-network[801519]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon. That is normal and expected when `wsdd` is not installed. Oct 29 15:23:39 drakkar gvfsd-network[801519]: GFileInfo created without standard::content-type Oct 29 15:23:39 drakkar gvfsd-network[801519]: file ../../../gio/gfileinfo.c: line 1821 (g_file_info_get_content_type): should not be reached Oct 29 15:23:39 drakkar gvfsd-network[801519]: g_ref_string_new_intern: assertion 'str != NULL' failed Oct 29 15:23:39 drakkar gvfsd-network[801519]: GFileInfo created without standard::content-type Oct 29 15:23:39 drakkar gvfsd-network[801519]: file ../../../gio/gfileinfo.c: line 1821 (g_file_info_get_content_type): should not be reached Oct 29 15:23:39 drakkar gvfsd-network[801519]: g_ref_string_new_intern: assertion 'str != NULL' failed Oct 29 15:23:39 drakkar gvfsd-network[801519]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: mountpoint for org.gtk.vfs.mountpoint_wsdd already running Oct 29 15:23:39 drakkar gvfsd-network[801519]: g_ref_string_release: assertion 'str != NULL' failed Oct 29 15:23:39 drakkar gvfsd-network[801519]: g_file_info_set_content_type: assertion 'content_type != NULL' failed That is more interesting, but I don't know if it's related to the freezing you saw. -- 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/2085795 Title: Gnome froze when opening file dialog in Firefox Status in gnome-shell package in Ubuntu: Incomplete Bug description: The Gnome froze, Firefox window became dimmed. and I cannot access the other display with mouse cursor. I was not able to open Logout window. I logged in over ssh and restarted gnome by killing gdm. What I saw in the log is: Oct 28 20:54:25 drakkar gvfsd-network[420517]: GFileInfo created without standard::content-type Oct 28 20:54:25 drakkar gvfsd-network[420517]: file ../../../gio/gfileinfo.c: line 1821 (g_file_info_get_content_type): should not be reached Oct 28 20:54:25 drakkar gvfsd-network[420517]: g_ref_string_new_intern: assertion 'str != NULL' failed Oct 28 20:54:25 drakkar gvfsd-wsdd[421070]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory) Oct 28 20:54:25 drakkar gvfsd-network[420517]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon. Oct 28 20:54:25 drakkar gvfsd-network[420517]: g_ref_string_release: assertion 'str != NULL' failed Oct 28 20:54:25 drakkar gvfsd-network[420517]: g_file_info_set_content_type: assertion 'content_type != NULL' failed This is the gnome-shell package mastier@drakkar:~$ apt-cache policy show gnome-shell gnome-shell: Installed: 46.0-0ubuntu6~24.04.5 Candidate: 46.0-0ubuntu6~24.04.5 Version table: *** 46.0-0ubuntu6~24.04.5 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu6~24.04.5 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 20:56:24 2024 DisplayManager: gdm3 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-09-05 (53 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 mtime.conffile..etc.logrotate.d.apport: 2023-08-24T03:09:53.125138 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2085795/+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 2085143] Re: /usr/libexec/gsd-power:11:__GI___libc_free:g_hash_table_unref:g_hash_table_unref:g_dbus_proxy_finalize:g_object_unref
** Description changed: + Stacktrace + + #0 0x7093e8ab3395 in __GI___libc_free (mem=0x361101620) at ./malloc/malloc.c:3375 + ar_ptr = + p = + err = + #1 0x7093e8e1c04c in g_hash_table_unref (hash_table=0x558b610fda00) at ../../../glib/ghash.c:1442 + __func__ = + _g_boolean_var_27 = + #2 g_hash_table_unref (hash_table=0x558b610fda00) at ../../../glib/ghash.c:1432 + __func__ = "g_hash_table_unref" + #3 0x7093e903fe9a in g_dbus_proxy_finalize (object=0x558b610ff3c0) at ../../../gio/gdbusproxy.c:218 + proxy = 0x558b610ff3c0 + __func__ = "g_dbus_proxy_finalize" + #4 0x7093e9a7c922 in g_object_unref (_object=0x558b610ff3c0) at ../../../gobject/gobject.c:4486 + object = 0x558b610ff3c0 + old_ref = 1 + toggle_notify = + toggle_data = + nqueue = 0x558b610ebad0 + obj_gtype = + retry_beginning = + retry_decrement = + __func__ = "g_object_unref" + #5 0x558b2f89b102 in gsd_power_manager_stop (manager=0x558b610f06f0) at ../plugins/power/gsd-power-manager.c:3142 + _pp = 0x558b610f0748 + _ptr = + #6 0x558b2f897400 in main (argc=, argv=) at ../plugins/common/daemon-skeleton-gtk.h:294 + error = 0x0 + name_own_id = 1 + + + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/7264c98132805a920c95de7bf217e3815cd44407 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- 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/2085143 Title: /usr/libexec/gsd- power:11:__GI___libc_free:g_hash_table_unref:g_hash_table_unref:g_dbus_proxy_finalize:g_object_unref Status in gnome-settings-daemon package in Ubuntu: New Bug description: Stacktrace #0 0x7093e8ab3395 in __GI___libc_free (mem=0x361101620) at ./malloc/malloc.c:3375 ar_ptr = p = err = #1 0x7093e8e1c04c in g_hash_table_unref (hash_table=0x558b610fda00) at ../../../glib/ghash.c:1442 __func__ = _g_boolean_var_27 = #2 g_hash_table_unref (hash_table=0x558b610fda00) at ../../../glib/ghash.c:1432 __func__ = "g_hash_table_unref" #3 0x7093e903fe9a in g_dbus_proxy_finalize (object=0x558b610ff3c0) at ../../../gio/gdbusproxy.c:218 proxy = 0x558b610ff3c0 __func__ = "g_dbus_proxy_finalize" #4 0x7093e9a7c922 in g_object_unref (_object=0x558b610ff3c0) at ../../../gobject/gobject.c:4486 object = 0x558b610ff3c0 old_ref = 1 toggle_notify = toggle_data = nqueue = 0x558b610ebad0 obj_gtype = retry_beginning = retry_decrement = __func__ = "g_object_unref" #5 0x558b2f89b102 in gsd_power_manager_stop (manager=0x558b610f06f0) at ../plugins/power/gsd-power-manager.c:3142 _pp = 0x558b610f0748 _ptr = #6 0x558b2f897400 in main (argc=, argv=) at ../plugins/common/daemon-skeleton-gtk.h:294 error = 0x0 name_own_id = 1 The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/7264c98132805a920c95de7bf217e3815cd44407 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2085143/+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 2085060] Re: gsd-power crashed with SIGSEGV in __GI___libc_free() from g_hash_table_unref() from g_hash_table_unref() from info_cache_free() from g_hash_table_remove_internal()
** Description changed: + Stacktrace + + #0 0x7ad719ab3395 in __GI___libc_free (mem=0xbf293fbb0) at ./malloc/malloc.c:3375 + ar_ptr = + p = + err = + #1 0x7ad719e1c04c in g_hash_table_unref (hash_table=0x5770f293bf10) at ../../../glib/ghash.c:1442 + __func__ = + _g_boolean_var_27 = + #2 g_hash_table_unref (hash_table=0x5770f293bf10) at ../../../glib/ghash.c:1432 + __func__ = "g_hash_table_unref" + #3 0x7ad71a046048 in info_cache_free (cache=0x5770f2940e40) at ../../../gio/gdbusintrospection.c:1886 + __func__ = "info_cache_free" + #4 0x7ad719e1aca9 in g_hash_table_remove_internal (hash_table=0x5770f292b230, key=0x7ad71ac12660 <_gsd_screen_saver_interface_info>, notify=1) at ../../../glib/ghash.c:1722 + node_index = 11 + node_hash = 448865888 + node_index = + node_hash = + __func__ = + _g_boolean_var_33 = + #5 g_hash_table_remove (hash_table=0x5770f292b230, key=key@entry=0x7ad71ac12660 <_gsd_screen_saver_interface_info>) at ../../../glib/ghash.c:1750 + No locals. + #6 0x7ad71a0470cf in g_dbus_interface_info_cache_release (info=0x7ad71ac12660 <_gsd_screen_saver_interface_info>) at ../../../gio/gdbusintrospection.c:2137 + cache = + __func__ = "g_dbus_interface_info_cache_release" + #7 0x7ad71a03feac in g_dbus_proxy_finalize (object=0x5770f2940c60) at ../../../gio/gdbusproxy.c:222 + proxy = 0x5770f2940c60 + __func__ = "g_dbus_proxy_finalize" + #8 0x7ad71aa46922 in g_object_unref (_object=0x5770f2940c60) at ../../../gobject/gobject.c:4486 + object = 0x5770f2940c60 + old_ref = 1 + toggle_notify = + toggle_data = + nqueue = 0x5770f2950240 + obj_gtype = + retry_beginning = + retry_decrement = + __func__ = "g_object_unref" + #9 0x5770d5187102 in gsd_power_manager_stop (manager=0x5770f2931900) at ../plugins/power/gsd-power-manager.c:3142 + _pp = 0x5770f2931958 + _ptr = + #10 0x5770d5183400 in main (argc=, argv=) at ../plugins/common/daemon-skeleton-gtk.h:294 + error = 0x0 + name_own_id = 1 + + + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/40e180c1cf5f7e9657be6f796bd3b35b705c35b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- 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/2085060 Title: gsd-power crashed with SIGSEGV in __GI___libc_free() from g_hash_table_unref() from g_hash_table_unref() from info_cache_free() from g_hash_table_remove_internal() Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Stacktrace #0 0x7ad719ab3395 in __GI___libc_free (mem=0xbf293fbb0) at ./malloc/malloc.c:3375 ar_ptr = p = err = #1 0x7ad719e1c04c in g_hash_table_unref (hash_table=0x5770f293bf10) at ../../../glib/ghash.c:1442 __func__ = _g_boolean_var_27 = #2 g_hash_table_unref (hash_table=0x5770f293bf10) at ../../../glib/ghash.c:1432 __func__ = "g_hash_table_unref" #3 0x7ad71a046048 in info_cache_free (cache=0x5770f2940e40) at ../../../gio/gdbusintrospection.c:1886 __func__ = "info_cache_free" #4 0x7ad719e1aca9 in g_hash_table_remove_internal (hash_table=0x5770f292b230, key=0x7ad71ac12660 <_gsd_screen_saver_interface_info>, notify=1) at ../../../glib/ghash.c:1722 node_index = 11 node_hash = 448865888 node_index = node_hash = __func__ = _g_boolean_var_33 = #5 g_hash_table_remove (hash_table=0x5770f292b230, key=key@entry=0x7ad71ac12660 <_gsd_screen_saver_interface_info>) at ../../../glib/ghash.c:1750 No locals. #6 0x7ad71a0470cf in g_dbus_interface_info_cache_release (info=0x7ad71ac12660 <_gsd_screen_saver_interface_info>) at ../../../gio/gdbusintrospection.c:2137 cache = __func__ = "g_dbus_interface_info_cache_release" #7 0x7ad71a03feac in g_dbus_proxy_finalize (object=0x5770f2940c60) at ../../../gio/gdbusproxy.c:222 proxy = 0x5770f2940c60 __func__ = "g_dbus_proxy_finalize" #8 0x7ad71aa46922 in g_object_unref (_object=0x5770f2940c60) at ../../../gobject/gobject.c:4486 object = 0x5770f2940c60 old_ref = 1 tog
[Desktop-packages] [Bug 2085061] Re: gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from g_dbus_interface_info_lookup_signal() from on_signal_received() from e
** Description changed: + Stacktrace + + #0 g_hash_table_lookup_node (hash_table=0x58ffa9856880, key=0x7e16cc008b80, hash_return=) at ../../../glib/ghash.c:428 + node_hash = + hash_value = 288199634 + have_tombstone = 0 + step = 0 + node_index = 1 + first_tombstone = 0 + node_index = + node_hash = + hash_value = + first_tombstone = + have_tombstone = + step = + _g_boolean_var_9 = + node_key = + #1 g_hash_table_lookup (hash_table=0x58ffa9856880, key=key@entry=0x7e16cc008b80) at ../../../glib/ghash.c:1488 + node_index = + node_hash = 288199634 + __func__ = "g_hash_table_lookup" + #2 0x7e16f1246ddc in g_dbus_interface_info_lookup_signal (info=0x7e16f1dde660 <_gsd_screen_saver_interface_info>, name=0x7e16cc008b80 "WakeUpScreen") at ../../../gio/gdbusintrospection.c:1978 + cache = + n = + result = + #3 0x7e16f12410c9 in on_signal_received (connection=, sender_name=0x7e16cc015580 ":1.89", object_path=, interface_name=, signal_name=0x7e16cc008b80 "WakeUpScreen", parameters=0x58ffa984abd0, user_data=0x58ffa9857cc0) at ../../../gio/gdbusproxy.c:851 + info = + proxy_weak = 0x58ffa9857cc0 + proxy = 0x58ffa985a860 + out = + #4 0x7e16f122b150 in emit_signal_instance_in_idle_cb (data=0x7e16cc001e90) at ../../../gio/gdbusconnection.c:4189 + signal_instance = 0x7e16cc001e90 + parameters = 0x58ffa984abd0 + has_subscription = 1 + #5 0x7e16f102e397 in g_main_dispatch (context=0x58ffa97a9f20) at ../../../glib/gmain.c:3357 + dispatch = 0x7e16f102b670 + prev_source = 0x0 + begin_time_nsec = 1947608561136 + was_in_call = 0 + user_data = 0x7e16cc001e90 + callback = 0x7e16f122b0d0 + cb_funcs = 0x7e16f111c380 + cb_data = 0x7e16cc013c70 + need_destroy = + source = 0x7e16cc0133a0 + current = 0x58ffa97aa160 + i = 0 + __func__ = "g_main_dispatch" + #6 0x7e16f108edc7 in g_main_context_dispatch_unlocked (context=0x58ffa97a9f20) at ../../../glib/gmain.c:4208 + No locals. + #7 g_main_context_iterate_unlocked.isra.0 (context=0x58ffa97a9f20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4273 + max_priority = 2147483647 + timeout_usec = 5127624 + some_ready = 1 + nfds = 3 + allocated_nfds = + fds = 0x58ffa9855fd0 + begin_time_nsec = 1943812861054 + #8 0x7e16f102f097 in g_main_loop_run (loop=0x58ffa9853210) at ../../../glib/gmain.c:4475 + self = + __func__ = "g_main_loop_run" + #9 0x7e16f1608025 in gtk_main () at ../../../gtk/gtkmain.c:1329 + loop = 0x58ffa9853210 + #10 0x58ff6bc303f4 in main (argc=, argv=) at ../plugins/common/daemon-skeleton-gtk.h:292 + error = 0x0 + name_own_id = 1 + + + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 47.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/a2c79b2516a7c235d7f1c9ccee92c2fdeb4d5e9f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- 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/2085061 Title: gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from g_dbus_interface_info_lookup_signal() from on_signal_received() from emit_signal_instance_in_idle_cb() Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Stacktrace #0 g_hash_table_lookup_node (hash_table=0x58ffa9856880, key=0x7e16cc008b80, hash_return=) at ../../../glib/ghash.c:428 node_hash = hash_value = 288199634 have_tombstone = 0 step = 0 node_index = 1 first_tombstone = 0 node_index = node_hash = hash_value = first_tombstone = have_tombstone = step = _g_boolean_var_9 = node_key = #1 g_hash_table_lookup (hash_table=0x58ffa9856880, key=key@entry=0x7e16cc008b80) at ../../../glib/ghash.c:1488 node_index = node_hash = 288199634 __func__ = "g_hash_table_lookup" #2 0x7e16f1246ddc in g_dbus_interface_info_lookup_signal (info=0x7e16f1dde660 <_gsd_screen_saver_interface_info>, name=0x7e16cc008b80 "WakeUpScreen") at ..
[Desktop-packages] [Bug 2086484] Re: Nvidia driver changed to nouveau after dist upgrade to oracular
kernel/drivers people, any idea how this would happen? ** Summary changed: - External HDMI does not work after dist upgrade + Nvidia driver changed to nouveau after dist upgrade to oracular ** Also affects: nvidia-graphics-drivers-560 (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2086484 Title: Nvidia driver changed to nouveau after dist upgrade to oracular Status in nvidia-graphics-drivers-560 package in Ubuntu: New Bug description: After upgrading 24.04 to 24.10, external HDMI did not work anymore on Predator Helios Neo 16 laptop (no signal at all). Found in settings that display driver has been switched to "X.Org X Server - Nouveau display driver" automatically during upgrade. Reverted back to "NVIDIA driver metapackage nvidia-driver-560 (propietary)" and external HDMI came back to live. IIRC 24.04 also used the propietary one by default --> look like the new driver does not support nvidia graphics cards fully on predator laptop series. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.fabric-imex-mgmt: DeviceFileMinor: 4323 DeviceFileMode: 256 DeviceFileModify: 1 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 560.35.03 Fri Aug 16 21:39:15 UTC 2024 GCC version: ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 20:08:43 2024 DistUpgraded: 2024-11-01 19:44:38,723 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: oracular DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Raptor Lake-S UHD Graphics [8086:a788] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:170f] NVIDIA Corporation AD106M [GeForce RTX 4070 Max-Q / Mobile] [10de:2860] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:170f] InstallationDate: Installed on 2024-09-06 (56 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: Acer Predator PHN16-71 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-9-generic root=UUID=1d90e851-4623-4ed6-b855-ca641935c925 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oracular on 2024-11-01 (0 days ago) dmi.bios.date: 11/14/2023 dmi.bios.release: 1.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Compass_RTX dmi.board.vendor: RPL dmi.board.version: V1.15 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.15:bd11/14/2023:br1.15:efr1.5:svnAcer:pnPredatorPHN16-71:pvrV1.15:rvnRPL:rnCompass_RTX:rvrV1.15:cvnAcer:ct10:cvrChassisVersion:sku: dmi.product.family: Predator Helios Neo 16 dmi.product.name: Predator PHN16-71 dmi.product.sku: dmi.product.version: V1.15 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.122-1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-560/+bug/2086484/+subscriptions -- Mailing list: https://launchp
