[Desktop-packages] [Bug 2023049] Re: nautilus shows wrong files after delete
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 It seems the same as bug #2022851 which should be fixed with the gtk4 candidate update in lunar-proposed ** This bug has been marked a duplicate of bug 2022851 Nautilus displays invalid directory content after deleting -- 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/2023049 Title: nautilus shows wrong files after delete Status in nautilus package in Ubuntu: Confirmed Bug description: Test case: 1) in a new directory: touch 1 2 3 result: files appear in nautilus 2) delete file 1 result: 3 disappears, 1 and 2 are shown 3) refresh using F5 results: 2 and 3 are shown I noticed this bizarre issue a few days ago and therefore reinstalled the 23.04 OS partition. Issue remains even after * fresh install of 23.04 on OS partition * gsettings reset-recursively org.gnome.nautilus * sudo rm -rf ~/.config/nautilus 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: Tue Jun 6 16:04:48 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1663, 327)' InstallationDate: Installed on 2023-06-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) 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 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/2023049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
just enable proposed, run 'apt install libgl1-mesa-dri libegl-mesa0' and you should get all relevant updates for mesa and nothing else -- 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: Triaged 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: New 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 2022930] Re: When deleting a file via Nautilus, following files can not be deleted
Thank you for your bug report. It sounds like that could be the same cause than bug #2022851, could you try if the gtk4 update in lunar- proposed fixes the issue for you? ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- 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/2022930 Title: When deleting a file via Nautilus, following files can not be deleted Status in nautilus package in Ubuntu: Incomplete Bug description: 1. Try to delete a file via Nautilus (Files). On the bottom right corner you will see the whole name of the file with the word selected on it. Press the Delete key on the keyboard and press enter. 2. try to delete a second file on the same folder. It will now show as "" selected instead of the actual name of the file and it will not delete anything. 3. You need to refresh nautilus for it to work once again, but it will only work once, you need to refresh every time you delete a file. An image on how it looks can be seen here: https://imgur.com/a/U5gumKp ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 07:26:13 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1402, 866)' InstallationDate: Installed on 2023-04-20 (45 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: 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 nautilus-share0.7.5-0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022882] Re: Lunar - gnome-shell crashes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/2022882 Title: Lunar - gnome-shell crashes Status in gnome-shell package in Ubuntu: Confirmed Bug description: Since updating from Kinetic to Lunar my gnome-shell regularly crashes. It happens out of nothing, sorry I cannot give any hint on how to reproduce it :( This is happening ~ 3 to 5 times a day. 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 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:04:13 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (139 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-10 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013042] Re: Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out
** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/2013042 Title: Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Lock screen's blurry wallpaper vanishes on the primary monitor if a second monitor is plugged in/out. I'm left with just the lock screen text on a black background. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2013042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009687] Re: [lunar] Nvidia GPU unused but still powered
We've narrowed a related (hopefully the same) issue down to being introduced in mutter!1968, which is the precursor to triple buffering. Not triple buffering itself, but part of the same patch. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1757415 ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/2009687 Title: [lunar] Nvidia GPU unused but still powered Status in GNOME Shell: New Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, Lenovo Legion 5 16" i7 12700H RTX 3070 Ti Nvidia 525 proprietary driver (official Ubuntu packages) Nvidia on-demand mode Ubuntu Wayland or Xorg sessions Ubuntu Lunar up to date I noticed a high power usage using powertop (or simply remaining time in g-c-c...). Nvidia driver seems offloaded but gpu power usage still shows ~ 9W -> 23W, random. uname -a Linux ** 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux nvidia-smi Wed Mar 8 10:59:21 2023 +-+ | NVIDIA-SMI 525.85.05Driver Version: 525.85.05CUDA Version: 12.0 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 34CP8 9W / 50W | 4MiB / 8192MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 5445 G /usr/bin/gnome-shell3MiB | +-+ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Graphics (ADL GT2) (0x46a6) Version: 22.3.6 Accelerated: yes Video memory: 31821MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.6 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 lspci 00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:06.2 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #2 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00
[Desktop-packages] [Bug 2022882] Re: Lunar - gnome-shell crashes
Drag and drop crashes are likely to be fixed in the 44.1 update (bug 2012230, bug 2012100). But if you want to debug your particular case further then please follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- 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/2022882 Title: Lunar - gnome-shell crashes Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since updating from Kinetic to Lunar my gnome-shell regularly crashes. It happens out of nothing, sorry I cannot give any hint on how to reproduce it :( This is happening ~ 3 to 5 times a day. 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 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:04:13 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (139 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-10 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023049] Re: nautilus shows wrong files after delete
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 I confirm this is fixed when switching to lunar-proposed. Thank you very much. -- 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/2023049 Title: nautilus shows wrong files after delete Status in nautilus package in Ubuntu: Confirmed Bug description: Test case: 1) in a new directory: touch 1 2 3 result: files appear in nautilus 2) delete file 1 result: 3 disappears, 1 and 2 are shown 3) refresh using F5 results: 2 and 3 are shown I noticed this bizarre issue a few days ago and therefore reinstalled the 23.04 OS partition. Issue remains even after * fresh install of 23.04 on OS partition * gsettings reset-recursively org.gnome.nautilus * sudo rm -rf ~/.config/nautilus 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: Tue Jun 6 16:04:48 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1663, 327)' InstallationDate: Installed on 2023-06-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) 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 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/2023049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778983] Re: Resume from suspend on Wayland breaks window positioning
** Changed in: mutter (Ubuntu) Status: Won't Fix => Confirmed ** Tags removed: bionic ** 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/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Confirmed Bug description: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1778983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755501] Re: GfxBench renders fullscreen content at wrong size in Gnome desktop (on X)
** Tags removed: bionic ** Tags added: focal ** Changed in: mutter (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1755501 Title: GfxBench renders fullscreen content at wrong size in Gnome desktop (on X) Status in mutter package in Ubuntu: New Bug description: Setup: * FullHD monitor (1920x1080 resolution) * Ubuntu 18.04 (pre-release) with Gnome/mutter 3.27.92, on top of X * GfxBench benchmark suite from Kishonti: https://gfxbench.com/ (one of the most common 3D benchmarks supporting Linux) Example test-case: * bin/testfw_app --gfx glfw --gl_api desktop_core --width 1920 --height 1080 --fullscreen 1 --test_id gl_manhattan Expected outcome: * Benchmark renders always in full monitor resolution, like happens with all other desktops (Unity, XFCE, KDE) Actual outcome: * There's a black bar at the top of the screen and benchmark content is vertically scaled to smaller size than fullscreen Same thing happens also with Ubuntu 16.04 version of Mutter (v3.18.3), so it's not a (recent) regression. I assume that any other similar test-case which: * requests full resolution fullscreen window * uses window size that it gets * but doesn't support resizing the window afterwards Would have the same issue. From xwininfo, xev and apitrace output I can see following: * Window is created in correct resolution * app sets some window properties * WM reparents it * WM maps window's parent to screen * WM resizes window's parent a smaller size -> I think this is the point when the application sets its GL viewport to wrong size * Some _NET_WM properties are set (by WM?) * WM resizes window's parent back to correct size, which is apparently too late for this application When comparing this to what Unity does: * Unity or app sets properties after reparenting * There's an extra intermediate window between the resized parent and the benchmark window * Resizing of the parent window to smaller size happens before that window is mapped on screen. I assume this means that the application doesn't get window resize event for the wrong window size * extra _NET_WM properties are set after parent is re-sized back to correct size -> this probably makes the time window with wrong window size shorter Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/60 I'm filing this here too because: * This was tested on latest Ubuntu 18.04 * Mutter upstream bug tracker doesn't support attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1755501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
That's a lot of private proprietary bugs. Are you sure you can't close most of them as duplicates of each other? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023151] [NEW] evolution-alarm-notify crashed with signal 5
*** This bug is a security vulnerability *** Public security bug reported: 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: ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic need-amd64-retrace ** Information type changed from Private to Public Security -- 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: New 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] [NEW] deja-dup-monitor crashed with signal 5
*** This bug is a security vulnerability *** Public security bug reported: 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: ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic need-amd64-retrace ** Information type changed from Private to Public Security -- 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: New 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
[Desktop-packages] [Bug 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session
Private bug 2016299 now has more complete stack traces. -- 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/2015386 Title: NVIDIA quad-GPU system crashes starting Wayland session Status in mutter package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022155] Re: File selection dialog does not allow selecting multiple files using Ctrl
** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu) ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022155 Title: File selection dialog does not allow selecting multiple files using Ctrl Status in gtk+3.0 package in Ubuntu: New Status in gtk4 package in Ubuntu: New Bug description: I have no idea if I have filed this against the right package. It happens in both Firefox and Chrome, whatever provides their file selection dialog for uploads is apparently the problem, I don't know if that's gnome shell or something else. When I want to upload multiple files in a web browser, I can do that if I hit shift, and then click another file. But, that selects not just the two files that I clicked on, but every file in between them in the dialog (which is the expected behaviour when shift clicking in a file selection dialog). When I just want to select two files that are not displayed next to each other, I expect to be able to Ctrl+click on the files, and for them and only them to be selected. But, this doesn't happen, the second file does not get selected when I do that. 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 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 10:08:32 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-08-04 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2022155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020803] Re: logging in at the lock screen causes the system to log me out and start over.
Thanks. Your journal.txt shows gnome-shell is crashing in: /home/leon/.local/share/gnome- shell/extensions/topiconsfix@ales...@devnullmail.com so please delete that extension. It's also not supported here. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/2020803 Title: logging in at the lock screen causes the system to log me out and start over. Status in gnome-shell package in Ubuntu: Invalid Bug description: After my system lock screen enables (whether through timeout or if I manually lock it), unlocking the system causes all programs to forcibly shut down and a new session to start. Effectively, I'm logging in fresh every time the lock screen is enabled. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gdm3 44.0-1ubuntu1 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 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 25 12:41:01 2023 InstallationDate: Installed on 2020-12-03 (902 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: Upgraded to lunar on 2023-04-26 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022320] Re: the user logout and all activitities where lost, all applications where closed without saving
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2022320 Title: the user logout and all activitities where lost, all applications where closed without saving Status in Ubuntu: Incomplete Bug description: here is a log part of the log I was training a neural network on my GPU when that happen. Jun 2 11:26:14 Experement snapd[1026]: devicemgr.go:2300: no NTP sync after 10m0s, trying auto-refresh anyway Jun 2 11:26:14 Experement snapd[1026]: autorefresh.go:594: Cannot prepare auto-refresh change: Post https://api.snapcraft.io/v2/snaps/refresh: dial tcp: lookup api.snapcraft.io: No address associated with hostname Jun 2 11:26:14 Experement snapd[1026]: stateengine.go:149: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: dial tcp: lookup api.snapcraft.io: No address associated with hostname Jun 2 11:28:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/112835.077228:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:29:22 Experement google-chrome.desktop[2861]: [2854:2884:0602/112922.423721:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:29:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/112935.114565:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:29:50 Experement google-chrome.desktop[2861]: [2854:2884:0602/112950.414014:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:30:01 Experement CRON[3581]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi) Jun 2 11:30:44 Experement google-chrome.desktop[2861]: [2854:2884:0602/113044.132395:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:30:51 Experement google-chrome.desktop[2861]: [2854:2884:0602/113051.623021:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:31:12 Experement systemd[1]: Started Run anacron jobs. Jun 2 11:31:12 Experement anacron[3582]: Anacron 2.3 started on 2023-06-02 Jun 2 11:31:12 Experement systemd[1]: Starting Cleanup of Temporary Directories... Jun 2 11:31:12 Experement anacron[3582]: Normal exit (0 jobs run) Jun 2 11:31:12 Experement systemd[1]: anacron.service: Deactivated successfully. Jun 2 11:31:12 Experement systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 2 11:31:12 Experement systemd[1]: Finished Cleanup of Temporary Directories. Jun 2 11:31:24 Experement google-chrome.desktop[2861]: [2854:2884:0602/113124.701284:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:31:31 Experement google-chrome.desktop[2861]: [2854:2884:0602/113131.182781:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:31:36 Experement google-chrome.desktop[2861]: [2854:2884:0602/113136.547141:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:31:49 Experement google-chrome.desktop[2861]: [2854:2884:0602/113149.340472:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:38:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/113835.095153:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:39:22 Experement google-chrome.desktop[2861]: [2854:2884:0602/113922.438095:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:39:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/113935.128280:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:40:44 Experement google-chrome.desktop[2861]: [2854:2884:0602/114044.169402:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:40:51 Experement google-chrome.desktop[2861]: [2854:2884:0602/114051.659049:ERROR:checkin_request.cc(243)] Check
[Desktop-packages] [Bug 2020682] Re: Release adsys 0.12.0
I see that we've done this sort of wholesale backport once before, but this doesn't seem like it falls under the "other safe cases" part of the SRU criteria: https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases It seems like this should have a more formal process? I don't see any special case documentation on the wiki, nor can I find it discussed on ubuntu-release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020682 Title: Release adsys 0.12.0 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Incomplete Status in adsys source package in Lunar: New Bug description: ADSys is part of the enterprise desktop offerings and customers are requesting the new version to be released for 22.04 LTS. [Impact] * ADSys depends on Go 1.20, so the golang-1.20 package must be backported to 22.04 as well. * The new version has some features that are heavily requested by enterprise customers running the LTS. [Test Plan] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5. AD user should be able to log in (https://github.com/ubuntu/adsys/wiki/2.-Prerequisites); 2. Install admx and adml files on your AD controller (https://github.com/ubuntu/adsys/wiki/3.-AD-Setup); 3. Configure some Group Policies in the AD server (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO); 4. Install ADSys, reboot the machine and login in as an AD user; 5. Ensure that the configuration done in the AD server is reflected on the Ubuntu machine; [Where problems could occur] * ADSys can prevent authentication of AD users if some policies can't be applied; * For local users, no impact will occur; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020682/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022322] Re: Gnome right butons bug
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2012388, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-appindicator (Ubuntu) ** This bug has been marked a duplicate of bug 2012388 X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2022322 Title: Gnome right butons bug Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: In the superior right corner, there are a region (about 5x5 cm2) that mouse do nothing, mainly in minimize and close butons, but ocouring to in menus, just in this corner. Double click in title bar force the restore and then, moving the software window to far of this corner, works properly. Thanks. Mr. Wagner Yaegashi 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 denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 06:13:24 2023 DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804] InstallationDate: Installed on 2022-05-01 (396 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-13 (20 days ago) dmi.bios.date: 07/14/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04REP.035.210714.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP350XAA-KD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9477A0K-C01-G001-S0001+10.0.17134 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04REP.035.210714.ZW:bd07/14/2021:br5.12:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP04REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-KD1BR:rvrSGL9477A0K-C01-G001-S0001+10.0.17134:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PREP: dmi.product.family: Notebook 3 Series dmi.product.name: 340XAA/350XAA/550XAA dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP dmi.product.version: P04REP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2022322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023008] Re: cannot install libegl-mesa0 on 22.04.2 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/2023008 Title: cannot install libegl-mesa0 on 22.04.2 LTS Status in mesa package in Ubuntu: Confirmed Bug description: # Summary `apt install libegl-mesa0` does not install it due to a dependency conflict in the apt repo. libegl-mesa0 has dependency to explicit versions of: * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2. # Expected behavior These closely linked packages to be up-to-date in the Ubuntu repo. # Workaround It is possible to install libegl-mesa0 by first downgrading the conflicting package versions: apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1 apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1 and then installing it normally: apt install libegl-mesa0 # Details ``` # apt install libegl-mesa0 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 22.2.5-0ubuntu0.1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages.` ``` 1) Is the hard dependency (=) really necessary? 2) Or should I just downgrade existing libglapi-mesa and libgbm1 installs? The difference is minor patch version only so I am hesitant to do so (there must have been a reasons for the .2 patch). # Environment ## cat /etc/lsb-release ``` cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" ``` # apt-cache policy ``` apt-cache policy libegl-mesa0 libegl-mesa0: Installed: (none) Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: 22.2.5-0ubuntu0.1~22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 22.0.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2023008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022824] Re: [amdgpu] random blue/pink frames in the desktop
** Summary changed: - random blue/pink frames in the desktop + [amdgpu] random blue/pink frames in the desktop ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Tags added: amdgpu ** Also affects: xserver-xorg-video-amdgpu (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-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2022824 Title: [amdgpu] random blue/pink frames in the desktop Status in linux-hwe-5.19 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop. every 1-2 minutes, there will be a random blue/pink frame(i'm not sure of the color because it only appears for a short time). I don't get this problem in fullscreen games running with dxvk and the random frames didn't show when I recorded my desktop with obs studio. I also got this problem in gnome(on wayland). When I have a dxvk game running or when I have 2 monitors connected, I don't get this issue. One thing to note is that when I have 2 monitors connected, my gpu will boost its vram clock to 2000mhz. what I tried: -rebooting -updating -disabling blur in kde settings -lowering my refresh rate from 144hz to 120hz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 3 00:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1043:05d7] InstallationDate: Installed on 2023-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=ca576fb0-08b4-45d8-aadd-83e9df696ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: B450M Pro4-F dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2022824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022369] Re: 200% scaling on wayland touchpad feels laggy
Thanks for the bug report. I would usually recommend trying MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to fix this but your logs seem to suggest that mode is already active. Please: 1. Try disabling these extensions in case they're having some effect: 'impatie...@gfxmonk.net', 'clipboard-indica...@dieg0js.github.io', 'espre...@coadmunkee.github.com', 'x11gestu...@joseexposito.github.io' 2. Try a USB mouse and confirm there is no such lag. 3. Report your findings to libinput at: https://gitlab.freedesktop.org/libinput/libinput/-/issues ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Summary changed: - 200% scaling on wayland touchpad feels laggy + 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th Status in libinput package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have an X1 carbon 9th gen with a 4k screen where I use 200% scaling. Unfortunately, the touchpad feels laggy and imprecise when trying to hit click targets. Switching to X11 helps as well as the flat acceleration profile in gnome tweaks. I feel like this is related to how gnome or libinput upscale mouse movement. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 16:57:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-15 (18 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/libinput/+bug/2022369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022841] Re: desktop crashed on login after sleep and clipboard extension not work
Thanks for the bug report. Please start by deleting all local extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. If the problem still occurs then please: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2022841 Title: desktop crashed on login after sleep and clipboard extension not work Status in gnome-shell package in Ubuntu: Incomplete Bug description: desktop crashed on login after sleep and clipboard extension not work 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 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 09:07:41 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-03 (547 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-10 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022864] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. Next time a "lockup" happens, please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2022864 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: Frequent lockups, not sure if it's related to NVIDIA or not. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 12:29:49 2023 DistUpgraded: Fresh install 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 RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo RocketLake-S GT1 [UHD Graphics 750] [17aa:32dd] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db] InstallationDate: Installed on 2023-06-01 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 002: ID 0c45:6366 Microdia Webcam Vitade AF Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 30EF004VUS ProcEnviron: LANG=en_US.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/ubuntu--vg-ubuntu--lv ro nomodeset text SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: M3JKT3AA dmi.board.name: 32DD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305435660291 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrM3JKT3AA:bd03/16/2023:br1.58:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny: dmi.product.family: ThinkStation P350 Tiny dmi.product.name: 30EF004VUS dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny dmi.product.version: ThinkStation P350 Tiny dmi.sys.vendor: LENOVO 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 To manage notifications about this b
[Desktop-packages] [Bug 2022885] Re: ubuntu-dock unresponsive
Sounds like https://github.com/micheleg/dash-to-dock/issues/2024 which is apparently a regression in version 82. ** Bug watch added: github.com/micheleg/dash-to-dock/issues #2024 https://github.com/micheleg/dash-to-dock/issues/2024 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/2024 Importance: Unknown Status: Unknown -- 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/2022885 Title: ubuntu-dock unresponsive Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: After starting an application from dock and closing it dock becomes unresponsive if no apps are open. I start an app from dock and then close it. click on any icon in the dock has no effect. now I can start the dash with super+a and then start an app from the dash or start the terminal with ctrl+alt+t now the dock works until an app (any app) is active. when I close all apps dock becomes unresponsive again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 82ubuntu1 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: ubuntu:GNOME Date: Mon Jun 5 08:12:29 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2022885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022954] Re: RDP and VNC fail when headless with no monitor (but work otherwise!)
** Package changed: xorg (Ubuntu) => gnome-shell (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/2022954 Title: RDP and VNC fail when headless with no monitor (but work otherwise!) Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: * Install fresh Ubuntu 22.04.2 LTS * Enable RDP and VNC via sharing control panel * Test RDP and VNC, verify working * Unplug monitor * Try RDP. Authenticate, then connection closed with no display * Try VNC. Authenticate, then connection closed with no display * Plug monitor back in * Try RDP. Works! * Try VNC. Works! * Unplug monitor * Try RDP. AUthenticate, then connection closed with no display * Try VNC. Authenticate, then connection closed with no display * GOTO 10 Symptoms are present with both wayland and X11. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 11:02:41 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [19da:b301] InstallationDate: Installed on 2023-06-01 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ZOTAC ZBOX-CI323NANO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_j45abz@/vmlinuz-5.19.0-43-generic root=ZFS=rpool/ROOT/ubuntu_j45abz ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B301P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI323NANO dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB301P027:bd09/11/2019:br5.11:svnZOTAC:pnZBOX-CI323NANO:pvrXX:rvnZOTAC:rnZBOX-CI323NANO:rvrXX:cvnDefaultstring:ct3:cvrDefaultstring:skuN/A: dmi.product.family: N/A dmi.product.name: ZBOX-CI323NANO dmi.product.sku: N/A dmi.product.version: XX dmi.sys.vendor: ZOTAC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Yeah I know, mentioned in comment #11: > * I can still reproduce the failure to revert when using the PPA version 42.5-0ubuntu1vv1 (fractional scaling support removed, so using integer scaling). What I was trying to say in comment #16 is not that fractional scaling was the cause of this bug, but that it will trigger Xdcv bugs we can't fix. So all testing of this bug should be done with fractional scaling disabled. -- 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: New 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
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Oh actually the logs you provided in comment #17 suggest that the fractional scaling patch is trying to implement the revert using fractional scaling (which will fail on Xdcv) even when the feature is disabled. So it sounds like I need to make a new PPA revision that has both the changes of vv1 and vv2 combined... -- 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: New 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- insta
[Desktop-packages] [Bug 2022889] Re: [SRU] libreoffice 7.5.4 for lunar
** Changed in: libreoffice (Ubuntu Lunar) Status: New => In Progress -- 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: In Progress 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 1265898] Re: thunderbird doesn't remember maximized window state in Ubuntu Gnome
I have de same issue in Ubuntu 23.04 and 23.10. Both gnome shell 44.0 and 44.01. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1265898 Title: thunderbird doesn't remember maximized window state in Ubuntu Gnome Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Confirmed Bug description: Not sure if this is thunderbird or gnome-shell related issue. Steps to reproduce: 1. Run thunderbird. 2. Maximize thunderbird window. 3. Close thunderbird. 4. Run thunderbird again. 5. Notice that thunderbird window is not maximized - maximized window state was not saved during closing. Expected behaviour: In 5. thudnderbird window is open in maximized state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:24.2.0+build1-0ubuntu1 Uname: Linux 3.13.0-031300rc6-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dotnokato 1431 F pulseaudio /dev/snd/pcmC0D0p: dotnokato 1431 F...m pulseaudio BuildID: 20131206222054 Channel: Unavailable CurrentDesktop: GNOME Date: Fri Jan 3 21:02:28 2014 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-15 (79 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) IpRoute: default via 10.100.10.1 dev eth0 proto static 10.100.10.0/24 dev eth0 proto kernel scope link src 10.100.10.8 metric 1 10.100.10.0/24 dev wlan0 proto kernel scope link src 10.100.10.12 metric 9 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) PrefSources: prefs.js [Profile]/extensions/gnomeintegrat...@davidmartinez.net/defaults/preferences/gnomeintegration.js Profiles: Profile0 (Default) - LastVersion=24.2.0/20131206222054 (In use) RelatedPackageVersions: rhythmbox-mozilla 3.0.1-1ubuntu8 gnome-shell 3.8.4-0ubuntu6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to trusty on 2013-11-05 (59 days ago) dmi.bios.date: 05/08/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68TT2 Ver. F.07 dmi.board.name: 30B0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.15 dmi.chassis.asset.tag: CNU7110B09 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68TT2Ver.F.07:bd05/08/2007:svnHewlett-Packard:pnHPCompaqnx6325(EY349EA#AKD):pvrF.07:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6325 (EY349EA#AKD) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1265898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022885] Re: ubuntu-dock unresponsive
** Changed in: dash-to-dock Status: Unknown => New -- 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/2022885 Title: ubuntu-dock unresponsive Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: After starting an application from dock and closing it dock becomes unresponsive if no apps are open. I start an app from dock and then close it. click on any icon in the dock has no effect. now I can start the dash with super+a and then start an app from the dash or start the terminal with ctrl+alt+t now the dock works until an app (any app) is active. when I close all apps dock becomes unresponsive again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 82ubuntu1 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: ubuntu:GNOME Date: Mon Jun 5 08:12:29 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2022885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
Is this going to happen in 23.10? It seems to have been stalled in -proposed since May. After the imminent Debian 12 release (which includes polkit 122), I intend to start removing legacy polkit 0.105 support, with my goal being polkitd-pkla no longer existing in Debian 13, and packages no longer shipping legacy polkitd-pkla configuration in /var/lib. If Ubuntu still needs this after that point, then you'll have to patch it back in where necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
** Changed in: policykit-1 (Ubuntu) Importance: Medium => High ** Changed in: policykit-1 (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => Sebastien Bacher (seb128) ** Changed in: policykit-1 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Fix Committed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023183] [NEW] network-manager autokpgtest failure (nm.py)
Public bug reported: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Lunar) Importance: Undecided Status: New -- 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/2023183 Title: network-manager autokpgtest failure (nm.py) Status in network-manager package in Ubuntu: New Status in network-manager source package in Lunar: New Bug description: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
@Simon, yes, I've been working on it in mantic. The new version is in proposed atm. I ported our Ubuntu specifics rules some days ago, https://launchpad.net/ubuntu/+source/policykit-desktop-privileges/0.22. The remaining blocker at this point is that currently duktape has no autopkgtest which is a requirement for the MIR (lp: #1997417). Upstream have tests but they are not included in the tarball. We started by looking at adding those but then hit an issue than the tests matching the current release rely on python2 which isn't available in the archive. The tests have been ported to python3 upstream so we are looking at including a newer version of those now. It doesn't help that the upstream project doesn't seem active at this point (no commit since Novembre, no reply to https://github.com/svaarala/duktape/issues/2536 asking for a new release) Anyway, those details aside I think it's fine for Ubuntu if you go ahead and start remove pkla files in Debian, thanks for letting us know! ** Bug watch added: github.com/svaarala/duktape/issues #2536 https://github.com/svaarala/duktape/issues/2536 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Fix Committed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
They are used for different platform of different OEM. The OEM platform owner tracks specific platform bugs by platform tag in the private bug and we are not able to share the platform information cross OEM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
@Dirk, are you sure you attached the right changeset? The patch is
adding autopkgtest to the package. Also such changes should be submitted
against the upstream project for review on
https://github.com/tseliot/ubuntu-drivers-common/pulls
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Incomplete
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* For this feature which only impact if the target system has a
custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510/520/525..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/custom_supported_gpus.json in the
system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for
more details.
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Upstream commit:
https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341
* build log (as file)
Please refer the attachment "buildlog"
* install log
Please refer the attachment "installlog"
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006110] Re: [SRU] Update to latest bugfix release for jammy
> [flatpak search meld] produces 3,010 spurious identical error messages That's https://github.com/ximion/appstream/issues/384, which is a libappstream bug that cannot be fixed by a Flatpak change (as much as we might like to). I contributed a fix which was included in appstream 0.15.3, so this SRU would incorporate that fix. ** Bug watch added: github.com/ximion/appstream/issues #384 https://github.com/ximion/appstream/issues/384 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to latest bugfix release for jammy Status in Flatpak: New Status in appstream package in Ubuntu: Confirmed Bug description: Appstream 0.15.6 is available since December, 2022 and comes with lots of crash fixes [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components, since the release of Jammy, a few point releases have been made to appstream that fixes crashes and optimizations. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populatedwith data [ Where problems could occur ] * GNOME Software and KDE Discover could be affected by a sudden crashes but that is unlikely. [ Other Info ] * To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982764] Re: Peek does not capture mouse cursor in Xorg + does not work under Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screenshot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1982764 Title: Peek does not capture mouse cursor in Xorg + does not work under Wayland Status in Peek: New Status in gnome-screenshot package in Ubuntu: Confirmed Status in peek package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 22.04 Jammy django@ASGARD:~$ sudo lshw -c video [sudo] Mot de passe de django : *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabricant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 nom logique: /dev/fb0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom fb configuration : depth=32 driver=i915 latency=0 resolution=1920,1080 ressources : irq:32 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d django@ASGARD:~$ using peek from repository ( 1.5.1+git20211214-1 amd64 ) I can't get it to work under Wayland session ( peek window opens but no recording at all ). Under Xorg session it almost works but does not "capture" mouse- cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/peek/+bug/1982764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982764] Re: Peek does not capture mouse cursor in Xorg + does not work under Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: peek (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1982764 Title: Peek does not capture mouse cursor in Xorg + does not work under Wayland Status in Peek: New Status in gnome-screenshot package in Ubuntu: Confirmed Status in peek package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 22.04 Jammy django@ASGARD:~$ sudo lshw -c video [sudo] Mot de passe de django : *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabricant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 nom logique: /dev/fb0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom fb configuration : depth=32 driver=i915 latency=0 resolution=1920,1080 ressources : irq:32 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d django@ASGARD:~$ using peek from repository ( 1.5.1+git20211214-1 amd64 ) I can't get it to work under Wayland session ( peek window opens but no recording at all ). Under Xorg session it almost works but does not "capture" mouse- cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/peek/+bug/1982764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722096] Re: AisleRiot card theme is not branded
Thanks for the work on those fixes and the detailed explanations and sorry for the review delay, the changes are on their way to Ubuntu now ** Changed in: branding-ubuntu (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to branding-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1722096 Title: AisleRiot card theme is not branded Status in branding-ubuntu package in Ubuntu: Fix Committed Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 branding-ubuntu: 0.8 AisleRiot uses .svgz file for card theme. bonded.svg in this package is not used. Expected branding-ubuntu should include a file bonded.svgz, and get bonded.svgz in package aisleriot diverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/branding-ubuntu/+bug/1722096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023086] Re: Gtk-4 update breaks nautilus
** Description changed: - - Before explaining the issue, let me say this: Ubuntu is becoming very - annoying. It's another patching gone wrong. Instead of releasing Gnome - 44.2 you guys patch in another bug in libgtk. And worse, it took me 2 - hours to find out what the problem is. Plus I reset Gnome desktop - because I thought doing the good old dconf reset helps. Folks at Ubuntu - - this is just very annoying! + It took me 2 hours to find out what the problem is. I reset Gnome + desktop because I thought doing the good old dconf reset helps. Folks at + Ubuntu - this kind of quality is just very annoying and unacceptable! Now to the bug. This is Ubuntu 23.04. Updates up-to-date. The latest update of libgtk-4 from version 4.10.1 to 4.10.3 breaks nautilus' move- to-trash behavior and copying is broken too. If you move a file to trash with libgtk-4.10.3 installed, the wrong icon is removed from the icon view. Just watch the attached video to see the issue. -- 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/2023086 Title: Gtk-4 update breaks nautilus Status in gtk4 package in Ubuntu: New Bug description: It took me 2 hours to find out what the problem is. I reset Gnome desktop because I thought doing the good old dconf reset helps. Folks at Ubuntu - this kind of quality is just very annoying and unacceptable! Now to the bug. This is Ubuntu 23.04. Updates up-to-date. The latest update of libgtk-4 from version 4.10.1 to 4.10.3 breaks nautilus' move-to-trash behavior and copying is broken too. If you move a file to trash with libgtk-4.10.3 installed, the wrong icon is removed from the icon view. Just watch the attached video to see the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2023086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors
I don't see a report so I presume this is OK to release? -- 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/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact --- I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. Test Case - 1. Install the update 2. Log out 3. Log back in 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. 5. Drag a window from one screen to the other. The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. Other Info -- Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020277] Re: Update gnome-shell to 44.1
This bug was fixed in the package gnome-shell - 44.1-0ubuntu1 --- gnome-shell (44.1-0ubuntu1) lunar; urgency=medium [ Jarred Wilson ] * New upstream release (LP: #2020277, LP: #1968383) * Drop patches applied in new release * Rebase patches [ Jeremy Bicha ] * Drop patch to ensure tray icons windows are shown: applied in new release * debian/control.in: Bump minimum mutter to 44.1 -- Jeremy Bícha Mon, 22 May 2023 16:33:48 -0400 ** Changed in: gnome-shell (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020277 Title: Update gnome-shell to 44.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Released Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS It is also believed to fix at least one crash issue reported as LP: #2016007 but without a clear test case, that bug is not included in this SRU verification. Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell 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.1 (LP: #2020225). This was done with bumped dependencies in debian/control. gnome-shell 44.1 could be run with mutter 44.1 but it led to build test failures. Also, mixing different versions of mutter & gnome-shell is not supported upstream. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] Re: Update mutter to 44.1
This bug was fixed in the package mutter - 44.1-0ubuntu1 --- mutter (44.1-0ubuntu1) lunar; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2020225, LP: #2012717, LP: #2013216, LP: #2015861, LP: #2017097) * debian/libmutter-12-0.symbols: Add new symbols * Drop 3 patches applied in new release [ Daniel van Vugt ] * Update triple buffering patch for Mutter 44.1 (LP: #2017137) -- Jeremy Bícha Fri, 19 May 2023 16:18:13 -0400 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020277] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2020277 Title: Update gnome-shell to 44.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Released Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS It is also believed to fix at least one crash issue reported as LP: #2016007 but without a clear test case, that bug is not included in this SRU verification. Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell 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.1 (LP: #2020225). This was done with bumped dependencies in debian/control. gnome-shell 44.1 could be run with mutter 44.1 but it led to build test failures. Also, mixing different versions of mutter & gnome-shell is not supported upstream. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] Re: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04
This bug was fixed in the package mutter - 44.1-0ubuntu1 --- mutter (44.1-0ubuntu1) lunar; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2020225, LP: #2012717, LP: #2013216, LP: #2015861, LP: #2017097) * debian/libmutter-12-0.symbols: Add new symbols * Drop 3 patches applied in new release [ Daniel van Vugt ] * Update triple buffering patch for Mutter 44.1 (LP: #2017137) -- Jeremy Bícha Fri, 19 May 2023 16:18:13 -0400 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017137 Title: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Find a machine with an Intel GPU. 2. Log into 'Ubuntu on Xorg'. 3. Press Super+A and scroll the icon right left/right. It should be perfectly smooth like in Wayland sessions. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2017137 Title: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Find a machine with an Intel GPU. 2. Log into 'Ubuntu on Xorg'. 3. Press Super+A and scroll the icon right left/right. It should be perfectly smooth like in Wayland sessions. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed
This bug was fixed in the package mutter - 44.1-0ubuntu1 --- mutter (44.1-0ubuntu1) lunar; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2020225, LP: #2012717, LP: #2013216, LP: #2015861, LP: #2017097) * debian/libmutter-12-0.symbols: Add new symbols * Drop 3 patches applied in new release [ Daniel van Vugt ] * Update triple buffering patch for Mutter 44.1 (LP: #2017137) -- Jeremy Bícha Fri, 19 May 2023 16:18:13 -0400 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 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/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 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/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors
This bug was fixed in the package mutter - 44.1-0ubuntu1 --- mutter (44.1-0ubuntu1) lunar; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2020225, LP: #2012717, LP: #2013216, LP: #2015861, LP: #2017097) * debian/libmutter-12-0.symbols: Add new symbols * Drop 3 patches applied in new release [ Daniel van Vugt ] * Update triple buffering patch for Mutter 44.1 (LP: #2017137) -- Jeremy Bícha Fri, 19 May 2023 16:18:13 -0400 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact --- I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. Test Case - 1. Install the update 2. Log out 3. Log back in 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. 5. Drag a window from one screen to the other. The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. Other Info -- Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015861] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact --- I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. Test Case - 1. Install the update 2. Log out 3. Log back in 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. 5. Drag a window from one screen to the other. The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. Other Info -- Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
This bug was fixed in the package mutter - 44.1-0ubuntu1 --- mutter (44.1-0ubuntu1) lunar; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2020225, LP: #2012717, LP: #2013216, LP: #2015861, LP: #2017097) * debian/libmutter-12-0.symbols: Add new symbols * Drop 3 patches applied in new release [ Daniel van Vugt ] * Update triple buffering patch for Mutter 44.1 (LP: #2017137) -- Jeremy Bícha Fri, 19 May 2023 16:18:13 -0400 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012717] Re: GNOME 44 multi-monitor screen freeze when resuming from sleep
This bug was fixed in the package mutter - 44.1-0ubuntu1 --- mutter (44.1-0ubuntu1) lunar; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #2020225, LP: #2012717, LP: #2013216, LP: #2015861, LP: #2017097) * debian/libmutter-12-0.symbols: Add new symbols * Drop 3 patches applied in new release [ Daniel van Vugt ] * Update triple buffering patch for Mutter 44.1 (LP: #2017137) -- Jeremy Bícha Fri, 19 May 2023 16:18:13 -0400 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012717 Title: GNOME 44 multi-monitor screen freeze when resuming from sleep Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Using multiple monitors in a Wayland session, one or both may freeze when resuming from sleep. [ Test Plan ] 1. Log into a Wayland session. 2. Set up gnome-shell to span two monitors. 3. Wait for the monitors to sleep. 4. Wiggle the mouse to wake them. 5. Move the mouse between both monitors. 6. Verify that the mouse appears on both monitors and neither are frozen. [ Where problems could occur ] This fix affects frame scheduling so problems could always occur in the form of other screen freezes and frame rate issues. [ Original report ] Testing GNOME 44 I find it can't resume from sleep properly if two monitors are plugged in. Both monitors wake up, but one is completely frozen and the other is partially frozen (stops responding to anything but cursor movement). Using Intel graphics with two USB-C monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012717] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2012717 Title: GNOME 44 multi-monitor screen freeze when resuming from sleep Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Using multiple monitors in a Wayland session, one or both may freeze when resuming from sleep. [ Test Plan ] 1. Log into a Wayland session. 2. Set up gnome-shell to span two monitors. 3. Wait for the monitors to sleep. 4. Wiggle the mouse to wake them. 5. Move the mouse between both monitors. 6. Verify that the mouse appears on both monitors and neither are frozen. [ Where problems could occur ] This fix affects frame scheduling so problems could always occur in the form of other screen freezes and frame rate issues. [ Original report ] Testing GNOME 44 I find it can't resume from sleep properly if two monitors are plugged in. Both monitors wake up, but one is completely frozen and the other is partially frozen (stops responding to anything but cursor movement). Using Intel graphics with two USB-C monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
This bug was fixed in the package gnome-shell - 44.1-0ubuntu1 --- gnome-shell (44.1-0ubuntu1) lunar; urgency=medium [ Jarred Wilson ] * New upstream release (LP: #2020277, LP: #1968383) * Drop patches applied in new release * Rebase patches [ Jeremy Bicha ] * Drop patch to ensure tray icons windows are shown: applied in new release * debian/control.in: Bump minimum mutter to 44.1 -- Jeremy Bícha Mon, 22 May 2023 16:33:48 -0400 ** Changed in: gnome-shell (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Incomplete Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Incomplete Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
> Therefore, the crash is fixed even though there is still a remaining bug. Does this bug need reopening then, or a new bug filed? I leave that up to you - setting Incomplete for now since that's better than Fix Released and this being forgotten. ** Changed in: gnome-shell (Ubuntu Lunar) Status: Fix Released => Incomplete -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Incomplete Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
The issue is fixed in mantic by https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/1.9.9-2 ubuntu-sponsors is subscribed but the change is a patch without the packaging integration or the changelog entry, could you perhaps add a debdiff for each serie instead? ** Changed in: pcsc-lite (Ubuntu) Importance: Undecided => High ** Changed in: pcsc-lite (Ubuntu) Status: Confirmed => 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: Unknown 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 2022951] Re: Update mutter to 44.2
** Changed in: mutter (Ubuntu Lunar) Status: Triaged => In 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/2022951 Title: Update mutter to 44.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.2/NEWS 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 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 2020652] Re: gnome-shell crashed with SIGSEGV in on_swap_buffer_update_result() from on_swap_buffer_update_result() from flush_callbacks() from callback_idle() from g_main_disp
We are working on getting mutter 44.2 with this update to the triple buffering patch into Ubuntu 23.04. I was unable to easily duplicate this crash in my testing so I am not mentioning this bug in the debian/changelog. We need clear test cases for bugs in Stable Release Update changelogs. -- 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/2020652 Title: gnome-shell crashed with SIGSEGV in on_swap_buffer_update_result() from on_swap_buffer_update_result() from flush_callbacks() from callback_idle() from g_main_dispatch() Status in mutter package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/25d29dc8989c98e49b3e39291a1d7299932996ab contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Changed in: mutter (Ubuntu Lunar) Status: Triaged => In 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/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: In Progress 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
** Description changed: 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. -- 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: In Progress 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 2022961] Re: Update gnome-shell to 44.2
** Changed in: gnome-shell (Ubuntu Lunar) Status: Triaged => In Progress ** Description changed: 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 - - 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. 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. -- 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: In Progress 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 1722096] Re: AisleRiot card theme is not branded
This bug was fixed in the package branding-ubuntu - 0.11 --- branding-ubuntu (0.11) mantic; urgency=medium * fix XML IDs in Aisleriot SVG card theme and compress as SVGZ (lp: #1722096) -- MestreLion Wed, 07 Jun 2023 15:03:07 +0200 ** Changed in: branding-ubuntu (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to branding-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1722096 Title: AisleRiot card theme is not branded Status in branding-ubuntu package in Ubuntu: Fix Released Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 branding-ubuntu: 0.8 AisleRiot uses .svgz file for card theme. bonded.svg in this package is not used. Expected branding-ubuntu should include a file bonded.svgz, and get bonded.svgz in package aisleriot diverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/branding-ubuntu/+bug/1722096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006110] Re: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy
This debdiff contains a minimal fix to resolve the noisy assertions (and potential crash) when searching for AppStream data. It should be suitable for upload to Jammy. @tintou, sorry for hijacking the SRU report a bit, in hindsight I should probably have filed a new one. This should address the most visible issue though without any risk of introducing new problems. (It would still be nice to have a more recent AppStream in Jammy, but we can request that later) ** Summary changed: - [SRU] Update to latest bugfix release for jammy + [SRU] Update to 0.15.2-2ubuntu0.1 for jammy ** Description changed: - Appstream 0.15.6 is available since December, 2022 and comes with lots - of crash fixes + The attached debdiff contains two targeted fixes to address noisy + warning messages when AppStream is used with newer Flatpak versions. [ Impact ] - * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and - probably lot of other components, since the release of Jammy, a few - point releases have been made to appstream that fixes crashes and - optimizations. + * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and + probably lot of other components. However, this fix has already been + well-tested for over a year. [ Test Plan ] - * Open GNOME Software and KDE Discover and see that it is still - populatedwith data + * Open GNOME Software and KDE Discover and see that it is still + populated with data. [ Where problems could occur ] - * GNOME Software and KDE Discover could be affected by a sudden crashes - but that is unlikely. + * If GNOME Software / KDE Discover still show all applications, everything should be fine, as this is the codepath this change touches. + * `apt update` should not emit any warning messages from AppStream. [ Other Info ] - - * + + * ** Patch added: "appstream_0.15.2-2_to_0.15.2-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2006110/+attachment/5678473/+files/appstream_0.15.2-2_to_0.15.2-2ubuntu0.1.debdiff ** Also affects: appstream (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy Status in Flatpak: New Status in appstream package in Ubuntu: Confirmed Status in appstream source package in Jammy: New Bug description: The attached debdiff contains two targeted fixes to address noisy warning messages when AppStream is used with newer Flatpak versions. [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components. However, this fix has already been well-tested for over a year. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populated with data. [ Where problems could occur ] * If GNOME Software / KDE Discover still show all applications, everything should be fine, as this is the codepath this change touches. * `apt update` should not emit any warning messages from AppStream. [ Other Info ] * To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] [SRU] Update to 0.7.18-2ubuntu0.1 for jammy
Public bug reported: [ 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 ] * Run "flatpak search firefox" - Observe the failure. * Update to the patched version * Run "flatpak search firefox" again, it should work now. [ 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. ** Affects: appstream-glib (Ubuntu) Importance: Undecided Status: New ** Affects: appstream-glib (Ubuntu Jammy) Importance: Undecided Status: New ** Patch added: "appstream-glib_0.7.18-2_to_0.7.18-2ubuntu0.1.debdiff" https://bugs.launchpad.net/bugs/2023215/+attachment/5678475/+files/appstream-glib_0.7.18-2_to_0.7.18-2ubuntu0.1.debdiff ** Also affects: appstream-glib (Ubuntu Jammy) Importance: Undecided Status: New -- 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] Update to 0.7.18-2ubuntu0.1 for jammy Status in appstream-glib package in Ubuntu: New Status in appstream-glib source package in Jammy: New 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 ] * Run "flatpak search firefox" - Observe the failure. * Update to the patched version * Run "flatpak search firefox" again, it should work now. [ 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. 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 2017716] Re: Folders and files frequently need to be clicked twice
@jurgen-schellaert-j I didn't mean to move cursor outside the window, I meant to move over white space inside the files view, like the white space between files/folders or beneath files/folders when they don't cover the entire view. Moving cursor outside nautilus negates the bug. -- 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/2017716 Title: Folders and files frequently need to be clicked twice Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. 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: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2017716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017716] Re: Folders and files frequently need to be clicked twice
Just to iterate here: this problem only effects X11. It's already fixed in GTK 4.8.3 and 4.10.1 for Wayland. -- 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/2017716 Title: Folders and files frequently need to be clicked twice Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. 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: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2017716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Good news ! But i stay on Ubuntu Jammy and shall use the work around i did. See first post of me. -- 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: Unknown 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 2023115] Re: ftp application support needs default configuration
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2023115 Title: ftp application support needs default configuration Status in ubuntu-meta package in Ubuntu: New Bug description: With both Chrome and Firefox having dropped ftp support, Ubuntu needs a correct default configuration to actually open ftp links. Things like gconf-editor and stuff no longer are present/work. Various "gio mime" options all return with things like: ``` λ gio mime x-scheme-handler/ftp nautilus-folder-handler.desktop gio: Failed to load info for handler “nautilus-folder-handler.desktop” λ gio mime x-scheme-handler/ftp nautilus.desktop gio: Failed to load info for handler “nautilus.desktop” λ gio mime x-scheme-handler/ftp=nautilus.desktop No default applications for “x-scheme-handler/ftp=nautilus.desktop” ``` Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2023115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2023209 Title: Windows get wrong z-index and flickering decoration halo Status in ubuntu-meta package in Ubuntu: New 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+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 2023209] Re: Windows get wrong z-index and flickering decoration halo
** Package changed: ubuntu-meta (Ubuntu) => mutter (Ubuntu) -- 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/2023209 Title: Windows get wrong z-index and flickering decoration halo Status in mutter package in Ubuntu: New 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+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 2017716] Re: Folders and files frequently need to be clicked twice
** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2017716 Title: Folders and files frequently need to be clicked twice Status in Nautilus: New Status in gtk4 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. 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: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2017716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990444] Re: firefox snap took 20 minutes to update
I tried to reproduce breaking the connection to the snap store but the issue was not reproduced. Please, in case it happens again, . run the https://github.com/snapcore/snapd/blob/master/debug-tools/snap-debug-info.sh if that happens again . provide the output of snap change ` with that update's ID ** Changed in: snapd Status: New => Incomplete ** Changed in: snapd Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1990444 Title: firefox snap took 20 minutes to update Status in snapd: Incomplete Status in firefox package in Ubuntu: Invalid Bug description: I logged and firefox was unavailable, no indication of update, nothing. When I tried to launch firefox I was invited to install it BUT I klnow it's installed, so I tried to install it but it said to me I needed to 'snap refresh', I tried to snap refresh but it indicated that everything was up to date. I tried to uninstall/reinstall the firefox snap and at this moment, I got the indication that the update was in progress since 15 MINUTES ! Then I tried to remove the snap because I was sure it's bugged : in 20.04 firefox never took more than 2 mins to update and my machine BUT after 20 minutes firefox launched... wtf ? I'm an ubuntu user since circa 2005 and I believe firefox was already the default browser then, this is the worse user experience I've ever had. 1/ I never selected auto-update, let me update when I want : being blocked 15 MINUTES by the OS is not a good user experience, I know this is accepted by Windows users but I prefer to use Ubuntu 2/ If you want to update tell me you're updating not that the application is not installed : really not a good idea if you want your users to trust you I've waited 6 months after 22.04 release to migrate from 20.04 because I don't want to have this kind of bugs, I hope you do something really quick because this is not at the level of quality expected by your users. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1990444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Hey Marc, Per your request, bug number is: #2522 -- 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 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/ubuntu/+source/gnome-control-center/+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 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2522 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2522 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2522 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in gnome-control-center: 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/gnome-control-center/+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 2006110] Re: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy
** Changed in: appstream (Ubuntu) Status: Confirmed => Fix Released ** Changed in: appstream (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to 0.15.2-2ubuntu0.1 for jammy Status in Flatpak: New Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Jammy: Triaged Bug description: The attached debdiff contains two targeted fixes to address noisy warning messages when AppStream is used with newer Flatpak versions. [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components. However, this fix has already been well-tested for over a year. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populated with data. [ Where problems could occur ] * If GNOME Software / KDE Discover still show all applications, everything should be fine, as this is the codepath this change touches. * `apt update` should not emit any warning messages from AppStream. [ Other Info ] * To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in gnome-control-center: 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/gnome-control-center/+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 2011611] Re: [FFe] Include Tiling Assistant in the default install
I'm closing this bug since we ended up not doing this for Ubuntu 23.04. We are doing it for 23.10 now but we are not in Feature Freeze. ** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2011611 Title: [FFe] Include Tiling Assistant in the default install Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Invalid Bug description: We want to add better support for tiling in the ubuntu desktop, while we're looking forward to implement it in mutter natively, at the current state the best option we have is that of using an extension. Tiling assistant is a well upstream-supported extension that is already in ubuntu universe (while MIR in progress at #2007710) and that provides more tiling features and an easier way to manage tiles. We propose to keep the tiling assistant extension disabled by default, but available for being enabled (and tuned) from gnome-control-center. In particular the extension allows to: - Do quarter-tiling of windows - Dispose tiles side-to-side and top-bottom - Select window to be tiled in empty slots - Organize tiles in windows groups that override focus behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2011611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979312] Re: Shotwell 0.32 released 2023-04-22, please update Ubuntu package
This bug was fixed in the package shotwell - 0.32.1-0ubuntu1 --- shotwell (0.32.1-0ubuntu1) mantic; urgency=medium [ Jeremy Bícha ] * New upstream release (LP: #1979312) * Drop all patches: applied in new release * debian/control: Switch to libsoup3 and webkit2gtk-4.1 * debian/control: Build-Depend on libsecret-1-dev * debian/control: Bump minimum gexiv2 and gstreamer * debian/rules: Update configure arguments [ Jörg Frings-Fürst ] * debian/control: - Change to new repository. -- Jeremy Bícha Wed, 07 Jun 2023 13:53:40 -0400 ** Changed in: shotwell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1979312 Title: Shotwell 0.32 released 2023-04-22, please update Ubuntu package Status in shotwell package in Ubuntu: Fix Released Bug description: New stable version - Shotwell 0.32 released 2023-04-22 , see https://gitlab.gnome.org/GNOME/shotwell/-/blob/master/NEWS Please update shotwell before Ubuntu 23.10 Feature freeze. Lots of important features and bugfixes, for example: * Support HiDPI for photo viewer and tools * Support HEIF/HEVC, AVIF, MXF, Webp files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1979312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019939] Re: Outdated documentation about NetworkManager keyfiles
** Changed in: debian-handbook (Ubuntu) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2019939 Title: Outdated documentation about NetworkManager keyfiles Status in debian-handbook package in Ubuntu: New Status in dhcpcanon package in Ubuntu: New Status in fai package in Ubuntu: New Status in gnome-user-docs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in scap-security-guide package in Ubuntu: New Status in wifi-qr package in Ubuntu: New Bug description: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections&literal=1&perpkg=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019939] Re: Outdated documentation about NetworkManager keyfiles
** Changed in: debian-handbook (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2019939 Title: Outdated documentation about NetworkManager keyfiles Status in debian-handbook package in Ubuntu: In Progress Status in dhcpcanon package in Ubuntu: New Status in fai package in Ubuntu: New Status in gnome-user-docs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in scap-security-guide package in Ubuntu: New Status in wifi-qr package in Ubuntu: New Bug description: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections&literal=1&perpkg=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022930] Re: When deleting a file via Nautilus, following files can not be deleted
Hi thank you, I tried but it did not work. I left a message saying: If it helps, I enabled proposed, updated but the issue is still there. Maybe I needed to wait some more for the proposed repositories to show the correct packages? -- 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/2022930 Title: When deleting a file via Nautilus, following files can not be deleted Status in nautilus package in Ubuntu: Incomplete Bug description: 1. Try to delete a file via Nautilus (Files). On the bottom right corner you will see the whole name of the file with the word selected on it. Press the Delete key on the keyboard and press enter. 2. try to delete a second file on the same folder. It will now show as "" selected instead of the actual name of the file and it will not delete anything. 3. You need to refresh nautilus for it to work once again, but it will only work once, you need to refresh every time you delete a file. An image on how it looks can be seen here: https://imgur.com/a/U5gumKp ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 07:26:13 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1402, 866)' InstallationDate: Installed on 2023-04-20 (45 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: 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 nautilus-share0.7.5-0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022851] Re: Nautilus displays invalid directory content after deleting
If it helps, I enabled proposed, updated but the issue is still there. Maybe I needed to wait some more for the proposed repositories to show the correct packages? -- 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/2022851 Title: Nautilus displays invalid directory content after deleting Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Lunar: Fix Committed Bug description: Impact -- When files are deleted in Nautilus, they can still show up but in the wrong order. This can also happen if the files are rearranged. This bug is marked Critical because it happen with gtk4 4.10.3+ds-0ubuntu1 in lunar-updates but not with 4.10.1+ds-2ubuntu1 which was originally released with Lunar. Test Case - Install the gtk4 update 1. Close the file browser windows if they are open 2. From a terminal, run these commands: mkdir delete-test cd delete-test touch a b c d e f 3. Open the Nautilus file browser window 4. Navigate to the delete-test folder 5. Select the f file and press the Delete key to delete the file. The file should be deleted and you should see only the files a b c d e in the current folder view What Could Go Wrong --- This fix is included in gtk4 4.10.4 update so see the master bug LP: #2023031 Original Bug Report --- When I delete or reorganize files, they can be displayed wrong. After going to another directory and then back, everything displays properly. 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 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 18:25:47 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)' InstallationDate: Installed on 2022-07-22 (317 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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/gtk/+bug/2022851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022997] Re: Nautilus does not update view properly when deleting or moving files unless refreshed
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2022997 Title: Nautilus does not update view properly when deleting or moving files unless refreshed Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Confirmed Bug description: This issue happens in Nautilus 44.0, both on Wayland and X11, and has also been noted in upstream Gnome as well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945 When deleting files, only the file being deleted should be shown as deleted, and when moving files/folders, the file/folder should appear as-is in the destination directory. However, this is not the case here. When deleting, the file/folder gets deleted correctly in the filesystem, but Nautilus does not update the view properly. The file being deleted still remains, instead showing another file to be deleted and when undoing delete operation via [Ctrl-Z], it shows a duplicate of the deleted file/folder. This issue persists until you refresh the view [F5], when the view shows up correctly. Also, when moving files/folders to another directory, the file/folder initially shows up as a blank 'text' file named '', until you refresh the view, when it shows up correctly. It is worth noting that this issue has apparently been fixed in Fedora and Arch for a while (see gitlab bug report linked above). Please implement the same fixes here in Ubuntu as well. System details: OS: Ubuntu Version: 23.04 GNOME Version: 44.0 Kernel: Linux 6.2.0-20-generic Package details: nautilus: Installed: 1:44.0-1ubuntu2 Candidate: 1:44.0-1ubuntu2 Version table: *** 1:44.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 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 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 08:45:58 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 549)' InstallationDate: Installed on 2023-06-03 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: 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/nautilus/+bug/2022997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Tested with fresh installed jammy on machine with Nvidia GPU. Enabled -proposed channel and install ubuntu-drivers-common 0.9.6.2~0.22.04.3. Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and related packages will be installed. Executed command "sudo ubuntu- drivers install nvidia:515-open" and Nvidia open driver 515 and related packages will be installed. -- 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 2020641] Re: Installing or removing apps through snap-store launches another gdm session
On second thoughts, patching lunar is unlikely to be useful. So long as the fix is in mantic for future releases, that's enough. ** Tags removed: verification-done-lunar ** Tags added: verification-needed-lunar ** Changed in: gdm3 (Ubuntu Lunar) Status: Fix Committed => Won't Fix ** Changed in: gdm3 (Ubuntu Lunar) Importance: High => Low ** Changed in: gdm3 (Ubuntu Kinetic) Importance: Undecided => Low -- 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/2020641 Title: Installing or removing apps through snap-store launches another gdm session Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Fix Committed Status in gdm3 source package in Kinetic: Won't Fix Status in gdm3 source package in Lunar: Won't Fix Status in gdm3 source package in Mantic: Fix Released Bug description: gdm3 version: 42.0-1ubuntu7.22.04.2 Ubuntu version: Ubuntu 22.04.2 LTS [Description] Installing or removing snap packages through NICE DCV on AWS will cause the user to be kicked out of their session. The issue happens on machines running nvidia GPUs (passed through to a VM) with the GRID driver installed as well as the normal nvidia driver. [Steps to reproduce] Simply install or remove any snap through the snap store will trigger the issue, for example: $ snap install skype also running any of the following commands will also trigger the issue: $ snap connect skype:opengl :opengl $ snap disconnect skype:opengl :opengl $ snap connect skype:camera :camera $ snap disconnect skype:camera :camera After further investigation I was able to pin down the issue to udev and could reproduce the issue by running the following command: $ sudo udevadm trigger --parent-match=/sys/devices/pci:00/:00:1e.0/drm/card0 where "/sys/devices/pci:00/:00:1e.0/drm/card0" corresponds to the nvidia GPU of my instance. A more generic way of triggering the issue would be running: $ sudo udevadm trigger [Solution] I have investigated the issue and discovered that it lies within GDM3 in the "udev_is_settled" function (daemon/gdm-local-display-factory.c). In the case where the udev is settled the line "g_clear_signal_handler (&factory->uevent_handler_id, factory->gudev_client);" at the end of the function is triggered however this is not the case when the function returns early and will lead to the user being logged out. In its current implementation there are three different return points before "g_clear_signal_handler" is executed where the udev devices would already have settled. I have written a patch that fixes this issue by making sure the function "g_clear_signal_handler" is executed in all cases for which the udev is settled. [possible regressions] Excessive clearing of the signal handler might cause a case where it is not being re-initialized the next time it is needed. [Base test plan] This test plan is to make sure the issue listed in the description section is fixed. 1. Create a new nvidia accelerated VM instance on AWS with NICE DCV and the GRID driver (or normal driver) installed. Make sure the GPU is being fully passed through to the instance (do not slice the GPU). 2. Access the instance using the NICE DCV client and login. 3. Install any snap package (E.g $ snap install skype). 4. Verify there are no new sessions being launched with the user being gdm. $ sudo loginctl Also make sure that you don't get logged out of your own session. 5. Repeat step 4 while running the following command as well: $ sudo udevadm trigger 6. If the current session stays active and no new sessions spawn while performing step 3 or 5, the test succeeded. [Extra tests] This test plan is a sanity check to make sure no regressions have been created. 1. Login to the session 2. Run a few applications (E.g: Nautilus, gedit, terminal, firefox, skype, libreoffice, mpv, vlc...) and use some on the built in features (E.g: the launcher, search...) 3. Switch sessions without terminating the current one. 4. Login as a separate user and repeat step 2 5. Go back to the first session and make sure everything behaves as expected 6. Switch to init 3: $ init 3 and go back to init 5 afterwards: $ init 5 7. If no issues were found, the test succeeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2023209 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: lunar ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/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. 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 2023209] Re: Windows get wrong z-index and flickering decoration halo
Also it sounds like you are describing bug 2013216 and bug 2020674, both of which have had fixes released in the past week. So please try updating your system: sudo apt update sudo apt full-upgrade and reboot. The packages you need to get the fixes are: libmutter-12-0 version 44.1-0ubuntu1 libgtk-4-1 version 4.10.3+ds-0ubuntu1 -- 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. 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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
Tested with fresh installed focal on machine with Nvidia GPU. Enabled -proposed channel and install ubuntu-drivers-common 1:0.9.0~0.20.04.8. Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and related packages will be installed. Executed command "sudo ubuntu- drivers install nvidia:515-open" and Nvidia open driver 515 and related packages will be installed. -- 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 2015955] Re: gnome-shell crashed with SIGSEGV in wl_resource_add_destroy_listener() from meta_wayland_keyboard_set_focus() from meta_wayland_seat_set_input_focus()
Tracking upstream in https://gitlab.gnome.org/GNOME/mutter/-/issues/2853 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2853 https://gitlab.gnome.org/GNOME/mutter/-/issues/2853 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2853 Importance: Unknown Status: Unknown -- 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/2015955 Title: gnome-shell crashed with SIGSEGV in wl_resource_add_destroy_listener() from meta_wayland_keyboard_set_focus() from meta_wayland_seat_set_input_focus() Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: GNOME Shell reliably crashes when I drag a (buggy) Wayland client from a scale-1 output to a scale-2 output. The client bug is: https://github.com/wez/wezterm/issues/2445#issuecomment-1502516313 - it will set (and commit) a buffer_scale of 2 while having a buffer with dimensions not a multiple of 2 committed in some circumstances. GNOME Shell (correctly) sends a protocol error, and disconnects the client. However, when dragging the window from a scale-1 output to a scale-2 output with the mouse, gnome-shell will kill the client with a protocol error, but then immediately crash. I've tested killing a gnome-text-editor client with SIGTERM while moving the window with the mouse, and that *doesn't* kill gnome shell, so this doesn't appear to be just a matter of a client disconnecting while their window is currently mouse-dragged. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.9+bcachefs.git20230406.7889026b-1.1-generic 6.2.9 Uname: Linux 6.2.9+bcachefs.git20230406.7889026b-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 14:17:29 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 GsettingsChanges: InstallationDate: Installed on 2021-11-02 (525 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/chris ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/home/chris/.cargo/bin/nu XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 () UpgradeStatus: Upgraded to lunar on 2022-11-17 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015955] Re: gnome-shell crashed with SIGSEGV in wl_resource_add_destroy_listener() from meta_wayland_keyboard_set_focus() from meta_wayland_seat_set_input_focus()
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015955 Title: gnome-shell crashed with SIGSEGV in wl_resource_add_destroy_listener() from meta_wayland_keyboard_set_focus() from meta_wayland_seat_set_input_focus() Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: GNOME Shell reliably crashes when I drag a (buggy) Wayland client from a scale-1 output to a scale-2 output. The client bug is: https://github.com/wez/wezterm/issues/2445#issuecomment-1502516313 - it will set (and commit) a buffer_scale of 2 while having a buffer with dimensions not a multiple of 2 committed in some circumstances. GNOME Shell (correctly) sends a protocol error, and disconnects the client. However, when dragging the window from a scale-1 output to a scale-2 output with the mouse, gnome-shell will kill the client with a protocol error, but then immediately crash. I've tested killing a gnome-text-editor client with SIGTERM while moving the window with the mouse, and that *doesn't* kill gnome shell, so this doesn't appear to be just a matter of a client disconnecting while their window is currently mouse-dragged. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.9+bcachefs.git20230406.7889026b-1.1-generic 6.2.9 Uname: Linux 6.2.9+bcachefs.git20230406.7889026b-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 14:17:29 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 GsettingsChanges: InstallationDate: Installed on 2021-11-02 (525 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/chris ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/home/chris/.cargo/bin/nu XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 () UpgradeStatus: Upgraded to lunar on 2022-11-17 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
@seb128
the patches in the debdiff file picked from
https://github.com/tseliot/ubuntu-drivers-
common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3,
https://github.com/tseliot/ubuntu-drivers-
common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115 and
https://github.com/tseliot/ubuntu-drivers-
common/commit/83528313da84b55c04daa62b5edcbf823e5c067b. The patches were
merged in the Pull Request https://github.com/tseliot/ubuntu-drivers-
common/pull/76 and related discussion was in
https://github.com/tseliot/ubuntu-drivers-common/pull/71
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Incomplete
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* For this feature which only impact if the target system has a
custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510/520/525..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/custom_supported_gpus.json in the
system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for
more details.
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Upstream commit:
https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341
* build log (as file)
Please refer the attachment "buildlog"
* install log
Please refer the attachment "installlog"
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-pri
[Desktop-packages] [Bug 2015039] Re: /usr/bin/gnome-shell:5:XPending:g_main_context_prepare:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop
If you are seeing: error_code 8 request_code 147 (unknown) minor_code 6 then it might be: https://gitlab.gnome.org/GNOME/mutter/-/issues/2857 ** This bug is no longer a duplicate of bug 2014986 gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] ** Summary changed: - /usr/bin/gnome-shell:5:XPending:g_main_context_prepare:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop + gnome-shell crashed with SIGTRAP in XPending() from g_main_context_prepare() from g_main_context_iterate() from g_main_loop_run() from meta_context_run_main_loop() ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2857 https://gitlab.gnome.org/GNOME/mutter/-/issues/2857 -- 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/2015039 Title: gnome-shell crashed with SIGTRAP in XPending() from g_main_context_prepare() from g_main_context_iterate() from g_main_loop_run() from meta_context_run_main_loop() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c6063fbb3a541487a381237ffa308e1ecb9cc16b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015027] Re: /usr/bin/gnome-shell:5:XPending:g_main_context_check:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop
If you are seeing: error_code 8 request_code 147 (unknown) minor_code 6 then it might be: https://gitlab.gnome.org/GNOME/mutter/-/issues/2857 ** This bug is no longer a duplicate of bug 2014986 gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] ** Summary changed: - /usr/bin/gnome-shell:5:XPending:g_main_context_check:g_main_context_iterate:g_main_loop_run:meta_context_run_main_loop + gnome-shell crashed with SIGTRAP in XPending() from g_main_context_check() from g_main_context_iterate() from g_main_loop_run() from meta_context_run_main_loop() ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2857 https://gitlab.gnome.org/GNOME/mutter/-/issues/2857 -- 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/2015027 Title: gnome-shell crashed with SIGTRAP in XPending() from g_main_context_check() from g_main_context_iterate() from g_main_loop_run() from meta_context_run_main_loop() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
