[Desktop-packages] [Bug 1986845] Re: "send to" with thunderbird snap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1986845 Title: "send to" with thunderbird snap Status in thunderbird package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04 If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1986845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986845] Re: "send to" with thunderbird snap
** Changed in: thunderbird (Ubuntu) Importance: Undecided => Low -- 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/1986845 Title: "send to" with thunderbird snap Status in thunderbird package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04 If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1986845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986845] Re: "send to" with thunderbird snap
Ah yes, confirmed. It only happens with the thunderbird snap, not the default thunderbird deb. Confirmed in 22.04 and 22.10. ** Package changed: gnome-shell-extension-desktop-icons-ng (Ubuntu) => thunderbird (Ubuntu) ** Changed in: thunderbird (Ubuntu) Status: Incomplete => New ** No longer affects: nautilus (Ubuntu) ** Tags added: jammy kinetic -- 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/1986845 Title: "send to" with thunderbird snap Status in thunderbird package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04 If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1986845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
** Description changed: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] - 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) + 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode - 4. There should be 5G related option + 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. + + [Other info] + This patch is from upstream gnome-control-center. For more information + refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 -- 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/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center source package in Jammy: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. [Other info] This patch is from upstream gnome-control-center. For more information refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.4
This bug was fixed in the package mutter - 42.4-2ubuntu1 --- mutter (42.4-2ubuntu1) kinetic; urgency=medium * Merge from Debian unstable (LP: #1985856). Remaining changes: - Add triple-buffering patch - Add x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr - Add ubuntu/wayland-data-device-Allow-any-drag-timestamppatch + Allow any drag timestamp as drag start serial - Add backends-native-kms-crtc-Don-t-compare-gamma-values-on-un.patch + Avoid memory errors when comparing gamma values - Add monitor-manager-Ensure-monitors-settings-after-backend-ha.patch + Ensure privacy screen settings are applied on startup - Add patches from GNOME !2364 + Fix X11 selection related crash when Xwayland died - debian/libmutter-10-0.symbols: Add symbols for triple buffering patch mutter (42.4-2) unstable; urgency=medium * Team upload * d/control.in, d/gbp.conf: Set up branches for an unstable upload * d/p/tests-Give-mutter-test-runner-the-RUNPATH-to-find-Clutter.patch: Add patch to fix missing RUNPATH in tests, fixing an autopkgtest regression in 42.4. - Note that this does not resolve a different autopkgtest regression in 42.4, in environments where /dev/dri/card0 exists but is inaccessible. However, the /dev/dri/card0 issue is not fatal for Debian's production infrastructure, which uses autopkgtest-virt-lxc and therefore does not provide /dev/dri/card0 at all. -- Jeremy Bicha Wed, 17 Aug 2022 14:39:04 -0400 ** Changed in: mutter (Ubuntu) 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/1985856 Title: Update Mutter to 42.4 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.4/NEWS It's hoped that this update will be included in Ubuntu 22.04.1 LTS. Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg 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/1985856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986845] Re: "send to" with thunderbird snap
Ubuntu 22.04 ** Description changed: + + On Ubuntu 22.04 + If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) -- 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/1986845 Title: "send to" with thunderbird snap Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Incomplete Bug description: On Ubuntu 22.04 If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1986845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.4
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- 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/1985856 Title: Update Mutter to 42.4 Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.4/NEWS It's hoped that this update will be included in Ubuntu 22.04.1 LTS. Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg 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/1985856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986889] [NEW] Icons are blurry in nautilus 43 at display scale >= 200%
Public bug reported: Icons are blurry in nautilus 43 at display scale >= 200%. Screenshot attached (compare the icons to their text). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 18 10:58:35 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2022-07-20 (28 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.1-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Medium Status: Triaged ** Tags: amd64 apport-bug kinetic visual-quality ** Attachment added: "Screenshot from 2022-08-18 10-57-16.png" https://bugs.launchpad.net/bugs/1986889/+attachment/5609464/+files/Screenshot%20from%202022-08-18%2010-57-16.png ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #530 https://gitlab.gnome.org/GNOME/nautilus/-/issues/530 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/530 Importance: Unknown Status: Unknown ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged -- 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/1986889 Title: Icons are blurry in nautilus 43 at display scale >= 200% Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Icons are blurry in nautilus 43 at display scale >= 200%. Screenshot attached (compare the icons to their text). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Aug 18 10:58:35 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2022-07-20 (28 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.1-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1986889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986845] Re: "send to" with thunderbird snap
Using Ubuntu 22.10 I find the opposite is true: It works from the desktop but fails from Files (right click and then Email..) What version of Ubuntu are you using? ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Incomplete ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: New => 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/1986845 Title: "send to" with thunderbird snap Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Incomplete Bug description: If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1986845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification
I'm guessing because hardly anyone ever sees this bug anymore. I haven't seen it myself for a long time. If it is still bothering you then the best place to discuss it is with the GNOME developers directly in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/358 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #358 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/358 -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Can you attach a photo or video of the issue? -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB
This bug has been open for 10 years now and I don't think it's reasonable to ask that legacy apps be redesigned, if those apps even have developers anymore. They may well use "legacy" Xlib but also XCB is "legacy" now too. Please focus on Wayland for new projects. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to modern XCB Status in 9wm package in Ubuntu: New Status in aewm package in Ubuntu: New Status in aewm++ package in Ubuntu: New Status in afterstep package in Ubuntu: New Status in amiwm package in Ubuntu: Invalid Status in blackbox package in Ubuntu: New Status in cairo package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in ctwm package in Ubuntu: New Status in dwm package in Ubuntu: Opinion Status in enlightenment package in Ubuntu: New Status in fvwm package in Ubuntu: New Status in fvwm1 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in icewm package in Ubuntu: New Status in jwm package in Ubuntu: Invalid Status in larswm package in Ubuntu: New Status in lwm package in Ubuntu: New Status in matchbox-window-manager package in Ubuntu: New Status in metacity package in Ubuntu: Invalid Status in miwm package in Ubuntu: New Status in muffin package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in pekwm package in Ubuntu: New Status in ratpoison package in Ubuntu: New Status in sapphire package in Ubuntu: New Status in sawfish package in Ubuntu: New Status in spectrwm package in Ubuntu: Fix Released Status in tinywm package in Ubuntu: New Status in tritium package in Ubuntu: New Status in twm package in Ubuntu: New Status in vtwm package in Ubuntu: New Status in w9wm package in Ubuntu: New Status in windowlab package in Ubuntu: New Status in wm2 package in Ubuntu: New Status in wmaker package in Ubuntu: Opinion Status in xmonad package in Ubuntu: New Bug description: Port/rewrite the window manager to use the modern XCB (X C Binding) library instead of the old legacy Xlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/9wm/+bug/1030022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984327] Re: Component mismatch: new lerc support requires universe package
Andreas, can you revert this change now? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1984327 Title: Component mismatch: new lerc support requires universe package Status in tiff package in Ubuntu: Fix Released Bug description: tiff is in sync with debian, and version tiff 4.4.0-1[1] enabled lerc support. Unfortunately lerc[2] is in ubuntu universe, and tiff is in main, so we either MIR lerc, or disable it in tiff. For now, let's disable lerc support. 1. https://launchpad.net/ubuntu/+source/tiff/4.4.0-1 2. https://launchpad.net/ubuntu/+source/lerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1984327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
My T460P (nvida + intel GPU): snap X11 works. video decoder with
hardware acceleration.
ubuntu frame with WayLand test: proper display.
Only problem is no video hardware decode. (I think it is not the snap
problem, the native version is also not support.)
It is nearly a perfect build.
Hope the wayland hardware acceleration will work in near future.
Lee
On Thu, Aug 18, 2022 at 1:44 AM Nathan Teodosio <1816...@bugs.launchpad.net>
wrote:
> The snap in the hwacc channel has been updated. Now it automatically
> detects Wayland or Xorg and sets flags accordingly.
>
> ** Description changed:
>
> To test the snap with VA-API changes,
>
> 1. Install the Chromium snap,
>
> sudo snap install --channel candidate/hwacc chromium
>
> - 2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
> + 2. Start Chromium,
>
> -snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
> - --enable-features=VaapiVideoDecoder
> -
> -If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
> -
> - chromium --enable-features=VaapiVideoDecoder --disable-
> - features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
> +snap run chromium
>
> 3. Open a video, e.g. one from https://github.com/chthomos/video-media-
> samples
>
> - 4. Enter about:media-internals in the address bar and note what the page
> - says for kVideoDecoderName.
> + 4. Enter about:media-internals in the address bar, click the
> + corresponding box (if the video is playing, it will have the "(kPlay)"
> + identifier) and note what the page says for kVideoDecoderName.
>
> Please report
>
> - - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
> - - If failed, the video used for testing, including codec and
> resolution if possible;
> + - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is
> {FFMpeg,Vpx,Dav1d}VideoDecoder;
> - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
> - Distro version (`grep VERSION= /etc/os_release`);
> - GPU (`lscpu`);
> - CPU generation (`lscpu`).
>
> About the last point, it may be that unfortunately only those with newer
> generations of Intel CPUs will have luck with this, but it's still an
> uncertainty. So reports are highly welcome.
>
> --Original Bug report -
>
> Libva is no longer working for snap installed chromium 72.0.3626.109
> (Official Build) snap (64-bit)
>
> I followed this instruction
> sudo snap install --channel=candidate/vaapi chromium
>
> My amdgpu can use libva
>
> `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
> 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
> vainfo: Supported profile and entrypoints
> VAProfileMPEG2Simple: VAEntrypointVLD
> VAProfileMPEG2Main : VAEntrypointVLD
> VAProfileVC1Simple : VAEntrypointVLD
> VAProfileVC1Main: VAEntrypointVLD
> VAProfileVC1Advanced: VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
> VAProfileH264Main : VAEntrypointVLD
> VAProfileH264Main : VAEntrypointEncSlice
> VAProfileH264High : VAEntrypointVLD
> VAProfileH264High : VAEntrypointEncSlice
> VAProfileHEVCMain : VAEntrypointVLD
> VAProfileHEVCMain10 : VAEntrypointVLD
> VAProfileJPEGBaseline : VAEntrypointVLD
> VAProfileNone : VAEntrypointVideoProc`
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1816497
>
> Title:
> [snap] vaapi chromium no video hardware decoding
>
> Status in chromium-browser package in Ubuntu:
> In Progress
>
> Bug description:
> To test the snap with VA-API changes,
>
> 1. Install the Chromium snap,
>
> sudo snap install --channel candidate/hwacc chromium
>
> 2. Start Chromium,
>
> snap run chromium
>
> 3. Open a video, e.g. one from https://github.com/chthomos/video-
> media-samples
>
> 4. Enter about:media-internals in the address bar, click the
> corresponding box (if the video is playing, it will have the "(kPlay)"
> identifier) and note what the page says for kVideoDecoderName.
>
> Please report
>
> - The value for kVideoDecoderName from step 4. Success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is
> {FFMpeg,Vpx,Dav1d}VideoDecoder;
> - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
> - Distro version (`grep VERSION= /etc/os_release`);
> - GPU (`lscpu`);
> - CPU generation (`lscpu`).
>
> About the last point, it may be that unfortunately only those with
>
[Desktop-packages] [Bug 1986861] [NEW] pulseaudio stops accepting connections
Public bug reported: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1986861 Title: pulseaudio stops accepting connections Status in pulseaudio package in Ubuntu: New Bug description: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1986861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986841] Re: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1986841 Title: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command Status in cups package in Ubuntu: New Bug description: canon pixma g2010 printer connected through usb, added in printer settings when i searched for it but when i give print command to print a page it sends command and still no print out and also there is no pending jobs showing, and when i tried to print test page it is also not printing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-oem-5.17/linux-modules-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 21:37:30 2022 InstallationDate: Installed on 2022-07-11 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for G2010: usb://Canon/G2010%20series?serial=20B026=1 MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511/RV711/E3411 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/G2010.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/G2010.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2011 dmi.bios.release: 4.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04PA.M006.20110615.XW dmi.board.asset.tag: Tag 12345 dmi.board.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04PA.M006.20110615.XW:bd06/15/2011:br4.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511/RV711/E3411:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511/RV711/E3411:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:sku: dmi.product.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971473] Re: Untranslated desktop file
Quentin: Actually there is not much to see. The language packs are fine,
and the purpose of the upload was to make sure that they keep being so.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1971473
Title:
Untranslated desktop file
Status in system-config-printer package in Ubuntu:
Fix Released
Status in system-config-printer source package in Jammy:
Fix Committed
Bug description:
[Impact]
While the Ubuntu changes include translatable strings, the .pot file
does not get refreshed when building, but upstream's .pot already in
the po/ directory gets imported to LP. As a result, some strings such
as "Printers" in the .desktop file show up untranslated.
There is a temorary workaround in place, but this proposal makes sure
that the fix won't be overwritten by the upstream .pot in case of some
additional package upload to jammy-proposed/jammy-updates.
[Test Plan]
It may be advisable to install system-config-printer{,-common} from
jammy-proposed and confirm that the updated packages work as usual.
But this is all about language packs in future point releases, and to
confirm the intention with this upload, please take these steps:
* Check out the translation import queue:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+imports
and confirm that the new po/system-config-printer.pot file was imported
successfully.
* Visit this page:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+pots/system-config-printer/oc/569
and confirm that it still leads to the "Printers" page with an Occitan
translation.
[Where problems could occur]
The buildlogs include some warnings related to the creation of the
.pot file. But we don't really know if upstream does it better, and I
have not identified any significant resulting issue.
[Original description]
Hello,
I am using Ubuntu MATE and on its control centre the entry "Printers" is not
translated whereas 100% translated.
It comes from the desktop file apparently. It happens to me in Occitan,
Catalan and French, didn't try more locales.
I opened an issue here:
https://github.com/mate-desktop/mate-control-center/issues/693#issuecomment-1115713053
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1971473/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986841] [NEW] canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command
You have been subscribed to a public bug: canon pixma g2010 printer connected through usb, added in printer settings when i searched for it but when i give print command to print a page it sends command and still no print out and also there is no pending jobs showing, and when i tried to print test page it is also not printing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-oem-5.17/linux-modules-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 21:37:30 2022 InstallationDate: Installed on 2022-07-11 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for G2010: usb://Canon/G2010%20series?serial=20B026=1 MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511/RV711/E3411 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/G2010.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/G2010.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2011 dmi.bios.release: 4.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04PA.M006.20110615.XW dmi.board.asset.tag: Tag 12345 dmi.board.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04PA.M006.20110615.XW:bd06/15/2011:br4.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511/RV711/E3411:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511/RV711/E3411:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:sku: dmi.product.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command https://bugs.launchpad.net/bugs/1986841 You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952107] Re: Google Contacts API Deprecated
I added a Bionic task. This is blocked because we haven't been able to find a working patch to fix this issue. You can see one attempt in the comment history of this bug. I added some notes from my attempt at https://salsa.debian.org/gnome-team/evolution/-/merge_requests/3 ** Also affects: evolution (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: evolution-data-server (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu Bionic) Status: New => Triaged ** Changed in: evolution (Ubuntu Bionic) Status: New => Triaged ** Changed in: evolution (Ubuntu Focal) Assignee: Jeremy Bicha (jbicha) => (unassigned) ** Changed in: evolution-data-server (Ubuntu Focal) Assignee: Jeremy Bicha (jbicha) => (unassigned) -- 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/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Bionic: Triaged Status in evolution-data-server source package in Bionic: Triaged Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971473] Re: Untranslated desktop file
Hello!
I am away and I can only have my PC with Jammy Friday, I will see this by then
:D
Many thanks again!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1971473
Title:
Untranslated desktop file
Status in system-config-printer package in Ubuntu:
Fix Released
Status in system-config-printer source package in Jammy:
Fix Committed
Bug description:
[Impact]
While the Ubuntu changes include translatable strings, the .pot file
does not get refreshed when building, but upstream's .pot already in
the po/ directory gets imported to LP. As a result, some strings such
as "Printers" in the .desktop file show up untranslated.
There is a temorary workaround in place, but this proposal makes sure
that the fix won't be overwritten by the upstream .pot in case of some
additional package upload to jammy-proposed/jammy-updates.
[Test Plan]
It may be advisable to install system-config-printer{,-common} from
jammy-proposed and confirm that the updated packages work as usual.
But this is all about language packs in future point releases, and to
confirm the intention with this upload, please take these steps:
* Check out the translation import queue:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+imports
and confirm that the new po/system-config-printer.pot file was imported
successfully.
* Visit this page:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+pots/system-config-printer/oc/569
and confirm that it still leads to the "Printers" page with an Occitan
translation.
[Where problems could occur]
The buildlogs include some warnings related to the creation of the
.pot file. But we don't really know if upstream does it better, and I
have not identified any significant resulting issue.
[Original description]
Hello,
I am using Ubuntu MATE and on its control centre the entry "Printers" is not
translated whereas 100% translated.
It comes from the desktop file apparently. It happens to me in Occitan,
Catalan and French, didn't try more locales.
I opened an issue here:
https://github.com/mate-desktop/mate-control-center/issues/693#issuecomment-1115713053
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1971473/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980408] Autopkgtest regression report (glib2.0/2.72.3-0ubuntu1)
All autopkgtests for the newly accepted glib2.0 (2.72.3-0ubuntu1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: systemd/249.11-0ubuntu3.4 (armhf) flatpak/1.12.7-1 (arm64) libaperture-0/0.1.0+git20200908-3 (armhf) automake-1.16/1:1.16.5-1.3 (arm64) booth/1.0-237-gdd88847-4ubuntu2.2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986452] Re: Sound: ubuntu loses track of the selected output sink
Brian Murray has set the package, so I'm not going to touch a thing here (my thanks for the package selection). -- 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/1986452 Title: Sound: ubuntu loses track of the selected output sink Status in gnome-control-center package in Ubuntu: New Bug description: Whenever I'm on Ubuntu the audio loses track of the selected output device (Line Out - Built-in Audio), and does not save the selected output when restarting (and perhaps re-logging, I have not tried this). Having several output options to choose from the system apparently chooses the first detected device (in my case, HyperX Cloud Flight S, an USB device). HyperX Cloud Flight S is appropriately selected as the input device. This was present in 20.04 LTS, as well, but not in 18.04 LTS. Workaround: open the Sound Settings, select the correct output device and keep the Settings window with the Sound settings selected minimized on the Favorites. If you select some other settings or close the Settings Ubuntu will lose track of the output device in a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971473] Re: Untranslated desktop file
@Chris: I think you understood it perfectly well. The block-proposed-
jammy tag sounds fine to me.
To prepare for a possible migration to -updates later, I followed the
steps in the test plan and verified the upload.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1971473
Title:
Untranslated desktop file
Status in system-config-printer package in Ubuntu:
Fix Released
Status in system-config-printer source package in Jammy:
Fix Committed
Bug description:
[Impact]
While the Ubuntu changes include translatable strings, the .pot file
does not get refreshed when building, but upstream's .pot already in
the po/ directory gets imported to LP. As a result, some strings such
as "Printers" in the .desktop file show up untranslated.
There is a temorary workaround in place, but this proposal makes sure
that the fix won't be overwritten by the upstream .pot in case of some
additional package upload to jammy-proposed/jammy-updates.
[Test Plan]
It may be advisable to install system-config-printer{,-common} from
jammy-proposed and confirm that the updated packages work as usual.
But this is all about language packs in future point releases, and to
confirm the intention with this upload, please take these steps:
* Check out the translation import queue:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+imports
and confirm that the new po/system-config-printer.pot file was imported
successfully.
* Visit this page:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+pots/system-config-printer/oc/569
and confirm that it still leads to the "Printers" page with an Occitan
translation.
[Where problems could occur]
The buildlogs include some warnings related to the creation of the
.pot file. But we don't really know if upstream does it better, and I
have not identified any significant resulting issue.
[Original description]
Hello,
I am using Ubuntu MATE and on its control centre the entry "Printers" is not
translated whereas 100% translated.
It comes from the desktop file apparently. It happens to me in Occitan,
Catalan and French, didn't try more locales.
I opened an issue here:
https://github.com/mate-desktop/mate-control-center/issues/693#issuecomment-1115713053
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1971473/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
That could very well be the case. It does not appear when the desktop is initially loaded, but shortly after a refresh(?). If I keep the second monitor (TV) active, the scaling workaround does not work - the lines on both monitors come back when set back to 100% scale. If I click the desktop the line disappears from the monitor that was clicked - and comes back once the desktop is no longer focused. An annoying little thing that I'm sure is equally annoying to figure out. -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952107] Re: Google Contacts API Deprecated
Brian, Sebastien, do either of you have the ability to mark this as a bug in Bionic as well for tracking purposes? (I don't seem to have permission to do that). It would be excellent for your patches to be backported to Bionic, regardless of _who_ submits such a patch. Thank you very much in advance! -- 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/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)
libnettle8 3.8.1-2 finally landed in kinetic, hence updating the status to Fix Released and closing this ticket. ** Changed in: nettle (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1959469 Title: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto) Status in Ubuntu on IBM z Systems: Fix Released Status in nettle package in Ubuntu: Fix Released Status in nettle package in Debian: New Bug description: Upgrade nettle to latest version >= 3.7.4 (crypto) Description Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for Crypto Libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
The snap in the hwacc channel has been updated. Now it automatically
detects Wayland or Xorg and sets flags accordingly.
** Description changed:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
- 2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
+ 2. Start Chromium,
-snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
- --enable-features=VaapiVideoDecoder
-
-If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
-
- chromium --enable-features=VaapiVideoDecoder --disable-
- features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
+snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-media-
samples
- 4. Enter about:media-internals in the address bar and note what the page
- says for kVideoDecoderName.
+ 4. Enter about:media-internals in the address bar, click the
+ corresponding box (if the video is playing, it will have the "(kPlay)"
+ identifier) and note what the page says for kVideoDecoderName.
Please report
- - The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- - If failed, the video used for testing, including codec and resolution if
possible;
+ - The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with newer
generations of Intel CPUs will have luck with this, but it's still an
uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
[Desktop-packages] [Bug 1986845] [NEW] "send to" with thunderbird snap
Public bug reported: If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1986845 Title: "send to" with thunderbird snap Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: If thunderbird snap is the default emailer: Right click on a file on the desktop, "send to" opens thunderbird for a new mail but without the attachment Doing the same from files opens the mail to be sent with the attachment (the file on the desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1986845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification
Why haven't you still fixed it?!?! The most stupid feature of gnome after no way to set alt+shift for switching input languages *poo* -- 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/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Hallo, I can confirm this is a problem also for us, with the latest firefox and chromium from snap store, including the limited applicability of the workaround regarding ccache_name location thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Triaged Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB
** No longer affects: compiz ** Changed in: compiz (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to modern XCB Status in 9wm package in Ubuntu: New Status in aewm package in Ubuntu: New Status in aewm++ package in Ubuntu: New Status in afterstep package in Ubuntu: New Status in amiwm package in Ubuntu: Invalid Status in blackbox package in Ubuntu: New Status in cairo package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in ctwm package in Ubuntu: New Status in dwm package in Ubuntu: Opinion Status in enlightenment package in Ubuntu: New Status in fvwm package in Ubuntu: New Status in fvwm1 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in icewm package in Ubuntu: New Status in jwm package in Ubuntu: Invalid Status in larswm package in Ubuntu: New Status in lwm package in Ubuntu: New Status in matchbox-window-manager package in Ubuntu: New Status in metacity package in Ubuntu: Invalid Status in miwm package in Ubuntu: New Status in muffin package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in pekwm package in Ubuntu: New Status in ratpoison package in Ubuntu: New Status in sapphire package in Ubuntu: New Status in sawfish package in Ubuntu: New Status in spectrwm package in Ubuntu: Fix Released Status in tinywm package in Ubuntu: New Status in tritium package in Ubuntu: New Status in twm package in Ubuntu: New Status in vtwm package in Ubuntu: New Status in w9wm package in Ubuntu: New Status in windowlab package in Ubuntu: New Status in wm2 package in Ubuntu: New Status in wmaker package in Ubuntu: Opinion Status in xmonad package in Ubuntu: New Bug description: Port/rewrite the window manager to use the modern XCB (X C Binding) library instead of the old legacy Xlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/9wm/+bug/1030022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
** Changed in: compiz (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in human-theme: New Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/human-theme/+bug/1721955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Hi, I installed the chromium snap and it's not able to open the locally installed winehq.org compatible Roblox! This is a super huge deal IMHO because having Roblox on Linux is very awesome for the Pipeline of Linux users(the Children) who love to play that game! Roblox.com (the great creative game for the Children) games only work from the browser-based "Play" button for each game so since xdg-mime / xdg-open for roblox-player cannot be called from the snap based chromium, it breaks roblox. Roblox.com can be installed on Ubuntu / Linux in winehq.org or to make it easier - with Grapejuice https://brinkervii.gitlab.io/grapejuice/docs/ or even Malik's wrapper at https://github.com/msmalik681/Maliks-Linux-Roblox-Wrapper Some people are saying to install chromium "from the repo" but that apparently is not an option any more in Ubuntu - it has to come from snap. Does anyone have a good workaround to setup the whitelist to allow these to work with snap chromium? # add my roblox launcher to xdg list. xdg-mime default "roblox-malik.desktop" x-scheme-handler/roblox-player # add my roblox studio launcher to xdg list. xdg-mime default "roblox-studio-malik.desktop" x-scheme-handler/roblox-studio xdg-mime default "roblox-studio-malik.desktop" application/x-roblox-rbxl xdg-mime default "roblox-studio-malik.desktop" application/x-roblox-rbxlx Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985128] Re: GDM fails to activate the login session in AWS Workspaces
Hello Marco, or anyone else affected, Accepted gnome-shell into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1985128 Title: GDM fails to activate the login session in AWS Workspaces Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: [Impact] This is the main error: Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > _promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985304] Please test proposed package
Hello Marco, or anyone else affected, Accepted gnome-shell into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/42.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1985304 Title: Update GNOME Shell to 42.4 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.4/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.2 Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. Verify that the basic functionality of each extension works as expected. 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/1985304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985304] Re: Update GNOME Shell to 42.4
> Verify that they can all be enabled without showing an error. IIRC the original request was to ensure that the extensions actually work (ie. a basic smoke test), not just that they can be enabled without error. I'll adjust your Test Plan accordingly. Really the Test Plan should be approved once by the SRU team and then documented on the wiki, so that we don't bikeshed each invididual one every SRU. I suggested this in https://discourse.ubuntu.com/t/scope-of- gnome-mru/18041/48 but there doesn't seem to be any progress on this. So sorry to be bikeshedding this here, but until those remaining steps are done, that's how it is. ** Description changed: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.4/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.2 Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. + Verify that the basic functionality of each extension works as expected. 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 ** Changed in: gnome-shell (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1985304 Title: Update GNOME Shell to 42.4 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.4/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.2 Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. Verify that the basic functionality of each extension works as expected. 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/1985304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
impish is EOL so removed. If I load libreoffice on my primary kinetic box; and seek help, it switches to firefox (snap) but on firefox I get only --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.4. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- snapd: Installed: 2.57.1+22.10 ** Tags removed: impish ** Tags added: kinetic -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833161] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Hi, I had the same problem. Comment #5 worked for me (after reboot): 1. Open terminal 2. sudo nano /etc/modprobe.d/alsa-base.conf 3. Add mentioned line in comment at the bottom of the conf file: options snd-hda-intel model=clevo-p950 4. CTRL+O -> CTRL+C 5. sudo reboot 6. test your sound My relevant specs: OS: Ubuntu 22.04LTS Soundcard: HDA Intel PCH Chip: Realtek ALC1220 Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1833161 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jproberge 1737 F pulseaudio /dev/snd/controlC0: jproberge 1737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:37:29 2019 InstallationDate: Installed on 2019-06-15 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1236 F pulseaudio jproberge 1737 F pulseaudio /dev/snd/controlC0: gdm1236 F pulseaudio jproberge 1737 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08P dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08P:bd05/07/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985128] Re: GDM fails to activate the login session in AWS Workspaces
** Description changed: - s We may get this error: - Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > _promisify/proto[asyncFunc]/ + _promisify/proto[asyncFunc]/https://bugs.launchpad.net/bugs/1985128 Title: GDM fails to activate the login session in AWS Workspaces Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: [Impact] This is the main error: Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > _promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985128] Re: [SRU] Update gnome-shell to 42.4 in 22.04
** Description changed: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] + There have been fixes in various places: a11y features and ibus, OSK, various UI fixes, login and SSO, extension loading and updates, stylesheets, ** Description changed: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse - [ Regression potential ] + [ What could go wrong ] There have been fixes in various places: a11y features and ibus, OSK, various UI fixes, login and SSO, extension loading and updates, stylesheets, ** Description changed: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS - [ Test case ] + [Test case] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse - [ What could go wrong ] + [Where problems could occur] There have been fixes in various places: a11y features and ibus, OSK, various UI fixes, login and SSO, extension loading and updates, stylesheets, ** Description changed: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [Test case] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [Where problems could occur] - There have been fixes in various places: a11y features and ibus, OSK, various UI fixes, login and SSO, extension loading and updates, stylesheets, + There have been fixes in various places: a11y features and ibus, OSK, various UI fixes, login and SSO, extension loading and updates, stylesheets. ** Description changed: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [Test case] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [Where problems could occur] - There have been fixes in various places: a11y features and ibus, OSK, various UI fixes, login and SSO, extension loading and updates, stylesheets. + There have been fixes in various places: a11y features and ibus, OSK, various UI fixes, login with realmd and SSO, extension loading and updates, stylesheets. ** Summary changed: - [SRU] Update gnome-shell to 42.4 in 22.04 + GDM fails to activate the login session in AWS Workspaces ** Description changed: - [Impact] - - This is the current GNOME 42.4 stable update, including some fixes and - translation updates. - - https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS - - [Test case] - - The update is part of GNOME stable updates - https://wiki.ubuntu.com/StableReleaseUpdates/GNOME - - GNOME Shell and its components should continue working - - Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions - https://launchpadlibrarian.net/511426552/gse - - [Where problems could occur] - There have been fixes in various places: a11y features and ibus, OSK, various UI fixes,
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
I am facing the same issue since upgrading from 20.04 to 22.04. I have a Lenovo ThinkPad X1 Extreme Gen 3 with an external monitor (Dell P2720DC) connected via USB-C displayport that used to turn off completely but now only blanks with the backlight remaining on. Display server: X11 Display driver: Nvidia 510.85.02 `xset dpms force off` turns off monitor correctly gjs is already installed Any help with debugging this would be useful since I don't see any issues in journalctl I still need to test if Nvidia Prime profile has any effect (performance vs on-demand) or if same occurs under Wayland. -- 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/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985128] Re: [SRU] Update gnome-shell to 42.4 in 22.04
** Description changed: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] - - == Original Description == - GDM fails to activate the login session in AWS Workspaces - - We may get this error: - - Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once - Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso - Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > - _promisify/proto[asyncFunc]/https://bugs.launchpad.net/bugs/1985128 Title: [SRU] Update gnome-shell to 42.4 in 22.04 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: Confirmed 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/oem-priority/+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 1985128] Re: [SRU] Update gnome-shell to 42.4 in 22.04
** Description changed: + [Impact] + This is the current GNOME 42.4 stable update, including some fixes and + translation updates. + + https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS + + [ Test case ] + + The update is part of GNOME stable updates + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + GNOME Shell and its components should continue working + + Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions + https://launchpadlibrarian.net/511426552/gse + + [ Regression potential ] + + == Original Description == GDM fails to activate the login session in AWS Workspaces We may get this error: Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > _promisify/proto[asyncFunc]/https://bugs.launchpad.net/bugs/1985128 Title: [SRU] Update gnome-shell to 42.4 in 22.04 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] == Original Description == GDM fails to activate the login session in AWS Workspaces We may get this error: Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > _promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985128] Re: [SRU] Update gnome-shell to 42.4 in 22.04
** Summary changed: - GDM fails to activate the login session in AWS Workspaces + [SRU] Update gnome-shell to 42.4 in 22.04 ** Description changed: + + GDM fails to activate the login session in AWS Workspaces + We may get this error: Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > - _promisify/proto[asyncFunc]/https://bugs.launchpad.net/bugs/1985128 Title: [SRU] Update gnome-shell to 42.4 in 22.04 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: [Impact] This is the current GNOME 42.4 stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-42/NEWS [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] == Original Description == GDM fails to activate the login session in AWS Workspaces We may get this error: Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > _promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985128] Re: GDM fails to activate the login session in AWS Workspaces
** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => High -- 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/1985128 Title: [SRU] Update gnome-shell to 42.4 in 22.04 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: GDM fails to activate the login session in AWS Workspaces We may get this error: Aug 05 18:05:39 ip-198-19-76-222 gdm3[837]: Gdm: GdmSession: conversation dcv-graphical-sso started more than once Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: _reportInitError dcv-graphical-sso Aug 05 18:05:39 ip-198-19-76-222 gnome-shell[1006]: JS ERROR: Failed to start dcv-graphical-sso verification: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Spawn.Failed: Could not create authentication > _promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971473] Re: Untranslated desktop file
This looks like it should be uploaded, but doesn't need to actually be
released into -updates, as there's no user-visible change?
I've marked this as block-proposed, so it will sit happily on the
pending SRU page until we need to make other changes to system-config-
printer. If I've misunderstood, and that's not appropriate, feel free to
remove the block-proposed-jammy tag.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1971473
Title:
Untranslated desktop file
Status in system-config-printer package in Ubuntu:
Fix Released
Status in system-config-printer source package in Jammy:
Fix Committed
Bug description:
[Impact]
While the Ubuntu changes include translatable strings, the .pot file
does not get refreshed when building, but upstream's .pot already in
the po/ directory gets imported to LP. As a result, some strings such
as "Printers" in the .desktop file show up untranslated.
There is a temorary workaround in place, but this proposal makes sure
that the fix won't be overwritten by the upstream .pot in case of some
additional package upload to jammy-proposed/jammy-updates.
[Test Plan]
It may be advisable to install system-config-printer{,-common} from
jammy-proposed and confirm that the updated packages work as usual.
But this is all about language packs in future point releases, and to
confirm the intention with this upload, please take these steps:
* Check out the translation import queue:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+imports
and confirm that the new po/system-config-printer.pot file was imported
successfully.
* Visit this page:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+pots/system-config-printer/oc/569
and confirm that it still leads to the "Printers" page with an Occitan
translation.
[Where problems could occur]
The buildlogs include some warnings related to the creation of the
.pot file. But we don't really know if upstream does it better, and I
have not identified any significant resulting issue.
[Original description]
Hello,
I am using Ubuntu MATE and on its control centre the entry "Printers" is not
translated whereas 100% translated.
It comes from the desktop file apparently. It happens to me in Occitan,
Catalan and French, didn't try more locales.
I opened an issue here:
https://github.com/mate-desktop/mate-control-center/issues/693#issuecomment-1115713053
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1971473/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971473] Re: Untranslated desktop file
Hello Quentin, or anyone else affected,
Accepted system-config-printer into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/system-config-
printer/1.5.16-0ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: system-config-printer (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
** Tags added: block-proposed-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1971473
Title:
Untranslated desktop file
Status in system-config-printer package in Ubuntu:
Fix Released
Status in system-config-printer source package in Jammy:
Fix Committed
Bug description:
[Impact]
While the Ubuntu changes include translatable strings, the .pot file
does not get refreshed when building, but upstream's .pot already in
the po/ directory gets imported to LP. As a result, some strings such
as "Printers" in the .desktop file show up untranslated.
There is a temorary workaround in place, but this proposal makes sure
that the fix won't be overwritten by the upstream .pot in case of some
additional package upload to jammy-proposed/jammy-updates.
[Test Plan]
It may be advisable to install system-config-printer{,-common} from
jammy-proposed and confirm that the updated packages work as usual.
But this is all about language packs in future point releases, and to
confirm the intention with this upload, please take these steps:
* Check out the translation import queue:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+imports
and confirm that the new po/system-config-printer.pot file was imported
successfully.
* Visit this page:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+pots/system-config-printer/oc/569
and confirm that it still leads to the "Printers" page with an Occitan
translation.
[Where problems could occur]
The buildlogs include some warnings related to the creation of the
.pot file. But we don't really know if upstream does it better, and I
have not identified any significant resulting issue.
[Original description]
Hello,
I am using Ubuntu MATE and on its control centre the entry "Printers" is not
translated whereas 100% translated.
It comes from the desktop file apparently. It happens to me in Occitan,
Catalan and French, didn't try more locales.
I opened an issue here:
https://github.com/mate-desktop/mate-control-center/issues/693#issuecomment-1115713053
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1971473/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761374] Re: Scrolling the app grid incurs very high CPU usage
With triple buffering: The stutter was fixed in mutter 42 for Ubuntu. Without triple buffering: The root cause of the high GPU usage is fixed in gnome-shell 43. ** Tags added: fixed-in-43 fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed -- 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/1761374 Title: Scrolling the app grid incurs very high CPU usage Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/174 Scrolling the app grid incurs very high CPU usage. On an i7-7700 desktop it uses 47% CPU (compared to 17% to display a maximized glxgears). I imagine most machines can't scroll the app grid smoothly. It doesn't appear smooth on this machine so I would look at the CPU usage problem first. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1761374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986756] Re: gnome-shell crashed with SIGSEGV in CLUTTER_IS_ACTION() from clutter_action_get_phase() from clutter_actor_run_actions() from clutter_actor_event() from _clutter_a
** Summary changed: - /usr/bin/gnome-shell:11:CLUTTER_IS_ACTION:clutter_action_get_phase:clutter_actor_run_actions:clutter_actor_event:_clutter_actor_handle_event + gnome-shell crashed with SIGSEGV in CLUTTER_IS_ACTION() from clutter_action_get_phase() from clutter_actor_run_actions() from clutter_actor_event() from _clutter_actor_handle_event() -- 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/1986756 Title: gnome-shell crashed with SIGSEGV in CLUTTER_IS_ACTION() from clutter_action_get_phase() from clutter_actor_run_actions() from clutter_actor_event() from _clutter_actor_handle_event() 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 42.2-0ubuntu0.2, the problem page at https://errors.ubuntu.com/problem/7590c855d87e9f7e64e20163b14554e73483b125 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/1986756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986757] Re: gnome-shell crashed with SIGSEGV in meta_drm_buffer_ensure_fb_id() from process_mode_set() from process_entries() from meta_kms_impl_device_simple_process_update()
** Summary changed: - /usr/bin/gnome-shell:11:meta_drm_buffer_ensure_fb_id:process_mode_set:process_entries:meta_kms_impl_device_simple_process_update:meta_kms_impl_device_process_update + gnome-shell crashed with SIGSEGV in meta_drm_buffer_ensure_fb_id() from process_mode_set() from process_entries() from meta_kms_impl_device_simple_process_update() from meta_kms_impl_device_process_update() -- 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/1986757 Title: gnome-shell crashed with SIGSEGV in meta_drm_buffer_ensure_fb_id() from process_mode_set() from process_entries() from meta_kms_impl_device_simple_process_update() from meta_kms_impl_device_process_update() 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 42.2-0ubuntu0.2, the problem page at https://errors.ubuntu.com/problem/8bc8f2028dd652c4b8cced87a84331ed3044881a 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/1986757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986756] [NEW] gnome-shell crashed with SIGSEGV in CLUTTER_IS_ACTION() from clutter_action_get_phase() from clutter_actor_run_actions() from clutter_actor_event() from _clutter
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.2-0ubuntu0.2, the problem page at https://errors.ubuntu.com/problem/7590c855d87e9f7e64e20163b14554e73483b125 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy kinetic -- 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/1986756 Title: gnome-shell crashed with SIGSEGV in CLUTTER_IS_ACTION() from clutter_action_get_phase() from clutter_actor_run_actions() from clutter_actor_event() from _clutter_actor_handle_event() 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 42.2-0ubuntu0.2, the problem page at https://errors.ubuntu.com/problem/7590c855d87e9f7e64e20163b14554e73483b125 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/1986756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986757] [NEW] gnome-shell crashed with SIGSEGV in meta_drm_buffer_ensure_fb_id() from process_mode_set() from process_entries() from meta_kms_impl_device_simple_process_update
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.2-0ubuntu0.2, the problem page at https://errors.ubuntu.com/problem/8bc8f2028dd652c4b8cced87a84331ed3044881a 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/1986757 Title: gnome-shell crashed with SIGSEGV in meta_drm_buffer_ensure_fb_id() from process_mode_set() from process_entries() from meta_kms_impl_device_simple_process_update() from meta_kms_impl_device_process_update() 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 42.2-0ubuntu0.2, the problem page at https://errors.ubuntu.com/problem/8bc8f2028dd652c4b8cced87a84331ed3044881a 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/1986757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Partial duplicate: bug 1816497 ** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => In Progress ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** Changed in: firefox (Ubuntu) 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/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux browsers. We will close this bug when both browsers will have Va-api decoding working OOTB without user interaction like in WinOS and MacOS August 2022 : * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1 ) -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need to fix this as most youtube is AV1 now. * In july 2020, things are getting better : - Chromium : A patch is used on most distro packages. , more info here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1816497 - Firefox : Firefox team has done a great job and now Va-api decoding in Wayland is possible and X11 is possible in nightly ! Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 * In 2015 I opened this bug , no easy solution was available and battery drained when playing video in browser was crazy. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
