[Desktop-packages] [Bug 1993284] Re: All app icons are missing after computer locked for some time (Ubuntu 22.04)
*** This bug is a duplicate of bug 1936734 *** https://bugs.launchpad.net/bugs/1936734 Hi I'm also facing the same issue is there any workaround ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1993284 Title: All app icons are missing after computer locked for some time (Ubuntu 22.04) Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Happening in Ubuntu 22.04 How to reproduce: Left computer idle and locked for quite some time Unlock the computer Only Show Applications icon is shown in dash-to-dock When clicked, blank black screen with no application is shown. And can't return to desktop or do any other navigations. Log out / restart menu still works so I usually restart my computer to fix this. Affected application: micheleg-dash-to-dock ~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1993284/+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 2022889] Autopkgtest regression report (libreoffice/4:7.5.4-0ubuntu0.23.04.1)
All autopkgtests for the newly accepted libreoffice (4:7.5.4-0ubuntu0.23.04.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/4:7.5.4-0ubuntu0.23.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#libreoffice [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2022889 Title: [SRU] libreoffice 7.5.4 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.4 is in its forth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.4_release * Version 7.5.3 is currently released in lunar. For a list of fixed bugs compared to 7.5.3 see the list of bugs fixed in the release candidates of 7.5.4 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14936260/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230605_142135_2b00f@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230605_113325_1478c@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230605_085103_17f17@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230605_092012_906e0@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230605_104011_2ff4a@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in.a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2022889/+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 2023417] Re: Update nautilus to 44.2.1
Hello Jeremy, or anyone else affected, Accepted nautilus into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:44.2.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nautilus (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- 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/2023417 Title: Update nautilus to 44.2.1 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Lunar: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 44 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS (The current version in Ubuntu 23.04 is 44.0) Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well Test Case 2 --- 1. Install the update 2. Run pkill nautilus to ensure all open nautilus windows are closed 3. Open Nautilus 4. Click Ctrl+N to open a second Nautilus window 5. In the first Nautilus window, open the Preferences dialog. This dialog is modal to this window (can't be moved away from centered in the window). Close Preferences. Close this window. 6. In the second Nautilus window, open the Preferences dialog. The preferences dialog should be modal to the window (and it should not crash). https://gitlab.gnome.org/GNOME/nautilus/-/issues/2986 Test Case 3 --- 1. Install the update 2. Open a terminal and run sudo apt install gnome-sushi 3. Open Nautilus 4. Open the preferences dialog and turn on Expandable Folders in List View. Close the preferences dialog. 5. Press Ctrl+l to focus the address bar and enter /usr/share 6. Use the space bar to open the Sushi previewer on one of the folders 7. With the Sushi preview window open, use the down arrow keys to navigate down to other folders. Keep going down until you go beyond the first page of results in Nautilus. The main nautilus window should scroll down to show these results focused. https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1221 What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME Core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires gtk4 4.10.4 (LP: #2023031) This update drops 4 cherry-picked patches that have been applied in the new release It also cherry-picks 3 patches from the stable gnome-44 branch (future nautilus 44.3). It also includes a patch included in 44.2 but dropped from 44.2.1 because it was not clear how long it would take for gtk4 4.10.4 to be released. But gtk 4.10.4 was released only a few hours later. https://gitlab.gnome.org/GNOME/nautilus/-/commit/e193b2ce5d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023417/+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 2013235] Autopkgtest regression report (mutter/44.2-0ubuntu1)
All autopkgtests for the newly accepted mutter (44.2-0ubuntu1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: mutter/44.2-0ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#mutter [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013235 Title: Drag and Drop not working in Qt-Applications on Gnome 44 Status in Kdenlive: Invalid Status in Mutter: Fix Released Status in OpenShot Video Editor: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact == Drag and drop items within Qt applications not working since upgrade to Ubuntu Lunar developmental release. The items can be picked up then the cursor changed to the "forbid" sign and no further interaction to the app. Confirmed affected apps: 3d Slicer, Krita. Test Case = 1. Start from Ubuntu 23.04 (the default desktop not KDE or Kubuntu) 2. Open a terminal and run sudo apt install krita 3. Install the updated mutter packages then log out and log back in. 4. Run Krita 5. Click New File. Then click Create 6. Select the rectangle from the left sidebar. Draw a rectangle on the canvas. 7. In the menu, select Layer > New > Add Paint Layer 8. Select the ellipse/circle from the left sidebar. Draw an ellipse on the canvas. 9. In the right sidebar, drag Paint Layer 1 on top of Paint Layer 2 so that they switch places. This should work with the updated mutter packages but does not work with mutter 44.0 or mutter 44.1. What Could Go Wrong === This fix is included in the upstream mutter 44.2 release so see the master bug for that update: https://launchpad.net/bugs/2022951 To manage notifications about this bug go to: https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 2022951] Autopkgtest regression report (mutter/44.2-0ubuntu1)
All autopkgtests for the newly accepted mutter (44.2-0ubuntu1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: mutter/44.2-0ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#mutter [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022951 Title: Update mutter to 44.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.2/NEWS This is basically a prerequisite for GNOME Shell 44.2 LP: #2022961 Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This also includes an update of the triple buffering patch to add one commit to fix a potential crash with resuming from suspend. That triple buffering patch is maintained in a targeted mutter 44 branch by Canonical Desktop engineer Daniel. I was unable to easily reproduce the crash so I didn't include LP: #2020652 in the SRU changelog. I dropped 2 patches to mark some tests as flaky since mutter seems to build reliably enough on Debian and Ubuntu without those patches. Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 44.2 to require mutter >= 44.2 (even though GNOME Shell 44.2 appears to run ok with Mutter 44.1). I believe the only way to make the dependency relationship work the other way (not allow Mutter 44.2 with GNOME Shell 44.1) requires bumping the Breaks version but I don't think it's worth using Breaks unless necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2022951/+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 2013126] Re: file chooser dialog doesn't respect system theme
This bug was fixed in the package libadwaita-1 - 1.3.3-1ubuntu1 --- libadwaita-1 (1.3.3-1ubuntu1) mantic; urgency=medium [ Marco Trevisan (Treviño) ] * Merge with Debian. Remaining changes: - debian/patches: Support yaru accent colors using adwaita theming * debian/patches: refresh * debian/patches: Reuse GSettings implementation for yaru accents (LP: #2013126) [ Grigorii Khvatskii ] * debian/patches: Always init gsettings and legacy settings backends (LP: #2013126) libadwaita-1 (1.3.3-1) experimental; urgency=medium * New upstream release (LP: #2023411) -- Marco Trevisan (Treviño) Fri, 09 Jun 2023 21:29:44 +0200 ** Changed in: libadwaita-1 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2013126 Title: file chooser dialog doesn't respect system theme Status in libadwaita-1 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Bug description: The file chooser dialog uses the default (light) style, even when the dark style is enabled. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 21:08:55 2023 InstallationDate: Installed on 2022-09-07 (202 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2013126/+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 2023411] Re: Update libadwaita to 1.3.3
This bug was fixed in the package libadwaita-1 - 1.3.3-1ubuntu1 --- libadwaita-1 (1.3.3-1ubuntu1) mantic; urgency=medium [ Marco Trevisan (Treviño) ] * Merge with Debian. Remaining changes: - debian/patches: Support yaru accent colors using adwaita theming * debian/patches: refresh * debian/patches: Reuse GSettings implementation for yaru accents (LP: #2013126) [ Grigorii Khvatskii ] * debian/patches: Always init gsettings and legacy settings backends (LP: #2013126) libadwaita-1 (1.3.3-1) experimental; urgency=medium * New upstream release (LP: #2023411) -- Marco Trevisan (Treviño) Fri, 09 Jun 2023 21:29:44 +0200 ** Changed in: libadwaita-1 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/2023411 Title: Update libadwaita to 1.3.3 Status in libadwaita-1 package in Ubuntu: Fix Released Status in libadwaita-1 source package in Lunar: In Progress Bug description: Impact -- 1. There is a new release in the stable 1.3 series. https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.3.3/NEWS Test Case 1 --- After installing the update, open gnome-control-center and nautilus. Ensure that the apps run and that the on/off switches, checkboxes, and other visual elements still display correctly. In gnome-control-center click Appearance in the sidebar. Verify that switching the style between Light and Dark works correctly. Also choose a different accent color and verify that elements like folder icons in Nautilus and on/off switches have correctly adopted the accent color you chose. Test Case 2 --- Run adwaita-1-demo run the style classes demo check that all elements are properly visible and check that link color has enough contrast with background. What Could Go Wrong --- libadwaita is an addon library to GTK4 to allow apps to easily use more of the GNOME style and allow for widgets to be added and improved faster than in the normal GTK development cycle. libadwaita is included in all Ubuntu desktop flavors except for Kubuntu & Lubuntu. Many of the default Ubuntu desktop apps and even GNOME Shell in 23.04 use libadwaita. As a component of GNOME core, there is a micro-release exception for libadwaita. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2023411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Although Mustafa says he's not well-versed, he's way smarter than me :) So his comment#26 seems to be much more relevant than what I have to say, but I'd like to reply to Daniel's comment#24/25 anyway: I saw the details you mentioned on comment #16, and I also have fractional scaling turned off. By "having it off" I'm assuming this [1] is enough, right? Also, I noticed that by previous pasteboard wasn't too clear in showing the problem when I use 42.5-0ubuntu1vv5. I want to clarify that I get a screen as if I had 3 monitors side by side, but all in the same "client monitor". If you try to maximize the application, it picks one of the "screens" and maximizes to it, as we can see here [2]. Even without changing the fractional scale or scale setting, just by having the 42.5-0ubuntu1vv5 packages installed, I get this "triple monitor in 1" situation when I boot my VM. I had to reinstall the original packages from our archives in order to fix this. Also, I just want to make sure you're aware that these are the *mutter* packages that I have installed: ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.5-0ubuntu1 amd64GObject introspection data for Mutter ii libmutter-10-0:amd6442.5-0ubuntu1 amd64window manager library from the Mutter window manager ii mutter-common 42.5-0ubuntu1 all shared files for the Mutter window manager i.e. Just want to make clear that I don't have the "mutter" package installed, but the ones above. Back to your comment, iiuc, the "Impossible to set scaling on crtc 65 to 1.00, error id 2" means that we're trying to use some incomplete RandR implementation in Xdcv. Isn't it the fractional scaling, that was effectively removed from your 42.5-0ubuntu1vv5 package? In this case, doesn't the errors showing up means that we're still trying to use something that isn't properly implemented in Xdcv? Just for my own information, what's the difference between the vv5 and vv4 builds? Tested with vv4 in a VM: ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.5-0ubuntu1vv4 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.5-0ubuntu1vv4 amd64window manager library from the Mutter window manager ii mutter-common 42.5-0ubuntu1vv4 all shared files for the Mutter window manager As soon as I installed it in my VM, I got that "triple monitor" situation again, and then I realized it's really just what you had described, that it automatically enables these other monitors. I can disable them and get back to 1 single monitor. With vv4, I can apply the scale 200% [3] and then revert it, but then it changes my resolution to 800x600. After realizing that, I went back to the vv5 package and re-tested and I notice it's the same behavior as in vv4. After installing it automatically enables all 4 monitors, I have to manually disable them and keep just 1. Then I test the scale to 200% + revert and it does revert, but also changes my resolution to 800x600. I can't really test that in Workspaces, because when it enables the extra monitors, I'm no longer able to access the Workspace with the AWS Workspaces client. If I try to change the scale in Workspaces, I believe it tries to enable the other monitors, and then all I get is a blank screen. And here's the output of "xrandr --verbose" from the VM [5] and the Workspace [6] [1] https://pasteboard.co/qEbvvwijUW2F.png [2] https://pasteboard.co/K9Oh9nZ8wqNk.png [3] https://pastebin.ubuntu.com/p/xkcFScZv5c/ [4] https://pastebin.ubuntu.com/p/mVwWt4Rzsr/ [5] https://pastebin.ubuntu.com/p/JC4PXwdv55/ [6] https://pastebin.ubuntu.com/p/S5bXz975Nn/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full
[Desktop-packages] [Bug 2023417] Re: Update nautilus to 44.2.1
This bug was fixed in the package nautilus - 1:44.2.1-1ubuntu1 --- nautilus (1:44.2.1-1ubuntu1) mantic; urgency=medium * Resynchronize with Debian (LP: #2023417), remaining Ubuntu changes: - Depend on xdg-desktop-portal-gnome | xdg-desktop-portal-backend. Required for "Set as Background" feature - debian/control.in: + Build-Depend on libunity-dev + lower gnome-sushi Recommends to a Suggests - debian/changelog, debian/rules: set epoch number (which was added by error) - debian/source_nautilus.py, debian/nautilus-data.install: + Apport hook to list versions of files in /usr/lib/nautilus and reassign the crashes when they are not due to nautilus code directly - debian/rules: + Build Unity support - 04_suppress_umount_in_ltsp.patch: + Don't list unmount and eject actions on LTSP clients - 12_unity_launcher_support.patch: + unity launcher integration (list bookmarks in the context menu, display a bar on the icon during copies) - 18_unity_icon_color.patch: + specify a background color for the unity launcher icon - 19_unity_open_location_xid.patch: + Add a new dbus property to store the lists of opened locations referenced by their parent nautilus window XID. - ubuntu_backspace_behaviour.patch: + restore backspace behaviour to go back - Revert commit that requires libcloudproviders because it's not in Ubuntu main nautilus (44.2.1-1) experimental; urgency=medium * New upstream release * debian/control.in: Bump minimum gtk4 to 4.10.4 * Revert the reverting of a bugfix that requires gtk4 4.10.4 * Cherry-pick 3 fixes from the gnome-44 branch nautilus (44.2-1) experimental; urgency=medium * Team upload [ Amin Bandali ] * New upstream release (Closes: #1034880) - Fix crashes with expandable folders and on Other Locations (Corey Berla) (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2882) - Avoid inconsistent search states (Khalid Abu Shawarib) (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2875) - Prevent lingering tracker cursors (Carlos Garnacho) (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2557) - Fix rubberband range behavior on list view (António Fernandes) (https://gitlab.gnome.org/GNOME/nautilus/-/issues/2974) [ Jeremy Bicha ] * debian/control.in: Depend on eject (Closes: #1035538) -- Jeremy Bícha Fri, 09 Jun 2023 15:04:38 -0400 ** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2882 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2882 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2875 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2875 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2557 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2557 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2974 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2974 -- 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/2023417 Title: Update nautilus to 44.2.1 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Lunar: In Progress Bug description: Impact -- This is a new stable release in the GNOME 44 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS (The current version in Ubuntu 23.04 is 44.0) Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well Test Case 2 --- 1. Install the update 2. Run pkill nautilus to ensure all open nautilus windows are closed 3. Open Nautilus 4. Click Ctrl+N to open a second Nautilus window 5. In the first Nautilus window, open the Preferences dialog. This dialog is modal to this window (can't be moved away from centered in the window). Close Preferences. Close this window. 6. In the second Nautilus window, open the Preferences dialog. The preferences dialog should be modal to the window (and it should not crash). https://gitlab.gnome.org/GNOME/nautilus/-/issues/2986 Test Case 3 --- 1. Install the update 2. Open a terminal and run sudo apt install gnome-sushi 3. Open Nautilus 4. Open the preferences dialog and turn on Expandable Folders in List View. Close the preferences dialog. 5. Press Ctrl+l to focus the address bar and enter /usr/share 6. Use the space bar to open the Sushi previewer on one of the folders 7. With the Sushi preview window open, use the down arrow keys to navigate down to other folders. Keep going
[Desktop-packages] [Bug 2023417] Re: Update nautilus to 44.2.1
** Description changed: Impact -- This is a new stable release in the GNOME 44 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS (The current version in Ubuntu 23.04 is 44.0) Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well + + Test Case 2 + --- + 1. Install the update + 2. Run pkill nautilus to ensure all open nautilus windows are closed + 3. Open Nautilus + 4. Click Ctrl+N to open a second Nautilus window + 5. In the first Nautilus window, open the Preferences dialog. This dialog is modal to this window (can't be moved away from centered in the window). Close Preferences. Close this window. + 6. In the second Nautilus window, open the Preferences dialog. The preferences dialog should be modal to the window (and it should not crash). + + https://gitlab.gnome.org/GNOME/nautilus/-/issues/2986 + + Test Case 3 + --- + 1. Install the update + 2. Open a terminal and run sudo apt install gnome-sushi + 3. Open Nautilus + 4. Open the preferences dialog and turn on Expandable Folders in List View. Close the preferences dialog. + 5. Press Ctrl+l to focus the address bar and enter /usr/share + 6. Use the space bar to open the Sushi previewer on one of the folders + 7. With the Sushi preview window open, use the down arrow keys to navigate down to other folders. Keep going down until you go beyond the first page of results in Nautilus. + + The main nautilus window should scroll down to show these results + focused. + + https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1221 What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME Core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires gtk4 4.10.4 (LP: #2023031) This update drops 4 cherry-picked patches that have been applied in the new release It also cherry-picks 3 patches from the stable gnome-44 branch (future nautilus 44.3). It also includes a patch included in 44.2 but dropped from 44.2.1 because it was not clear how long it would take for gtk4 4.10.4 to be released. But gtk 4.10.4 was released only a few hours later. https://gitlab.gnome.org/GNOME/nautilus/-/commit/e193b2ce5d5 -- 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/2023417 Title: Update nautilus to 44.2.1 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Lunar: In Progress Bug description: Impact -- This is a new stable release in the GNOME 44 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS (The current version in Ubuntu 23.04 is 44.0) Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well Test Case 2 --- 1. Install the update 2. Run pkill nautilus to ensure all open nautilus windows are closed 3. Open Nautilus 4. Click Ctrl+N to open a second Nautilus window 5. In the first Nautilus window, open the Preferences dialog. This dialog is modal to this window (can't be moved away from centered in the window). Close Preferences. Close this window. 6. In the second Nautilus window, open the Preferences dialog. The preferences dialog should be modal to the window (and it should not crash). https://gitlab.gnome.org/GNOME/nautilus/-/issues/2986 Test Case 3 --- 1. Install the update 2. Open a terminal and run sudo apt install gnome-sushi 3. Open Nautilus 4. Open the preferences dialog and turn on Expandable Folders in List View. Close the preferences dialog. 5. Press Ctrl+l to focus the address bar and enter /usr/share 6. Use the space bar to open the Sushi previewer on one of the folders 7. With the Sushi preview window open, use the down arrow keys to navigate down to other folders. Keep going down until you go beyond the first page of results in Nautilus. The main nautilus window should scroll down to show these results focused. https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1221 What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME Core, there is a
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Hi Steve. I updated the patches containing the requested changes and uploaded them to https://launchpad.net/~georgiag/+archive/ubuntu/lp1794064/+packages Please let me know if you prefer I attached the debdiffs here. I'm resubscribing ~ubuntu-sponsors. Thanks ** Patch removed: "evince_42.1-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581877/+files/evince_42.1-3ubuntu1.debdiff ** Patch removed: "evince_40.4-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581878/+files/evince_40.4-2ubuntu0.1.debdiff ** Patch removed: "evince_3.36.10-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581879/+files/evince_3.36.10-0ubuntu1.1.debdiff ** Patch removed: "evince_3.28.4-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581880/+files/evince_3.28.4-0ubuntu1.3.debdiff ** Patch removed: "apparmor_3.0.4-2ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581881/+files/apparmor_3.0.4-2ubuntu3.debdiff ** Patch removed: "apparmor_3.0.3-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581882/+files/apparmor_3.0.3-0ubuntu1.1.debdiff ** Patch removed: "apparmor_2.13.3-7ubuntu5.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581884/+files/apparmor_2.13.3-7ubuntu5.2.debdiff ** Patch removed: "apparmor_2.12-4ubuntu5.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581885/+files/apparmor_2.12-4ubuntu5.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Incomplete Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Incomplete Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
Upon further investigation, this is an issue that the package "xserver- xorg-video-vmware" causes to start happening, as on a perfectly fine working Kubuntu 22.04 installing that package only, and restarting, causes the issue to be immediately reproducible, versus non-reproducible without that package being installed. ** Also affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - opening a window: X server crashes. Logging in again and opening a window: system crash - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+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 781076] Re: package doc-base 0.9.5ubuntu2 failed to install/upgrade: Byte order is not compatible at ../../lib/Storable.pm
** Changed in: doc-base (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to doc-base in Ubuntu. https://bugs.launchpad.net/bugs/781076 Title: package doc-base 0.9.5ubuntu2 failed to install/upgrade: Byte order is not compatible at ../../lib/Storable.pm Status in doc-base package in Ubuntu: Fix Released Status in doc-base source package in Oneiric: Fix Released Status in doc-base package in Debian: Fix Released Bug description: Binary package hint: doc-base Upgrading from natty to oneiric. ProblemType: Package DistroRelease: Ubuntu 11.10 Package: doc-base 0.9.5ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 Architecture: i386 Date: Wed May 11 13:10:01 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1) PackageArchitecture: all SourcePackage: doc-base Title: package doc-base 0.9.5ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to oneiric on 2011-04-20 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/doc-base/+bug/781076/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
** Changed in: gnome-shell Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Committed Bug description: [ Impact ] Search [ Test case ] 1. From settings: a. Enable non-fractional scaling of 200% b. Show the dock on the left side c. Enable dock auto-hide 2. Hit Super key and search for any result 3. Hitting Enter key or clicking on an application icon should launch it [ Regression potential ] App grid has wrong sizes or not properly visible --- The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: BugDistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+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 2015760] Re: Accessibility is much worse in GNOME apps that have switched to GTK4
** No longer affects: libadwaita-1 (Ubuntu Mantic) ** No longer affects: gtk4 (Ubuntu) ** Changed in: libadwaita-1 (Ubuntu) Status: Triaged => Fix Released ** No longer affects: gtk4 (Ubuntu Lunar) ** No longer affects: gtk4 (Ubuntu Mantic) -- 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/2015760 Title: Accessibility is much worse in GNOME apps that have switched to GTK4 Status in libadwaita-1 package in Ubuntu: Fix Released Status in libadwaita-1 source package in Lunar: Triaged Bug description: Test Case - From Ubuntu 23.04 Open the Settings app (gnome-control-center) In the left sidebar, click Accessibility Click Seeing. Turn on Screen Reader Use the up and down arrow keys to navigate the list of other Seeing options. What Happens Only the first item in each list is read. (In this case, just High Contrast and Screen Reader but not items like Reduce Animation.) Other Info -- There are several other issues with GTK4 apps. For instance, Epiphany has switched to GTK4 with the GNOME 44 release. The webview is now no longer accessible. Workaround -- It is recommended that people who depend on the Screen Reader use Ubuntu 22.04 LTS until these issues are fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2015760/+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 2022961] Re: Update gnome-shell to 44.2
Hello Jeremy, or anyone else affected, Accepted gnome-shell into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/44.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022961 Title: Update gnome-shell to 44.2 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.2/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) This update requires mutter 44.2 (LP: #2022951). This was done with bumped dependencies in debian/control. gnome-shell 44.2 could be run with mutter 44.1, but mixing different versions of mutter & gnome- shell is not supported upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022961/+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 2013235] Re: Drag and Drop not working in Qt-Applications on Gnome 44
Hello Peng, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- 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/2013235 Title: Drag and Drop not working in Qt-Applications on Gnome 44 Status in Kdenlive: Invalid Status in Mutter: Fix Released Status in OpenShot Video Editor: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact == Drag and drop items within Qt applications not working since upgrade to Ubuntu Lunar developmental release. The items can be picked up then the cursor changed to the "forbid" sign and no further interaction to the app. Confirmed affected apps: 3d Slicer, Krita. Test Case = 1. Start from Ubuntu 23.04 (the default desktop not KDE or Kubuntu) 2. Open a terminal and run sudo apt install krita 3. Install the updated mutter packages then log out and log back in. 4. Run Krita 5. Click New File. Then click Create 6. Select the rectangle from the left sidebar. Draw a rectangle on the canvas. 7. In the menu, select Layer > New > Add Paint Layer 8. Select the ellipse/circle from the left sidebar. Draw an ellipse on the canvas. 9. In the right sidebar, drag Paint Layer 1 on top of Paint Layer 2 so that they switch places. This should work with the updated mutter packages but does not work with mutter 44.0 or mutter 44.1. What Could Go Wrong === This fix is included in the upstream mutter 44.2 release so see the master bug for that update: https://launchpad.net/bugs/2022951 To manage notifications about this bug go to: https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 2022951] Re: Update mutter to 44.2
Hello Jeremy, or anyone else affected, Accepted mutter into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/44.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- 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/2022951 Title: Update mutter to 44.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.2/NEWS This is basically a prerequisite for GNOME Shell 44.2 LP: #2022961 Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This also includes an update of the triple buffering patch to add one commit to fix a potential crash with resuming from suspend. That triple buffering patch is maintained in a targeted mutter 44 branch by Canonical Desktop engineer Daniel. I was unable to easily reproduce the crash so I didn't include LP: #2020652 in the SRU changelog. I dropped 2 patches to mark some tests as flaky since mutter seems to build reliably enough on Debian and Ubuntu without those patches. Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 44.2 to require mutter >= 44.2 (even though GNOME Shell 44.2 appears to run ok with Mutter 44.1). I believe the only way to make the dependency relationship work the other way (not allow Mutter 44.2 with GNOME Shell 44.1) requires bumping the Breaks version but I don't think it's worth using Breaks unless necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2022951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Re: [SRU] Service activation via Systemd socket
This looks very good to me, thanks. My only concern is that the test case includes a manual: systemctl start --user speech-dispatcher.socket Is that in place of re-starting the user session? I would expect the socket unit to be started automatically. Should we ask for a restart of the user session as part of the verification, to ensure this happens correctly? ** Description changed: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] - It's relevance is described in [1], of which I quote the essential parts + Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech- dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 ** Changed in: speech-dispatcher (Ubuntu Lunar) Status: Fix Committed => Incomplete ** Changed in: speech-dispatcher (Ubuntu Kinetic) Status: Fix Committed => Incomplete ** Changed in: speech-dispatcher (Ubuntu Jammy) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Incomplete Status in speech-dispatcher source package in Kinetic: Incomplete Status in speech-dispatcher source package in Lunar: Incomplete Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is
[Desktop-packages] [Bug 2023411] Re: Update libadwaita to 1.3.3
** Also affects: libadwaita-1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: libadwaita-1 (Ubuntu Lunar) Status: New => In Progress ** Changed in: libadwaita-1 (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: libadwaita-1 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libadwaita-1 (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/2023411 Title: Update libadwaita to 1.3.3 Status in libadwaita-1 package in Ubuntu: In Progress Status in libadwaita-1 source package in Lunar: In Progress Bug description: Impact -- 1. There is a new release in the stable 1.3 series. https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.3.3/NEWS Test Case 1 --- After installing the update, open gnome-control-center and nautilus. Ensure that the apps run and that the on/off switches, checkboxes, and other visual elements still display correctly. In gnome-control-center click Appearance in the sidebar. Verify that switching the style between Light and Dark works correctly. Also choose a different accent color and verify that elements like folder icons in Nautilus and on/off switches have correctly adopted the accent color you chose. Test Case 2 --- Run adwaita-1-demo run the style classes demo check that all elements are properly visible and check that link color has enough contrast with background. What Could Go Wrong --- libadwaita is an addon library to GTK4 to allow apps to easily use more of the GNOME style and allow for widgets to be added and improved faster than in the normal GTK development cycle. libadwaita is included in all Ubuntu desktop flavors except for Kubuntu & Lubuntu. Many of the default Ubuntu desktop apps and even GNOME Shell in 23.04 use libadwaita. As a component of GNOME core, there is a micro-release exception for libadwaita. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2023411/+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 2018523] Re: nautilus crashes while searching
I looked up the error ID from the previous comment and it is associated with LP: #2012554 -- 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/2018523 Title: nautilus crashes while searching Status in nautilus package in Ubuntu: Incomplete Bug description: While typing a search string into the nautilus search bar, nautilus stalls and then crashes after a few seconds. This happens a few times a day and is not limited to a specific string. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 15:53:55 2023 InstallationDate: Installed on 2021-05-04 (730 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-20 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018523/+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 2023417] Re: Update nautilus to 44.2.1
** Description changed: Impact + -- + This is a new stable release in the GNOME 44 series + + https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS + + (The current version in Ubuntu 23.04 is 44.0) + + Test Case 0 + --- + Nautilus has a build test suite that will fail the build if the tests fail. + + Test Case 1 + --- + Install the update + Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus + Run Nautilus and ensure that it still works well + + What Could Go Wrong + --- + nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. + + As a component of GNOME Core, there is a micro-release exception for + nautilus + + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + Other Info + -- + This update requires gtk4 4.10.4 (LP: #2023031) + + This update drops 4 cherry-picked patches that have been applied in the + new release + + It also cherry-picks 3 patches from the stable gnome-44 branch (future + nautilus 44.3). + + It also includes a patch included in 44.2 but dropped from 44.2.1 because it was not clear how long it would take for gtk4 4.10.4 to be released. But gtk 4.10.4 was released only a few hours later. + https://gitlab.gnome.org/GNOME/nautilus/-/commit/e193b2ce5d5 ** Also affects: nautilus (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu Lunar) Status: New => In Progress ** Changed in: nautilus (Ubuntu Lunar) Importance: Undecided => High -- 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/2023417 Title: Update nautilus to 44.2.1 Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Lunar: In Progress Bug description: Impact -- This is a new stable release in the GNOME 44 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS (The current version in Ubuntu 23.04 is 44.0) Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME Core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires gtk4 4.10.4 (LP: #2023031) This update drops 4 cherry-picked patches that have been applied in the new release It also cherry-picks 3 patches from the stable gnome-44 branch (future nautilus 44.3). It also includes a patch included in 44.2 but dropped from 44.2.1 because it was not clear how long it would take for gtk4 4.10.4 to be released. But gtk 4.10.4 was released only a few hours later. https://gitlab.gnome.org/GNOME/nautilus/-/commit/e193b2ce5d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023417/+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 2023417] [NEW] Update nautilus to 44.2.1
Public bug reported: Impact ** Affects: nautilus (Ubuntu) Importance: High Status: Fix Committed ** Tags: lunar upgrade-software-version -- 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/2023417 Title: Update nautilus to 44.2.1 Status in nautilus package in Ubuntu: Fix Committed Bug description: Impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023417/+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 2022391] Re: security breach
Thank you for taking the time to report this bug and help make Ubuntu better. 1. Could you try getting us the Technical Report in English? Close the Settings app Open the Terminal then run this command: LANGUAGE=C gnome-control-center 2. Could you take a screenshot of the Device Security page and attach it to this bug report? -- 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/2022391 Title: security breach Status in gnome-control-center package in Ubuntu: New Bug description: i update to lunar-lobster a few days ago (40 days ).I understand that i as a beta version but when i go to the security settings i saw that my firmware didnt pass the test so i dont know if is a problem of the version or is my laptop's problem My computer hardware : System: Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010 serial: Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: UEFI: HUAWEI v: 2.30 date: 07/04/2022 Battery: ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%) volts: 7.5 min: 7.6 CPU: Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz): avg: 1364 min/max: 400/4200 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2) Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi Drives: Local Storage: total: 476.94 GiB used: 149.06 GiB (31.3%) Info: Processes: 337 Uptime: 1h 35m Memory: 7.54 GiB used: 4.27 GiB (56.6%) Shell: Bash inxi: 3.3.25 Informe de seguridad del dispositivo == Detalles del informe Fecha generada: 2023-06-02 22:48:37 Versión de fwupd1.8.12 System details Modelo de hardware: HUAWEI NBD-WXX9 Procesador 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz SO: Ubuntu 23.04 Nivel de seguridad: HSI:0! (v1.8.12) HSI-1 Pruebas Intel Management Engine Version: Falló (No válido) UEFI Platform Key: Correcto (Válido) TPM v2.0:Correcto (Encontrada) Firmware BIOS Region:Correcto (Bloqueada) Firmware Write Protection Lock: Correcto (Activada) Platform Debugging: Correcto (No activada) Intel Management Engine Manufacturing Mode: Correcto (Bloqueada) UEFI Secure Boot:Correcto (Activada) Firmware Write Protection: Correcto (No activada) Intel Management Engine Override:Correcto (Bloqueada) TPM Platform Configuration: Correcto (Válido) HSI-2 Pruebas Intel BootGuard Fuse:Correcto (Válido) Intel BootGuard Verified Boot: Falló (No válido) Intel BootGuard ACM Protected: Falló (No válido) Intel BootGuard: Correcto (Activada) TPM Reconstruction:Falló (No encontrada) IOMMU Protection: Falló (No encontrada) Platform Debugging: Correcto (Bloqueada) HSI-3 Pruebas Suspend To RAM: Correcto (No activada) Intel BootGuard Error Policy: Falló (No válido) Pre-boot DMA Protection: Correcto (Activada) Intel CET: Correcto (Activada) Suspend To Idle: Correcto (Activada) HSI-4 Pruebas Encrypted RAM: Falló (No admitida) Intel SMAP: Correcto (Activada) Pruebas de tiempo de ejecución Firmware Updater Verification: Correcto (No envenenado) Linux Kernel Lockdown: Correcto (Activada) Linux Swap:Falló (No cifrado) Linux Kernel Verification: Correcto (No envenenado) Intel CET: Correcto (Admitida) Eventos de
[Desktop-packages] [Bug 2022002] Re: browsers are not working suddenly...
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022002 Title: browsers are not working suddenly... Status in firefox package in Ubuntu: Incomplete Bug description: same as up ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 1 01:06:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-05 (25 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 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/firefox/+bug/2022002/+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 2022391] Re: security breach
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Information type changed from Public Security to Public -- 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/2022391 Title: security breach Status in gnome-control-center package in Ubuntu: New Bug description: i update to lunar-lobster a few days ago (40 days ).I understand that i as a beta version but when i go to the security settings i saw that my firmware didnt pass the test so i dont know if is a problem of the version or is my laptop's problem My computer hardware : System: Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010 serial: Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: UEFI: HUAWEI v: 2.30 date: 07/04/2022 Battery: ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%) volts: 7.5 min: 7.6 CPU: Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz): avg: 1364 min/max: 400/4200 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2) Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi Drives: Local Storage: total: 476.94 GiB used: 149.06 GiB (31.3%) Info: Processes: 337 Uptime: 1h 35m Memory: 7.54 GiB used: 4.27 GiB (56.6%) Shell: Bash inxi: 3.3.25 Informe de seguridad del dispositivo == Detalles del informe Fecha generada: 2023-06-02 22:48:37 Versión de fwupd1.8.12 System details Modelo de hardware: HUAWEI NBD-WXX9 Procesador 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz SO: Ubuntu 23.04 Nivel de seguridad: HSI:0! (v1.8.12) HSI-1 Pruebas Intel Management Engine Version: Falló (No válido) UEFI Platform Key: Correcto (Válido) TPM v2.0:Correcto (Encontrada) Firmware BIOS Region:Correcto (Bloqueada) Firmware Write Protection Lock: Correcto (Activada) Platform Debugging: Correcto (No activada) Intel Management Engine Manufacturing Mode: Correcto (Bloqueada) UEFI Secure Boot:Correcto (Activada) Firmware Write Protection: Correcto (No activada) Intel Management Engine Override:Correcto (Bloqueada) TPM Platform Configuration: Correcto (Válido) HSI-2 Pruebas Intel BootGuard Fuse:Correcto (Válido) Intel BootGuard Verified Boot: Falló (No válido) Intel BootGuard ACM Protected: Falló (No válido) Intel BootGuard: Correcto (Activada) TPM Reconstruction:Falló (No encontrada) IOMMU Protection: Falló (No encontrada) Platform Debugging: Correcto (Bloqueada) HSI-3 Pruebas Suspend To RAM: Correcto (No activada) Intel BootGuard Error Policy: Falló (No válido) Pre-boot DMA Protection: Correcto (Activada) Intel CET: Correcto (Activada) Suspend To Idle: Correcto (Activada) HSI-4 Pruebas Encrypted RAM: Falló (No admitida) Intel SMAP: Correcto (Activada) Pruebas de tiempo de ejecución Firmware Updater Verification: Correcto (No envenenado) Linux Kernel Lockdown: Correcto (Activada) Linux Swap:Falló (No cifrado) Linux Kernel Verification: Correcto (No envenenado) Intel CET: Correcto (Admitida) Eventos de seguridad del equipo 2023-04-21 20:11:14 Firmware Updater VerificationCorrecto (No activada → No envenenado) 2023-01-28 17:13:05 Firmware Updater VerificatiFalló (No envenenado → No activada)
[Desktop-packages] [Bug 2021948] Re: New bugfix release 23.0.4
This bug was fixed in the package mesa - 23.0.4-0ubuntu1 --- mesa (23.0.4-0ubuntu1) mantic; urgency=medium * New upstream release. (LP: #2021948) - add a revert for amdgpu which missed 23.0.x branch -- Timo Aaltonen Fri, 09 Jun 2023 12:53:37 +0300 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- 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/2021948 Title: New bugfix release 23.0.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Lunar: New Bug description: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. We'll include an additional bugfix (a revert) to fix GPU hangs on some AMD gpu's running certain games. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+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 2022002] Re: browsers are not working suddenly...
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022002 Title: browsers are not working suddenly... Status in gnome-shell package in Ubuntu: New Bug description: same as up ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 1 01:06:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-05 (25 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022002/+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 2021935] Re: ubuntu desktop (mantic) error on post-install login
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2021935/+attachment/5676873/+files/CoreDump.gz ** Information type changed from Public Security to Public ** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2021935 Title: ubuntu desktop (mantic) error on post-install login Status in ayatana-indicator-messages package in Ubuntu: New Bug description: Ubuntu Desktop (mantic) install on hp dc7700 as QA-test. Install was a re-use of SDA6 which was Ubuntu-MATE 23.04 with music added to /home/Music, plus audacious, figlet, fortune, aptitude & other apps added earlier today expecting this re-install (no format) to auto-reinstall The install was PERFECT & as expected, but on first login I got an ERROR, PLEASE REPORT which is why this report. I've not detected any issues though. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ayatana-indicator-messages 22.9.0-1 Uname: Linux 6.2.0-20-generic x86_64 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 31 15:43:45 2023 ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ExecutableTimestamp: 1664708325 ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ProcCwd: /home/guiverc ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: ayatana-indicator-messages UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2021935/+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 2023411] [NEW] Update libadwaita to 1.3.3
Public bug reported: Impact -- 1. There is a new release in the stable 1.3 series. https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.3.3/NEWS Test Case 1 --- After installing the update, open gnome-control-center and nautilus. Ensure that the apps run and that the on/off switches, checkboxes, and other visual elements still display correctly. In gnome-control-center click Appearance in the sidebar. Verify that switching the style between Light and Dark works correctly. Also choose a different accent color and verify that elements like folder icons in Nautilus and on/off switches have correctly adopted the accent color you chose. Test Case 2 --- Run adwaita-1-demo run the style classes demo check that all elements are properly visible and check that link color has enough contrast with background. What Could Go Wrong --- libadwaita is an addon library to GTK4 to allow apps to easily use more of the GNOME style and allow for widgets to be added and improved faster than in the normal GTK development cycle. libadwaita is included in all Ubuntu desktop flavors except for Kubuntu & Lubuntu. Many of the default Ubuntu desktop apps and even GNOME Shell in 23.04 use libadwaita. As a component of GNOME core, there is a micro-release exception for libadwaita. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: libadwaita-1 (Ubuntu) Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/2023411 Title: Update libadwaita to 1.3.3 Status in libadwaita-1 package in Ubuntu: In Progress Bug description: Impact -- 1. There is a new release in the stable 1.3 series. https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.3.3/NEWS Test Case 1 --- After installing the update, open gnome-control-center and nautilus. Ensure that the apps run and that the on/off switches, checkboxes, and other visual elements still display correctly. In gnome-control-center click Appearance in the sidebar. Verify that switching the style between Light and Dark works correctly. Also choose a different accent color and verify that elements like folder icons in Nautilus and on/off switches have correctly adopted the accent color you chose. Test Case 2 --- Run adwaita-1-demo run the style classes demo check that all elements are properly visible and check that link color has enough contrast with background. What Could Go Wrong --- libadwaita is an addon library to GTK4 to allow apps to easily use more of the GNOME style and allow for widgets to be added and improved faster than in the normal GTK development cycle. libadwaita is included in all Ubuntu desktop flavors except for Kubuntu & Lubuntu. Many of the default Ubuntu desktop apps and even GNOME Shell in 23.04 use libadwaita. As a component of GNOME core, there is a micro-release exception for libadwaita. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2023411/+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 1788420] Re: Don't update netpbm-free to 2:10.78.05-0.1 for now
** Changed in: netpbm-free (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to netpbm-free in Ubuntu. https://bugs.launchpad.net/bugs/1788420 Title: Don't update netpbm-free to 2:10.78.05-0.1 for now Status in netpbm-free package in Ubuntu: Fix Released Status in netpbm-free package in Debian: Fix Released Status in netpbm-free package in Fedora: Fix Released Bug description: The new version is in Debian/experimental but has a soname change and require a transition. Unless we find a good reason to want to it now that's probably not for eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1788420/+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 2017445] Re: live session can not access other partitions
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2017445 ** Tags added: iso-testing -- 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/2017445 Title: live session can not access other partitions Status in nautilus package in Ubuntu: Invalid Bug description: I started installation and in 'files' click 'Other Locations' other partition of my PC does not appear. Other partitions whare available with old versions of ubuntu-desktop-installer ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 23 18:52:15 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2017445/+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 1924689] Re: Window border corruption after changing display scale between 100% and 200% in Xorg
This bug is not limited to changing the scale from lower to higher and is not limited to shadows displaying garbage. It also occurs: * when changing the scale from higher to lower * infrequently when new windows or dialogs are created, particularly snap apps like nautilus or gnome-text-editor or modal dialogs such as e.g. evolution Other effects in addition to shadows displaying garbage are: * the window not capturing mouse events correctly, other windows below the garbage window capture the events * the window not being able to capture focus, i.e. come to the front of other windows The situation can be 'fixed' by maximizing + unmaximizing the window, users can TAB-select the window if it cannot be reached with the mouse. (Summary from my duplicate bug report https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023209) -- 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/1924689 Title: Window border corruption after changing display scale between 100% and 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+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 2023209] Re: Windows get wrong z-index and flickering decoration halo
*** This bug is a duplicate of bug 1924689 *** https://bugs.launchpad.net/bugs/1924689 Thanks for the find! -- 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/2023209 Title: Windows get wrong z-index and flickering decoration halo Status in gnome-shell package in Ubuntu: Incomplete Bug description: Frequently, windows such as the new text editor, or the nautilus file browser, or modal dialogs seem to have an in valid z-index, i.e. I cannot click the title bar, and the window is virtually behind everything. The window also has a flickering halo full of garbage from other screen areas which looks like missallocated texture memory? It is possible to bring the window into the foreground, bu e.g. TABing through the applications but it cannot be used because other windows that are 'behind' it capture the mouse events through this window. This can happen with many Windows at the same time, typically after sleep-wake. The Windows can be rescued into normal state by using keyboard shortcuts to maximize-minimize, after which everything is fine. The z-index is correct, mouse events are captured and the decorations look perfect. This started happening with Ubuntu 22.10 and is still present in 23.04, so I assume that it is a bug in Gnome 43? This happens regularly after sleep wake which, in my case, often comes with a zoom switch between 100% (external monitor on dock) and 200% (internal HiDPI laptop screen). I am running Ubuntu on xorg, not Wayland, because screen-sharing individual windows with Zoom does not work on Wayland. I am observing this most frequently with Snap apps such as Nautilus and the new text editor, but also Evolution dialogs have come up with this. May be a timing issue that manifests more frequently with the slower snap apps? I understand that this bug-report is unsatisfying in how to reproduce this, and what exactly the outcome is, but it is pretty random in nature and I can only report the visual/ GUI outcome. I am happy to provide additional input as requested. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-05-04 (765 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: gnome-shell 44.1-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.1-0ubuntu1 Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-26 (43 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023209/+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 1699942] Re: network-manager fails to deprecate addresses
This bug is stale, and it remains unclear if there is a systemd bug, so marking invalid. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1699942 Title: network-manager fails to deprecate addresses Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1979352] Re: system frozen after sleep
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Incomplete Status in acpid package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in upower package in Ubuntu: Incomplete Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 2023403] [NEW] Dell XPS-17 trackpad stutters frequently
Public bug reported: Randomly, my trackpad has a lot of trouble detecting movement, for 10 to 20 seconds, until it comes back. Used to happen every day in previous versions, now every 3 days or so. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:43:21 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar performance ubuntu wayland-session -- 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/2023403 Title: Dell XPS-17 trackpad stutters frequently Status in xorg package in Ubuntu: New Bug description: Randomly, my trackpad has a lot of trouble detecting movement, for 10 to 20 seconds, until it comes back. Used to happen every day in previous versions, now every 3 days or so. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:43:21 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name:
[Desktop-packages] [Bug 2023401] [NEW] Upon shutdown, shutdown process doesn't complete and the computer stays on
Public bug reported: When I want to shutdown my computer, very often since last Ubuntu version, the process seems not to go to the end, and the computer never shuts down. I used not to notice it, physically close my laptop and put it back in my bag, then hours later find it very hot and with fans going at full speed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:35:50 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze lunar ubuntu wayland-session -- 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/2023401 Title: Upon shutdown, shutdown process doesn't complete and the computer stays on Status in xorg package in Ubuntu: New Bug description: When I want to shutdown my computer, very often since last Ubuntu version, the process seems not to go to the end, and the computer never shuts down. I used not to notice it, physically close my laptop and put it back in my bag, then hours later find it very hot and with fans going at full speed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:35:50 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine:
[Desktop-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
This bug is stale, so marking Won't Fix for systemd. For any similar issues on newer releases/hardware, new bugs should be opened. ** Changed in: systemd (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in pm-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+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 2023400] [NEW] Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification
Public bug reported: When I receive an e-mail, a notification appears. I click it in order for Thunderbird to open on the correct e-mail. But Thunderbird doesn't open right away, a new notification "'Thunderbird' is ready" appears, which I have to click in order for Thunderbird to open correctly. Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:31:36 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session -- 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/2023400 Title: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification Status in xorg package in Ubuntu: New Bug description: When I receive an e-mail, a notification appears. I click it in order for Thunderbird to open on the correct e-mail. But Thunderbird doesn't open right away, a new notification "'Thunderbird' is ready" appears, which I have to click in order for Thunderbird to open correctly. Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:31:36 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023
[Desktop-packages] [Bug 1882034] Re: cannot start X session with NIS account
Marking invalid for systemd due to age, and it being unclear whether this is in fact a systemd bug. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1882034 Title: cannot start X session with NIS account Status in gdm3 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: When login with a NIS account, X does not start, or more precisely it starts and exits immediately. Only errors in logs is: (EE) systemd-logind: failed to get session: PID 4335 does not belong to any known session X11/gdm login works fine with local accounts. SSH/terminal console login with NIS accounts works fine. /etc/X11/Xwrapper.config: allowed_users=anybody I've seen several reports of such problems under other versions (eg 19.10), but no working solutions was found. It seems that the problem is the same with lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 08:59:25 2020 InstallationDate: Installed on 2019-11-26 (190 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023215] Re: [SRU] appstream-glib can't handle em or code tags, breaking Flathub
I successfully completed the test case using appstream-glib
0.7.18-2ubuntu1 on Ubuntu 22.04 LTS.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: focal jammy verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/2023215
Title:
[SRU] appstream-glib can't handle em or code tags, breaking Flathub
Status in appstream-glib package in Ubuntu:
Fix Released
Status in appstream-glib source package in Focal:
In Progress
Status in appstream-glib source package in Jammy:
Fix Committed
Bug description:
[ Impact ]
* Currently, any application that is using modern AppStream metadata
containing / tags in their description, and that is still using the
deprecated appstream-glib will fail to parse this data.
* Unfortunately, this affects some high-visibility applications now, like
Flatpak, which are unable to perform proper searches. See
https://github.com/flatpak/flatpak/issues/5434 for reference.
* This kind of issue may potentially affect more tools as well.
[ Test Plan ]
1. Open a terminal and run
sudo apt install flatpak
2. Then run
flatpak remote-add --if-not-exists flathub
https://flathub.org/repo/flathub.flatpakrepo
3. Run
flatpak search meld
The broken output may look something like:
F: Failed to parse
/var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz file: Error
on line 1960 char 29: already set '
Organic Maps is a free Android & iOS offline maps app for travelers,
tourists, hikers, and cyclists.
It uses crowd-sourced OpenStreetMap data and is developed with love by
' and tried to replace with ' ('
No matches found
4. Install the updated appstream-glib packages.
5. Restart your computer then log back in.
6. Open a terminal and run
flatpak search firefox
The working output looks something like
Name DescriptionApplication ID Version Branch
Remotes
Meld Compare and merge your files org.gnome.meld 3.22.0 stable
flathub
[ Where problems could occur ]
* The reverse-dependencies for appstream-glib in Ubuntu Jammy are:
flatpak-tests
unity
libmalcontent-ui-0-0
libappstream-glib-dev
gir1.2-appstreamglib-1.0
appstream-util
flatpak
* Flatpak should continue to work, and there should be no new errors
in GNOME/Unity.
[ Other Info ]
* None. Updating this should mainly help Flatpak users and should
have no ill effects on any other component of the OS.
* This issue was fixed upstream in appstream-glib 0.8.1 which is
available in Ubuntu 22.10 and newer releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/2023215/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Incomplete Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Incomplete Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Changed in: pcsc-lite (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023382] Re: The self-diagnosis and smart item is not active on the nvme and usb flash drives
** Changed in: gnome-disk-utility Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2023382 Title: The self-diagnosis and smart item is not active on the nvme and usb flash drives Status in GNOME Disks: New Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: this bug was raised in the upstream. Since this problem is general, and not a specific distribution. https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/298 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/2023382/+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 2023382] Re: The self-diagnosis and smart item is not active on the nvme and usb flash drives
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2023382 Title: The self-diagnosis and smart item is not active on the nvme and usb flash drives Status in GNOME Disks: Unknown Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: this bug was raised in the upstream. Since this problem is general, and not a specific distribution. https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/298 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/2023382/+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 2023382] Re: The self-diagnosis and smart item is not active on the nvme and usb flash drives
** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #298 https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/298 ** Also affects: gnome-disk-utility via https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/298 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2023382 Title: The self-diagnosis and smart item is not active on the nvme and usb flash drives Status in GNOME Disks: Unknown Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: this bug was raised in the upstream. Since this problem is general, and not a specific distribution. https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/298 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/2023382/+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 2023382] [NEW] The self-diagnosis and smart item is not active on the nvme and usb flash drives
Public bug reported: this bug was raised in the upstream. Since this problem is general, and not a specific distribution. https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/298 ** Affects: gnome-disk-utility Importance: Unknown Status: Unknown ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2023382 Title: The self-diagnosis and smart item is not active on the nvme and usb flash drives Status in GNOME Disks: Unknown Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: this bug was raised in the upstream. Since this problem is general, and not a specific distribution. https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/298 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/2023382/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
Thank you for the report. I noted this in https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter for future updates that rely on the exception. Would it be appropriate to add this Test Plan to future mutter updates that are based on the exception? If so, please could you amend the wiki? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
** Also affects: mutter (Ubuntu Mantic) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Lunar) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2022889] Re: [SRU] libreoffice 7.5.4 for lunar
Hello Rico, or anyone else affected, Accepted libreoffice into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.4-0ubuntu0.23.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2022889 Title: [SRU] libreoffice 7.5.4 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.4 is in its forth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.4_release * Version 7.5.3 is currently released in lunar. For a list of fixed bugs compared to 7.5.3 see the list of bugs fixed in the release candidates of 7.5.4 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14936260/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230605_142135_2b00f@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230605_113325_1478c@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230605_085103_17f17@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230605_092012_906e0@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230605_104011_2ff4a@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence
[Desktop-packages] [Bug 2022909] Re: report a bug
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please note that bug reports should refer to just one issue as references to multiple problems will cause confusion as different packages and developers might be involved. Therefore, this bug report report should just be about your printing issue. I'm changing the bug description to reflect that. https://wiki.ubuntu.com/Bugs/FindRightPackage#Printing suggest that the errant package might be 'cups' so I'm moving this bug report so that those that can help with printing problems are made aware of this report. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2022909 as you haven't told us which of the several supported releases of Ubuntu you are using. Please then change the status of this bug report back to 'New'. Please note that "recent:///1506de527eb9a8aad255c0d3647d9d8a" refers to a file on your PC. It has not been uploaded to the bug report. Thank you! ** Summary changed: - report a bug + printing problem ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2022909 Title: printing problem Status in cups package in Ubuntu: Incomplete Bug description: Good morning. I still have a problem with my printer machine,I.In fact I tried many options possible to my simple knowledge an d it was in vain ,and in the end I received an input saying that they can not resolve my problem and I have to report it as a bug,so they ask me to save the file they give me in order to send in case I report the bug,and here I will attach the file so you can see for yourselves.Other thing I noticed is after this problem when I turn the power off on my laptop it takes much time than normally to shut down,Before it was on the click.Thank you for the help.greetings recent:///1506de527eb9a8aad255c0d3647d9d8a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2022909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hello Daniel, I've also been debugging this issue and noticed something weird while reproducing it. It seems that resizing the screen via resizing the NICE DCV client does not invoke the `meta_monitor_config_manager_set_current` method, so the current config and the history are untouched. Let's say we have an initial resolution of QxZ@T hz, sf 1(scale factor). The NICE DCV client screen resize changes it to WxH@F sf 1.5, but libmutter still thinks the screen is at QxZ@T sf 1. At this point, `xrandr` output no longer shows QxZ@T hz as a supported resolution. When the user tries to change the scale, the change is registered as both the resolution change and the scale change as per the perspective of "libmutter", and if the user proceeds to accept this configuration, everything is fine because the Xdcv already lists `WxH@F` as a supported resolution, but if not (i.e. user tries to revert back to the previous) it fails because QxZ@T hz is no longer on the supported resolution set. Therefore, I think one of the problems we're facing here is libmutter/Xdcv being out-of-sync when the screen resolution is changed via the NICE DCV client. I'm currently looking into how we can reflect the client resolutions to libmutter (I'm not well-versed in mutter codebase so progressing a little bit slow) I'll continue to post my findings as I progress. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed
[Desktop-packages] [Bug 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
Fixed in 45: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441 but I'll wait till next week to backport it to 44 because it's Friday night and I keep changing my mind about the design of the fix. -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2022941] Re: Zoom window not centered on text cursor
@niels862 further to comment #1, bug reports filed against the Ubuntu project without specifying a package will seldom attract the attention of those that can help resolve problems. I'm moving this to the 'mutter' package. This will bring your report to the attention of Ubuntu's Desktop Team which will assess your issue and move to the correct package if necessary. ** Package changed: ubuntu => mutter (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022941 Title: Zoom window not centered on text cursor Status in mutter package in Ubuntu: New Bug description: In certain applications, the zoomed in window moves to center on the text cursor instead of the pointer when typing but it does not focuses properly. This causes the typed text to be completely out of view. I use the default full-screen zoom in Ubuntu under the accessibility settings with the following settings: Magnification: 4.00 - 6.00 Magnifier position: Follow mouse cursor The problem primarily occurs when using Alt+Tab to witch tabs, but it sometimes appears when switching normally. To reproduce the problem, the following steps can be followed: - Activate the zoom function. - Start up Files and rename a file. - The zoomed in window will move to the upper left corner. Other applications in which the problem sometimes occurs (mostly when using Alt+Tab): Firefox, VSCode I also want to note that for other applications like Text Editor or Terminal, the cursor is always followed correctly. lsb_release -rd: Description: Ubuntu 22.04.2 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2022941/+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 2021948] Re: New bugfix release 23.0.4
** Description changed: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. + + We'll include an additional bugfix (a revert) to fix GPU hangs on some + AMD gpu's running certain games. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. -- 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/2021948 Title: New bugfix release 23.0.4 Status in mesa package in Ubuntu: New Status in mesa source package in Jammy: New Status in mesa source package in Lunar: New Bug description: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. We'll include an additional bugfix (a revert) to fix GPU hangs on some AMD gpu's running certain games. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+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 2023375] [NEW] Feature request - Allow the user to select currencies in Preferences
Public bug reported: If a user just uses 2-3 currencies, I don't see a reason to give him the whole range of currencies in the drop downs in Financial mode. My suggestion is to let the user select the currencies that he is going to use in the Preferences, and only these currencies will appear in Financial mode drop downs. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2023375 Title: Feature request - Allow the user to select currencies in Preferences Status in gnome-calculator package in Ubuntu: New Bug description: If a user just uses 2-3 currencies, I don't see a reason to give him the whole range of currencies in the drop downs in Financial mode. My suggestion is to let the user select the currencies that he is going to use in the Preferences, and only these currencies will appear in Financial mode drop downs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2023375/+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 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
If your cursor is skipping frames then I think the main fix for that is coming in mutter 45: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2679 Although I hope we can figure out a simpler patch to backport to 44. The issue is described in: https://gitlab.gnome.org/GNOME/mutter/-/issues/2459 Frame skips in Wayland sessions on non-Intel GPUs might also need mutter 44.1 (like with bug 2017097). If your cursor is smooth but just one frame higher latency then I am working on bug 2023363 for that. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2459 https://gitlab.gnome.org/GNOME/mutter/-/issues/2459 -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem didn't occur in previous version of ubuntu based on xorg. Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc or when heavy operations are done on it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-13 (50 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+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 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media
** Changed in: gsettings-desktop-schemas Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in GSettings Desktop Schemas: New Status in gnome-control-center package in Ubuntu: Confirmed Bug description: There is a MAJOR SECURITY VULNERABILITY in Ubuntu Desktop since release 18.04 ! Recently I used Ubuntu 22.04 LTS and noticed that the issue still exist! I don’t know the reason for it, but default values for “Removable Media” are VERY Risky! It will automatically run the software which is attached to the removable media. Why? Why has Ubuntu still didn’t disable that option? The following is the default configuration (the “bad” configuration): https://imgur.com/XXXQlV2 The following is the configuration which Ubuntu should be having (it is the fix to the problem): https://imgur.com/a/0JeM6ve Please change the default configurations for Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1983778/+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 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
I tried the latest suggestions of "CLUTTER_PAINT=disable-dynamic-max- render-time" as well as "MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0..." but neither of it helped. I had to go back to using Xorg. -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem didn't occur in previous version of ubuntu based on xorg. Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc or when heavy operations are done on it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-13 (50 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics
This bug was fixed in the package mesa - 23.0.3-0ubuntu2 --- mesa (23.0.3-0ubuntu2) mantic; urgency=medium * rules: Set VERSION so that it also includes the packaging revision. (LP: #2020604) -- Timo Aaltonen Tue, 30 May 2023 09:53:55 +0300 ** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released -- 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/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: Confirmed Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media
** Bug watch added: gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues #46 https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/46 ** Changed in: gsettings-desktop-schemas Status: Fix Released => Unknown ** Changed in: gsettings-desktop-schemas Remote watch: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2522 => gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues #46 -- 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/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in GSettings Desktop Schemas: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Bug description: There is a MAJOR SECURITY VULNERABILITY in Ubuntu Desktop since release 18.04 ! Recently I used Ubuntu 22.04 LTS and noticed that the issue still exist! I don’t know the reason for it, but default values for “Removable Media” are VERY Risky! It will automatically run the software which is attached to the removable media. Why? Why has Ubuntu still didn’t disable that option? The following is the default configuration (the “bad” configuration): https://imgur.com/XXXQlV2 The following is the configuration which Ubuntu should be having (it is the fix to the problem): https://imgur.com/a/0JeM6ve Please change the default configurations for Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1983778/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
** Description changed: + [ Impact ] + Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: - BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) - BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always - GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never + BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) + BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always + GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never - ProblemType: Bug - DistroRelease: Ubuntu 23.10 - Package: mutter 44.2-1ubuntu1 - ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 - Uname: Linux 6.2.0-21-generic x86_64 - ApportVersion: 2.26.1-0ubuntu3 - Architecture: amd64 - CasperMD5CheckResult: pass - Date: Fri Jun 9 14:58:58 2023 - InstallationDate: Installed on 2023-05-23 (16 days ago) - InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230522) - SourcePackage: mutter - UpgradeStatus: No upgrade log present (probably fresh install) + [ Test Plan ] + + 0. Find a machine with an Intel GPU. + + 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings + + 2. Reboot. + + 3. Log in to a Wayland session and wait for the desktop to become idle. + + 4. Also log in via ssh from a remote machine and run: +journalctl -f /usr/bin/gnome-shell + + 5. Over your idle desktop just wiggle the mouse continuously. + + 6. In your ssh login, verify that the resulting log messages from gnome- + shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: + Triple buffering:" when only the mouse pointer is moving. + + [ Where problems could occur ] + + In the frame rate and latency of the Ubuntu desktop experience. -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2023363] Re: Mouse input latency in GNOME 44 Wayland sessions is one frame higher than it should be
It's a regression in 44.1 caused by the fix for bug 2017137 / bug 2017097. Nobody noticed because one frame of latency is so hard to notice. ** Tags added: regression-update ** Tags added: regression ** Summary changed: - Mouse input latency in GNOME 44 Wayland sessions is one frame higher than it should be + Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier ** Tags added: lunar -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Bug description: Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 9 14:58:58 2023 InstallationDate: Installed on 2023-05-23 (16 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230522) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
** Tags removed: verification-needed verification-needed-focal verification-needed-jammy ** Tags added: verification-done verification-done-jammy verification-needed-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023365] [NEW] Window movement is delayed in screen share in Wayland
Public bug reported: In Wayland, - Open Chromium or Firefox - Go to https://mozilla.github.io/webrtc-landing/gum_test.html - Start full screen capture - Drag some windows around Expected: The movement of each window is reproduced in the screen cast smoothly and immediately. Observed: It takes a couple of seconds until each moved window's position is verified in the screen cast. The issue does not appear in Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 Date: Fri Jun 9 09:11:35 2023 InstallationDate: Installed on 2022-05-16 (388 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-01-17 (142 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland ** Attachment added: "Screencast from 2023-06-09 09-04-13.webm" https://bugs.launchpad.net/bugs/2023365/+attachment/5678751/+files/Screencast%20from%202023-06-09%2009-04-13.webm -- 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/2023365 Title: Window movement is delayed in screen share in Wayland Status in mutter package in Ubuntu: New Bug description: In Wayland, - Open Chromium or Firefox - Go to https://mozilla.github.io/webrtc-landing/gum_test.html - Start full screen capture - Drag some windows around Expected: The movement of each window is reproduced in the screen cast smoothly and immediately. Observed: It takes a couple of seconds until each moved window's position is verified in the screen cast. The issue does not appear in Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 Date: Fri Jun 9 09:11:35 2023 InstallationDate: Installed on 2022-05-16 (388 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-01-17 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023365/+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 2023363] Re: Mouse input latency in GNOME 44 Wayland sessions is one frame higher than it should be
** Summary changed: - Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment + Mouse input latency in GNOME 44 Wayland sessions is one frame higher than it should be -- 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/2023363 Title: Mouse input latency in GNOME 44 Wayland sessions is one frame higher than it should be Status in mutter package in Ubuntu: In Progress Bug description: Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 9 14:58:58 2023 InstallationDate: Installed on 2023-05-23 (16 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230522) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
BTW, what does this command return in an AWS Workspace? Any different to the VM? xrandr --verbose -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up- installing-linux.html One relevant difference is that Workspaces uses a custom X11 server /usr/bin/Xdcv, instead of /usr/lib/xorg/Xorg, and they have the following process being started: /usr/bin/Xdcv
[Desktop-packages] [Bug 2023363] [NEW] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment
Public bug reported: Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 9 14:58:58 2023 InstallationDate: Installed on 2023-05-23 (16 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230522) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: amd64 apport-bug mantic performance triple-buffering -- 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/2023363 Title: Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment Status in mutter package in Ubuntu: In Progress Bug description: Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 9 14:58:58 2023 InstallationDate: Installed on 2023-05-23 (16 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230522) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2023151] Re: evolution-alarm-notify crashed with signal 5
I'm going to mark this incomplete I suspect the issue is a consequence of a bad install - https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2023000 Regardless, if it's a real issue, it'll be re-filed... ** Changed in: evolution-data-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2023151 Title: evolution-alarm-notify crashed with signal 5 Status in evolution-data-server package in Ubuntu: Incomplete Bug description: I have no details to provide sorry. This is a QA test install only.. with packages & VERY MINOR change(s) having taken place on it ... ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: evolution-data-server (not installed) ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Tue Jun 6 16:30:18 2023 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2023-06-06 (1 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2023151/+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 2023158] Re: deja-dup-monitor crashed with signal 5
I'm going to mark this incomplete I suspect the issue is a consequence of a bad install - https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2023000 Regardless, if it's a real issue, it'll be re-filed... ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2023158 Title: deja-dup-monitor crashed with signal 5 Status in deja-dup package in Ubuntu: Incomplete Bug description: I have no useful details to provide sorry. This is a QA test install only.. with packages & VERY MINOR change(s) having taken place on it ... (on subsequent boot; these messages are now appearing & requesting me to file.. I'm in the middle of another QA-test install in another partition on this system & was only booting this system to ensure the newly installed xubuntu.mantic didn't impact here). ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: deja-dup (not installed) ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: LXQt Date: Tue Jun 6 16:29:58 2023 ExecutablePath: /usr/libexec/deja-dup/deja-dup-monitor InstallationDate: Installed on 2023-06-06 (1 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/deja-dup/deja-dup-monitor Signal: 5 SourcePackage: deja-dup StacktraceTop: () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: deja-dup-monitor crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2023158/+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
