[Desktop-packages] [Bug 2047780] Re: BlueZ release 5.71
This bug was fixed in the package bluez - 5.71-0ubuntu3 --- bluez (5.71-0ubuntu3) noble; urgency=medium * Denylist libebook1.2-dev on i386. -- Simon Quigley Sat, 06 Jan 2024 14:25:13 -0600 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
will it ever be bacported? -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: Fix Released Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
This bug was fixed in the package gnome-software - 45.3-2ubuntu1 --- gnome-software (45.3-2ubuntu1) noble; urgency=medium * Merge with Debian. Remaining change: - Add patch to disable apt updates (Closes: #787485) (LP: #1992498) gnome-software (45.3-2) unstable; urgency=high [ Matthias Klumpp ] * Add patch to fix showing deb packages (Closes: #1058924) (LP: #2047818) gnome-software (45.3-1) unstable; urgency=medium * New upstream release * Stop using debian/control.in and dh_gnome_clean * Drop nocheck annotation from appstream Build-Depends (Closes: #1059983) -- Jeremy Bícha Sun, 07 Jan 2024 11:48:39 -0500 ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software package in Debian: Fix Released Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048697] [NEW] Saving backup server credentials
Public bug reported: If I want to run a backup, I have to enter the username and password for the target backup server over and over again. Even if I set the checkbox Remember password. System: Description:Ubuntu 22.04.3 LTS Release:22.04 deja-dup: Installiert: 42.9-1ubuntu3 Installationskandidat: 42.9-1ubuntu3 Versionstabelle: *** 42.9-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.9-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: deja-dup 42.9-1ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 22:34:52 2024 InstallationDate: Installed on 2023-06-09 (213 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2048697 Title: Saving backup server credentials Status in deja-dup package in Ubuntu: New Bug description: If I want to run a backup, I have to enter the username and password for the target backup server over and over again. Even if I set the checkbox Remember password. System: Description: Ubuntu 22.04.3 LTS Release: 22.04 deja-dup: Installiert: 42.9-1ubuntu3 Installationskandidat: 42.9-1ubuntu3 Versionstabelle: *** 42.9-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.9-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: deja-dup 42.9-1ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 22:34:52 2024 InstallationDate: Installed on 2023-06-09 (213 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2048697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048701] [NEW] Xorg freeze
Public bug reported: After updating from 23.04 to 23.10 Screen freezes on boot. Booting with 23.04 kernel 6.2.0-36 still works. After getting 6.5.11-060511 from kernel ppa it works fine. >From journal of failed X: jan 08 22:14:06 chromium kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] applying backlight present quirk jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] [ENCODER:76:DDI A/PHY A] HPD is down, disabling eDP jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] *ERROR* crtc 45: Can't calculate constants, dotclock = 0! jan 08 22:14:06 chromium kernel: [ cut here ] jan 08 22:14:06 chromium kernel: i915 :00:02.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev)) jan 08 22:14:06 chromium kernel: WARNING: CPU: 1 PID: 101 at drivers/gpu/drm/drm_vblank.c:728 drm_crtc_vblank_helper_get_vblank_timestamp_internal+> jan 08 22:14:06 chromium kernel: Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul drm_display_helper cec polyval> jan 08 22:14:06 chromium kernel: CPU: 1 PID: 101 Comm: (udev-worker) Not tainted 6.5.0-14-generic #14-Ubuntu jan 08 22:14:06 chromium kernel: Hardware name: Acer Peppy, BIOS 03/02/2017 jan 08 22:14:06 chromium kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 df 49 68 e4 48 c7 c1 48 b5 71 c0 48 89 da 48 c7 c7 50 e3 71 c0 48 89 > jan 08 22:14:06 chromium kernel: RSP: 0018:a231804c3658 EFLAGS: 00010046 jan 08 22:14:06 chromium kernel: RAX: RBX: 933d80c7be30 RCX: jan 08 22:14:06 chromium kernel: RDX: RSI: RDI: jan 08 22:14:06 chromium kernel: RBP: a231804c36c8 R08: R09: jan 08 22:14:06 chromium kernel: R10: R11: R12: jan 08 22:14:06 chromium kernel: R13: 933d8b6f04a8 R14: a231804c36ec R15: 053f jan 08 22:14:06 chromium kernel: FS: 7fed1ae408c0() GS:933df8b0() knlGS: jan 08 22:14:06 chromium kernel: CS: 0010 DS: ES: CR0: 80050033 jan 08 22:14:06 chromium kernel: CR2: 56204b159120 CR3: 00010027c004 CR4: 000706e0 jan 08 22:14:06 chromium kernel: Call Trace: jan 08 22:14:06 chromium kernel: jan 08 22:14:06 chromium kernel: ? show_regs+0x6d/0x80 jan 08 22:14:06 chromium kernel: ? __warn+0x89/0x160 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? report_bug+0x17e/0x1b0 jan 08 22:14:06 chromium kernel: ? handle_bug+0x51/0xa0 jan 08 22:14:06 chromium kernel: ? exc_invalid_op+0x18/0x80 jan 08 22:14:06 chromium kernel: ? asm_exc_invalid_op+0x1b/0x20 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? _raw_spin_lock_irqsave+0xe/0x20 jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: drm_crtc_get_last_vbltimestamp+0x56/0x90 [drm] jan 08 22:14:06 chromium kernel: drm_reset_vblank_timestamp+0x73/0x100 [drm] jan 08 22:14:06 chromium kernel: drm_crtc_vblank_on+0xa9/0x1a0 [drm] jan 08 22:14:06 chromium kernel: ? assert_vblank_disabled+0x1d/0xd0 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_vblank_on+0x34/0x90 [i915] jan 08 22:14:06 chromium kernel: intel_modeset_setup_hw_state+0x1ea/0x540 [i915] jan 08 22:14:06 chromium kernel: ? drm_modeset_lock_all_ctx+0x99/0x1d0 [drm] jan 08 22:14:06 chromium kernel: ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0xa0 [drm] jan 08 22:14:06 chromium kernel: intel_display_driver_probe_nogem+0x186/0x250 [i915] jan 08 22:14:06 chromium kernel: i915_driver_probe+0x315/0x5b0 [i915] jan 08 22:14:06 chromium kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm] jan 08 22:14:06 chromium kernel: ? acpi_dev_found+0x64/0x80 jan 08 22:14:06 chromium kernel: i915_pci_probe+0xd0/0x170 [i915] jan 08 22:14:06 chromium kernel: local_pci_probe+0x44/0xb0 jan 08 22:14:06 chromium kernel: pci_call_probe+0x55/0x190 jan 08 22:14:06 chromium kernel: pci_device_probe+0x84/0x120 jan 08 22:14:06 chromium kernel: really_probe+0x1c4/0x410 jan 08 22:14:06 chromium kernel: __driver_probe_device+0x8c/0x180 jan 08 22:14:06 chromium kernel: driver_probe_device+0x24/0xd0 jan 08 22:14:06 chromium kernel: __driver_attach+0x10b/0x210 jan 08 22:14:06 chromium kernel: ? __pfx___driver_attach+0x10/0x10 jan 08 22:14:06 chromium kernel:
[Desktop-packages] [Bug 2048703] [NEW] Many apps do not display on Wayland/Nvidia
Public bug reported: Release: 23.10 Expect to happen: Run a flatpak app and it displays on the screen What happens instead: Some flatpaks fail to display when using Wayland and Nvidia card. The icon for the app shows in the dash and I can interact with the icon (i.e. right click and quit) but the app never displays on screen. All these same apps display properly when running the log in with X11. I'm no expert but it looks related to Vulkan. Here are the errors seen in Wayland but not in X11 Easy Effects, Weather & Resources display this: libEGL warning: egl: failed to create dri2 screen MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED MESA: error: zink: could not create swapchain Plexamp fails to display with the following errors: [48:0108/155953.331435:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [96:0108/155953.441997:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [55:0108/155953.531240:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. this warning shows in both Wayland and X11 when running plexamp... Warning: vkCreateInstance: Found no drivers! Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88) at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458) at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344) at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266) at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) Flacon displays this (only warnings) but displays properly: Warning: QSocketNotifier: Can only be used with threads started with QThread Warning: Could not find color scheme "" libEGL warning: egl: failed to create dri2 screen ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Many apps do no display on Wayland/Nvidia + Many apps do not display on Wayland/Nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2048703 Title: Many apps do not display on Wayland/Nvidia Status in flatpak package in Ubuntu: New Bug description: Release: 23.10 Expect to happen: Run a flatpak app and it displays on the screen What happens instead: Some flatpaks fail to display when using Wayland and Nvidia card. The icon for the app shows in the dash and I can interact with the icon (i.e. right click and quit) but the app never displays on screen. All these same apps display properly when running the log in with X11. I'm no expert but it looks related to Vulkan. Here are the errors seen in Wayland but not in X11 Easy Effects, Weather & Resources display this: libEGL warning: egl: failed to create dri2 screen MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED MESA: error: zink: could not create swapchain Plexamp fails to display with the following errors: [48:0108/155953.331435:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [96:0108/155953.441997:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [55:0108/155953.531240:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. this warning shows in both Wayland and X11 when running plexamp... Warning: vkCreateInstance: Found no drivers! Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88) at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458) at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344) at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266) at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) Flacon displays this (only warnings) but displays properly: Warning: QSocketNotifier: Can only be used with threads started with QThread Warning: Could not find color scheme "" libEGL warning: egl: failed to create dri2 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2048703/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043177] Re: gnome-shell crashed with SIGSEGV in wl_resource_post_error_vargs from wl_resource_post_error "destroyed popup not top most popup"
I think this is the upstream bug report: https://gitlab.gnome.org/GNOME/mutter/-/issues/3106 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3106 https://gitlab.gnome.org/GNOME/mutter/-/issues/3106 -- 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/2043177 Title: gnome-shell crashed with SIGSEGV in wl_resource_post_error_vargs from wl_resource_post_error "destroyed popup not top most popup" 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 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/53aea76c746a4e6657e752b77398505921f13491 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/2043177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
Hello, I'm facing a similar issue, using mantic. In noble development I haven't come across this bug thus far. I'm using the hellenic (greek) keyboard trying to type the following capital letters in ubuntu wayland: Ρ(R), Y, Ψ(C), Ζ. In parenthesis I'm adding the corresponding english letters if applicable. Instead, I'm getting the small letters ρ, υ, ψ, ζ. The applications tested are: text editor, libreoffice, gnome-calendar, gnome-terminal, application finder, firefox. I do not face such an issue in opera browser though. In my case what is different is that these letters are not accented (only υ/Υ can take an accent ύ/Ύ, yet this is not a separate key, I just have to press : before the letter in order to take the accent. I can bypass this, by pressing shift and the letter in question. I enabled mantic proposed, yet I couldn't come across the package in question. Under xorg I didn't notice this issue. Regards! -- 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/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047696] Re: [Lenovo ThinkPad E14 Gen 2] Entire system becomes laggy for unknown reason
Everything was running fine until this evening. Nothing obvious that could have triggered it. I did not have any extensions in ~/.local/share/gnome-shell/extensions, so I disabled all of the ones found through gnome-extensions list --enabled. It reduced the CPU usage of the gnome-shell process a bit, but didn't change the overall high usage. I recorded a few seconds of CPU usage graph for the top 5 processes with high CPU load according to htop and plotted a graph using procpath (see attachment). You can see that multiple processes are affected and have insanely high CPU load. Processes are: 2447 - /usr/bin/pulseaudio 2589 - /usr/lib/xorg/Xorg 2771 - /usr/bin/gnome-shell 4641 - /snap/chromium/... 32369 - /usr/share/dbeaver-ce I killed all of them, including gnome-shell and X, but it didn't change the overall behaviour. Killing X (logging back in again after that), resulted in low CPU load across all 8 cores, but as soon as I started chromium it went up to 100% on all cores and stayed like that for at least 45 seconds. All while everything GUI related appears super laggy. My guess is, that something is faulty around X, maybe even at a lower level. ** Attachment added: "procpath plot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047696/+attachment/5737445/+files/cpu.svg -- 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/2047696 Title: [Lenovo ThinkPad E14 Gen 2] Entire system becomes laggy for unknown reason Status in gnome-shell package in Ubuntu: Incomplete Bug description: Similar to whats described in https://bugs.launchpad.net/ubuntu/+bug/2032847 the system became super laggy since yesterday. It seems like something fundamental is affected. It can happen for typing, switching between tabs in browser (chrome or firefox), VS code (switching tabs, code highlighting), opening and closing applications, opening a new tmux session. Everything takes super long. Starting chromium or vs code will result in 100% cpu usage on all 8 cores according to htop for many seconds until it settles to stay around 30 to 50% all the time. Even opening a new browser tab causes comparable CPU load. But the described behaviour also happens without running chromium or vs code. Restarting gnome shell or gdm3 doesn't help. Switching back to Wayland doesn't help, there I even get mouse freezing. In summary, it seems like something multiplies the CPU usage of a lot of different processes. I've never seen anything like that. Yesterday I thought it could be the SSD breaking, because even booting (only after restart) took very long. But fsck before booting didn't show any problems. A full shutdown made it go away yesterday, and it seemed it would only appear again when I get notifications from Slack running in chromium, so I disabled it and was able to finish the work day. Today it started out well, I switched Slack to Firefox. But then it appeared again and now a shutdown doesn't fix it anymore. I know, it sounds funny, but I'm out of ideas even to narrow the source of the problem down and I really need this machine to work for work. Since yesterday I updated a system package called gjs (manually, since it was held back in sudo apt upgrade), which seems to be related to gnome-shell, it appears with quite high CPU usage in htop. I attached the output of journalctl -b0 and memfree -h, as this was asked in the thread mentioned above. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 13:21:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-28 (640 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-06 (478 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048696] [NEW] Desktop occasionally starts in overview if hotcorner enabled
Public bug reported: With the hot corner enabled via the gnome settings multitasking menu, occasionally the desktop on login will start in the overview rather than directly on the desktop. There will be times when after login I end up on the desktop so I cant reproduce the bug consistently but it happens regularly enough going through the login process. Double checked dconf and the dock has the "disable-overview-on-startup" property set to true (default). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 21:05:23 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-06-15 (207 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-05 (64 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2048696 Title: Desktop occasionally starts in overview if hotcorner enabled Status in gnome-shell package in Ubuntu: New Bug description: With the hot corner enabled via the gnome settings multitasking menu, occasionally the desktop on login will start in the overview rather than directly on the desktop. There will be times when after login I end up on the desktop so I cant reproduce the bug consistently but it happens regularly enough going through the login process. Double checked dconf and the dock has the "disable-overview-on-startup" property set to true (default). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 21:05:23 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-06-15 (207 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-05 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2048696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752680] Re: Night light does not work after resume from suspend or unlock.
I've the same issue facing on Ubuntu 22.04.1 LTS x86_64. I have a graphic driver Intel TigerLake-LP GT2 [Iris Xe Graphics] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1752680 Title: Night light does not work after resume from suspend or unlock. Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The night light feature does not work in these cases * Computer's screen shuts off due to timeout, and then is reactivated. * Computer is brought back from suspend * Computer desktop is locked, and unlocked using the password In all these cases, the night light icon is present in the notification area, and it says "Night Light On". But the screen temperature is that of normal daylight. In all these cases, disabling and re-enabling the night light using the notification area icon reactivates the night light. Version information Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 17.10 Artful Aardvark Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio /dev/snd/controlC0: talonx 2732 F pulseaudio CurrentDesktop: GNOME-Classic:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a InstallationDate: Installed on 2016-05-05 (659 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Micro-Star International Co., Ltd. GP62 6QE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop usbcore.autosuspend=-1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J5IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-16J5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.A dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.name: GP62 6QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1752680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions
Hi, Thanks for your help in making the 1.20.0-1~ubuntu22.04.3 version in the -proposed. The verification for 1.20.0-1~ubuntu22.04.3 version is DONE with the passed result. Please check detailed verification from the attached modemmanager_1.20.0-1~ubuntu22.04.3_verified.log. Confirmed the Telit FN990 modem is initialed with modemmanager 1.20.0-1~ubuntu22.04.3 well. The real Internet function is normal too. Tks. ** Attachment added: "modemmanager_1.20.0-1~ubuntu22.04.3_verified.log" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2047008/+attachment/5737546/+files/modemmanager_1.20.0-1~ubuntu22.04.3_verified.log ** Changed in: oem-priority Status: New => Fix Committed ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043177] Re: gnome-shell crashed with SIGSEGV in wl_resource_post_error_vargs from wl_resource_post_error "destroyed popup not top most popup"
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3106 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/2043177 Title: gnome-shell crashed with SIGSEGV in wl_resource_post_error_vargs from wl_resource_post_error "destroyed popup not top most popup" Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed 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 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/53aea76c746a4e6657e752b77398505921f13491 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/mutter/+bug/2043177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
I think the relevant test case here is whether there are any crashes:
3.36.9-0ubuntu0.20.04.2 - 2878 crashes
3.36.9-0ubuntu0.20.04.3 - 0 crashes
So that's almost good enough. We probably just need someone to try
custom calendars in 20.04 like the test case mentions, in case of 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/1915929
Title:
gnome-shell-calendar-server assert failure on arm64: double free or
corruption (fasttop)
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Focal:
Fix Committed
Status in gnome-shell source package in Hirsute:
Fix Released
Bug description:
[ Impact ]
gnome-shell-calendar-server crashes (and it seems to happen more in
aarch64).
https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1
[ Test case ]
There's not a clear test case, but this is relevant:
- Configure a supported calendar in your online accounts
- GNOME shell should show your events in the calendar (under notifications
panel)
[ Regression potential ]
gnome-shell-calendar-server may leak memory.
---
M1 Mac mini
Parallels Ubuntu VM
ProblemType: CrashDistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic aarch64
ApportVersion: 2.20.11-0ubuntu58
Architecture: arm64
AssertionMessage: double free or corruption (fasttop)
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 17 04:34:36 2021
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-calendar-server
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
InstallationDate: Installed on 2021-02-17 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
ProcCmdline: /usr/libexec/gnome-shell-calendar-server
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANG=en_US.UTF-8
RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
Signal: 6SourcePackage: gnome-shell
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
malloc_printerr (str=str@entry=0x81240c08 "double free or corruption
(fasttop)") at malloc.c:5389
_int_free (av=, p=0xe9eee300, have_lock=0) at
malloc.c:4298
g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-shell-calendar-server assert failure: double free or corruption
(fasttop)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915929/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048460] Re: [noble] Odd overview animation
I think this is described in https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/3303 but confusingly that's marked as a duplicate of https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2968 ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3303 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3303 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2968 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2968 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2968 Importance: Unknown Status: Unknown -- 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/2048460 Title: [noble] Odd overview animation Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Hi all, Hi Daniel, Sorry the desktop recording is not smooth but we can see here that the direction that take these two windows is not straight, there is a sudden bend. Just my feeling maybe, but that's not "sleek". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2048460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048460] Re: [noble] Odd overview animation
Here it is. :-) ** Attachment added: "no_french_chars_for_Daniel.webm" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2048460/+attachment/5737327/+files/no_french_chars_for_Daniel.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2048460 Title: [noble] Odd overview animation Status in mutter package in Ubuntu: Incomplete Bug description: Hi all, Hi Daniel, Sorry the desktop recording is not smooth but we can see here that the direction that take these two windows is not straight, there is a sudden bend. Just my feeling maybe, but that's not "sleek". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2048460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048460] Re: Windows move in a curved path in overview animations
** Summary changed: - [noble] Odd overview animation + Windows move in a curved path in overview animations ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** 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/2048460 Title: Windows move in a curved path in overview animations Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi all, Hi Daniel, Sorry the desktop recording is not smooth but we can see here that the direction that take these two windows is not straight, there is a sudden bend. Just my feeling maybe, but that's not "sleek". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2048460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047696] Re: [Lenovo ThinkPad E14 Gen 2] Entire system becomes laggy for unknown reason
Looks like DBeaver is the main problem. Can you disable that? ** Package changed: gnome-shell (Ubuntu) => 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/2047696 Title: [Lenovo ThinkPad E14 Gen 2] Entire system becomes laggy for unknown reason Status in Ubuntu: Incomplete Bug description: Similar to whats described in https://bugs.launchpad.net/ubuntu/+bug/2032847 the system became super laggy since yesterday. It seems like something fundamental is affected. It can happen for typing, switching between tabs in browser (chrome or firefox), VS code (switching tabs, code highlighting), opening and closing applications, opening a new tmux session. Everything takes super long. Starting chromium or vs code will result in 100% cpu usage on all 8 cores according to htop for many seconds until it settles to stay around 30 to 50% all the time. Even opening a new browser tab causes comparable CPU load. But the described behaviour also happens without running chromium or vs code. Restarting gnome shell or gdm3 doesn't help. Switching back to Wayland doesn't help, there I even get mouse freezing. In summary, it seems like something multiplies the CPU usage of a lot of different processes. I've never seen anything like that. Yesterday I thought it could be the SSD breaking, because even booting (only after restart) took very long. But fsck before booting didn't show any problems. A full shutdown made it go away yesterday, and it seemed it would only appear again when I get notifications from Slack running in chromium, so I disabled it and was able to finish the work day. Today it started out well, I switched Slack to Firefox. But then it appeared again and now a shutdown doesn't fix it anymore. I know, it sounds funny, but I'm out of ideas even to narrow the source of the problem down and I really need this machine to work for work. Since yesterday I updated a system package called gjs (manually, since it was held back in sudo apt upgrade), which seems to be related to gnome-shell, it appears with quite high CPU usage in htop. I attached the output of journalctl -b0 and memfree -h, as this was asked in the thread mentioned above. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 13:21:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-28 (640 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-06 (478 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2047696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048696] Re: Desktop occasionally starts in overview if hotcorner enabled
I think starting in overview is the default upstream behaviour and we only change it in the Ubuntu Dock extension. So it would be the Ubuntu Dock failing here. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (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/2048696 Title: Desktop occasionally starts in overview if hotcorner enabled Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: With the hot corner enabled via the gnome settings multitasking menu, occasionally the desktop on login will start in the overview rather than directly on the desktop. There will be times when after login I end up on the desktop so I cant reproduce the bug consistently but it happens regularly enough going through the login process. Double checked dconf and the dock has the "disable-overview-on-startup" property set to true (default). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 21:05:23 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-06-15 (207 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-05 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2048696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
i think src:nvidia-graphics-drivers-450 is ready to go -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
** Changed in: gnome-software (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software package in Debian: Fix Released Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
This is ok now. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software package in Debian: Fix Released Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
All kernel patches available in v5.19-rc1 or newer. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: Fix Released Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in bolt source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Comment #34 , jjohansen , sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 worked for me amazingly and allowed me to start my viber 21.0.0.1 again! Thank you a lot! it started crashing after I upgraded my Linux package from 6.5.0-14.14 to 6.6.0-14.14 on Jan 05th and rebooted. I am testing Ubuntu Noble 24.04 , soon to be released. Hope this bug to be fixed at least by Viber/Chrome developers until April 2024 -- 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/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in OEM Priority Project: New Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048460] Re: Windows move in a curved path in overview animations
** Changed in: gnome-shell Status: Unknown => 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/2048460 Title: Windows move in a curved path in overview animations Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi all, Hi Daniel, Sorry the desktop recording is not smooth but we can see here that the direction that take these two windows is not straight, there is a sudden bend. Just my feeling maybe, but that's not "sleek". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2048460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
The removal of pptpd seems like something that should be release noted to me, to give enquiring users somewhere to refer to. ** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
Ok, I think that the problem is that the bug report is in "firefox" instead of "xdg-desktop-portal-gnome". I'll prepare a new bug report there with the patch from Bas van den Heuvel. Sorry for the mistake. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
Ok Thks for all the work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048569] Re: rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links
the issue that qt creator can't handle file:///full/path/to/filename.cpp:linenumber on commandline (but supposed to) is known: https://bugreports.qt.io/browse/QTCREATORBUG-30143 however qt creator handles /full/path/to/filename.cpp:linenumber on commandline that's how I made a wrapper restoring the currently unavaliable (buggy) functionality -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2048569 Title: rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links Status in gnome-terminal package in Ubuntu: New Bug description: TLDR: I want to be able to open links like file:///full/path/to/filename.cpp:linenumber with rightclick open link video explanation: https://youtu.be/PmQAx7HF7_c ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 14:05:15 2024 InstallationDate: Installed on 2022-05-05 (612 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2048569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048569] [NEW] rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links
Public bug reported: TLDR: I want to be able to open links like file:///full/path/to/filename.cpp:linenumber with rightclick open link video explanation: https://youtu.be/PmQAx7HF7_c ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 14:05:15 2024 InstallationDate: Installed on 2022-05-05 (612 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2048569 Title: rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links Status in gnome-terminal package in Ubuntu: New Bug description: TLDR: I want to be able to open links like file:///full/path/to/filename.cpp:linenumber with rightclick open link video explanation: https://youtu.be/PmQAx7HF7_c ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 14:05:15 2024 InstallationDate: Installed on 2022-05-05 (612 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2048569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network
Is there any movement on this issue? I am having the same problem if I don't remove Airprint capabilities from all my network printers. I can't do that because if I do iOS devices can't print. Does anyone have any other ideas? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups package in Ubuntu: Triaged Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1753509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016925] Re: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04
I've seen the same issue when testing Ubuntu 23.04 on a recent Zen 4 CPU with embedded GPU (not my computer so I cannot give more details). The funny thing is that Firefox is not the only application impacted: the Ubuntu installer (the new one using Flutter) also appears completely corrupted, making it impossible to install Ubuntu from a live USB. The installer is also shipped as a snap application. -- 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/2016925 Title: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 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: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045096] Re: Error in network definition: Invalid MAC address 'random'
Reducing to "Medium", as I don't think we can hit this situation through the Netplan-everywhere integration, but manual steps (wrong YAML config) must be involved in reaching this state. We're working on a fix here: https://github.com/canonical/netplan/pull/427 ** Changed in: netplan Importance: High => Medium -- 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/2045096 Title: Error in network definition: Invalid MAC address 'random' Status in netplan: Triaged Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: netplan dose not understand the 'random' key word in 'Cloned MAC address' set by networkmanager. ``` /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC address 'random', must be XX:XX:XX:XX:XX:XX or XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX macaddress: "random" ^ ``` netplan Version 0.107-5ubuntu2 network-manager Version 1.44.2-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2045096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
