[Desktop-packages] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
For my case i have two GPUs, * iGPU for both laptop's screen and a monitor through an HDMI. * Nvidia for AI / CUDA stuff the same problem on Fedora 39 ... -- 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/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=2238711. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2023-09-13T09:59:09+00:00 filbar wrote: After last update I have problems with GDM and gnome-shell. When GDM starts id hangs with error: zář 13 11:40:40 fedora systemd[1]: Starting gdm.service - GNOME Display Manager... zář 13 11:40:40 fedora systemd[1]: Started gdm.service - GNOME Display Manager. zář 13 11:40:59 2001-1ae9-2e8-fa00-5260-9dab-358b-fd26.ip6.tmcz.cz gdm[928]: Gdm: GdmDisplay: Session never registered, failing zář 13 11:40:59 2001-1ae9-2e8-fa00-5260-9dab-358b-fd26.ip6.tmcz.cz gdm[928]: Gdm: Child process -1064 was already dead. zář 13 11:40:59 2001-1ae9-2e8-fa00-5260-9dab-358b-fd26.ip6.tmcz.cz gdm[928]: Gdm: GdmDisplay: Session never registered, failing zář 13 11:40:59 2001-1ae9-2e8-fa00-5260-9dab-358b-fd26.ip6.tmcz.cz gdm[928]: Gdm: Child process -1064 was already dead After downgrade of gnome-shell all starts working Reproducible: Always Steps to Reproduce: 1. Update fedora 2. Reboot 3. gdm hangs Actual Results: GDM hankgs Expected Results: GDM login screen Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/0 On 2023-09-16T10:18:50+00:00 filbar wrote: Created attachment 1989131 Debug info Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/1 On 2023-09-18T09:51:06+00:00 filbar wrote: I log i found abrt-notification[1836]: Process 1141 (gnome-shell) crashed in cogl_gl_create_timestamp_query() This works in gnome-shell beta - after upgrate to rc version I have this error- Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/2 On 2023-09-22T10:47:35+00:00 kparal wrote: Filip, please attach a full system journal of the failed boot. `journalctl -b > journal.txt` for the current boot, or `journalctl -b -1 > journal.txt` for the previous boot. Thanks. Also please attach `lspci` output. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/3 On 2023-09-24T21:23:32+00:00 james wrote: Seen here after upgrade to F39 on a machine with i3-1005G1 graphics. kernel-6.5.4-300.fc39.x86_64 mesa-dri-drivers-23.2.0~rc3-1.fc39.x86_64 gdm-45.0.1-1.fc39.x86_64 mutter-45.0-2.fc39.x86_64 gnome-shell-45.0-1.fc39.x86_64 My journal, lspci and backtrace attached below. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/4 On 2023-09-24T21:23:57+00:00 james wrote: Created attachment 1990365 output from journalctl -b Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/5 On 2023-09-24T21:24:16+00:00 james wrote: Created attachment 1990366 output from lspci Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/6 On 2023-09-24T21:24:34+00:00 james wrote: Created attachment 1990367 backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/7 On 2023-09-26T11:27:40+00:00 kparal wrote: Thanks, James. Could you please file a ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues , attach or link the files you attached here, and paste the resulting upstream ticket URL here? Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/8 On 2023-09-27T08:56:47+00:00 james wrote: (In reply to Kamil Páral from comment #8) > Thanks, James. Could you please file a ticket at > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues , attach or link the > files you attached here, and paste the resulting upstream ticket URL here? https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7053 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/16 On 2023-09-27T09:01:06+00:00 james wrote: Moved to mutter: https://gitlab.gnome.org/GNOME/mutter/-/issues/3056 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/comments/17
[Desktop-packages] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
Tracking in: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #2238711 https://bugzilla.redhat.com/show_bug.cgi?id=2238711 ** Also affects: mesa (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2238711 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3056 https://gitlab.gnome.org/GNOME/mutter/-/issues/3056 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3056 Importance: Unknown Status: Unknown ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Summary changed: - gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() + gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() -- 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/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
It appears 'pipe' is NULL in the Mesa source at:
static void
end_query(struct gl_context *ctx, struct gl_query_object *q)
{
struct st_context *st = st_context(ctx);
struct pipe_context *pipe = ctx->pipe;
bool ret = false;
st_flush_bitmap_cache(st_context(ctx));
if ((q->Target == GL_TIMESTAMP ||
q->Target == GL_TIME_ELAPSED) &&
!q->pq) {
q->pq = pipe->create_query(pipe, PIPE_QUERY_TIMESTAMP, 0);
q->type = PIPE_QUERY_TIMESTAMP;
}
I can't reproduce the problem myself so I wonder are you using two GPUs?
Do you have a monitor plugged into an Nvidia GPU?
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9889
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889
--
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/2037497
Title:
gnome-shell crashed with SIGSEGV at NULL from end_query() from
cogl_gl_create_timestamp_query() from
cogl_onscreen_egl_swap_buffers_with_damage()
Status in Mesa:
New
Status in Mutter:
Fix Released
Status in mesa package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Status in mesa package in Fedora:
Confirmed
Bug description:
crash after update
wayland session is not accessible anymore
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 27 05:52:26 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45.0-2ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
?? ()
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2037497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037527] Re: [Ffe] libwebp
** Changed in: libwebp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: Incomplete Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) Changes since mantic version 1.2.4-0.3 == libwebp (1.3.2-0.3) unstable; urgency=medium * Non-maintainer upload. * Fix invalid incremental decoding check. (Closes: #1052447) * Fix next is invalid pointer when WebPSafeMalloc fails * Fix static analyzer warnings. -- Salvatore Bonaccorso Fri, 22 Sep 2023 09:41:18 +0200 libwebp (1.3.2-0.2) unstable; urgency=medium * Non-maintainer upload. * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. (Closes: #1052355) -- Boyuan Yang Wed, 20 Sep 2023 15:59:13 -0400 libwebp (1.3.2-0.1) unstable; urgency=medium * Non-maintainer upload. * Upload to unstable. -- Boyuan Yang Wed, 20 Sep 2023 11:03:28 -0400 libwebp (1.3.2-0.1~exp2) experimental; urgency=medium * Non-maintainer upload. [ Gianfranco Costamagna ] * Also install .a files again. * Make sure we have built and installed anim_dump and anim_diff. (Closes: #1023482) -- Boyuan Yang Fri, 15 Sep 2023 14:41:40 -0400 libwebp (1.3.2-0.1~exp1) experimental; urgency=medium * Non-maintainer upload. * New upstream release 1.3.2. + The 1.3.x branch introduces libsharpyuv, which will be introduced as separate Debian binary packages. (Closes: #1040970) + CVE-2023-4863 is handled in this release. (LP: #2035220) * debian/gbp.conf: Use ignore-branch=True to avoid limitation on experimental branch. * debian/control: + Drop unnecessary build-dependency on autotools-related packages. + Add build-dependency on pkg-config. + Migrate buildsystem to cmake. (Closes: #1040972, LP: #2013083) + Apply RPATH-related hotfix before debhelper compat level 14. + Add new binary packages: libsharpyuv-dev, libsharpyuv0, libwebpdecoder3. * debian/libwebp-dev.install: Do not install static library anymore since CMake is not building them by default. * debian/rules: + Enforce --buildsystem=cmake. + Drop explicit option --enable-aligned, this option has been removed by libwebp upstream (see upstream ChangeLog). * debian/docs: Rename to libwebp-dev.docs to avoid confusion. * debian/patches: Drop all old patches, merged upstream. * debian/patches/: + 0001-CMakeLists.txt-Install-CMake-Config-to-arch-dep-loca.patch: Add patch to install CMake Config files to architecture-dependent location instead to retain Multi-Arch property of dev packages. * debian/copyright: Completely rewritten in machine-readable copyright format. -- Boyuan Yang Thu, 14 Sep 2023 22:22:30 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2037527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037527] Re: [Ffe] libwebp
** Changed in: libwebp (Ubuntu) Assignee: Ubuntu Release Team (ubuntu-release) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: Incomplete Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) Changes since mantic version 1.2.4-0.3 == libwebp (1.3.2-0.3) unstable; urgency=medium * Non-maintainer upload. * Fix invalid incremental decoding check. (Closes: #1052447) * Fix next is invalid pointer when WebPSafeMalloc fails * Fix static analyzer warnings. -- Salvatore Bonaccorso Fri, 22 Sep 2023 09:41:18 +0200 libwebp (1.3.2-0.2) unstable; urgency=medium * Non-maintainer upload. * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. (Closes: #1052355) -- Boyuan Yang Wed, 20 Sep 2023 15:59:13 -0400 libwebp (1.3.2-0.1) unstable; urgency=medium * Non-maintainer upload. * Upload to unstable. -- Boyuan Yang Wed, 20 Sep 2023 11:03:28 -0400 libwebp (1.3.2-0.1~exp2) experimental; urgency=medium * Non-maintainer upload. [ Gianfranco Costamagna ] * Also install .a files again. * Make sure we have built and installed anim_dump and anim_diff. (Closes: #1023482) -- Boyuan Yang Fri, 15 Sep 2023 14:41:40 -0400 libwebp (1.3.2-0.1~exp1) experimental; urgency=medium * Non-maintainer upload. * New upstream release 1.3.2. + The 1.3.x branch introduces libsharpyuv, which will be introduced as separate Debian binary packages. (Closes: #1040970) + CVE-2023-4863 is handled in this release. (LP: #2035220) * debian/gbp.conf: Use ignore-branch=True to avoid limitation on experimental branch. * debian/control: + Drop unnecessary build-dependency on autotools-related packages. + Add build-dependency on pkg-config. + Migrate buildsystem to cmake. (Closes: #1040972, LP: #2013083) + Apply RPATH-related hotfix before debhelper compat level 14. + Add new binary packages: libsharpyuv-dev, libsharpyuv0, libwebpdecoder3. * debian/libwebp-dev.install: Do not install static library anymore since CMake is not building them by default. * debian/rules: + Enforce --buildsystem=cmake. + Drop explicit option --enable-aligned, this option has been removed by libwebp upstream (see upstream ChangeLog). * debian/docs: Rename to libwebp-dev.docs to avoid confusion. * debian/patches: Drop all old patches, merged upstream. * debian/patches/: + 0001-CMakeLists.txt-Install-CMake-Config-to-arch-dep-loca.patch: Add patch to install CMake Config files to architecture-dependent location instead to retain Multi-Arch property of dev packages. * debian/copyright: Completely rewritten in machine-readable copyright format. -- Boyuan Yang Thu, 14 Sep 2023 22:22:30 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2037527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037527] Re: [Ffe] libwebp
What's the rational to want to push for a newer version at this point of the cycle and what sort of testing was done to ensure it's not including potential regressions? The security fixes are included as patches in the current package revision... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: Incomplete Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) Changes since mantic version 1.2.4-0.3 == libwebp (1.3.2-0.3) unstable; urgency=medium * Non-maintainer upload. * Fix invalid incremental decoding check. (Closes: #1052447) * Fix next is invalid pointer when WebPSafeMalloc fails * Fix static analyzer warnings. -- Salvatore Bonaccorso Fri, 22 Sep 2023 09:41:18 +0200 libwebp (1.3.2-0.2) unstable; urgency=medium * Non-maintainer upload. * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. (Closes: #1052355) -- Boyuan Yang Wed, 20 Sep 2023 15:59:13 -0400 libwebp (1.3.2-0.1) unstable; urgency=medium * Non-maintainer upload. * Upload to unstable. -- Boyuan Yang Wed, 20 Sep 2023 11:03:28 -0400 libwebp (1.3.2-0.1~exp2) experimental; urgency=medium * Non-maintainer upload. [ Gianfranco Costamagna ] * Also install .a files again. * Make sure we have built and installed anim_dump and anim_diff. (Closes: #1023482) -- Boyuan Yang Fri, 15 Sep 2023 14:41:40 -0400 libwebp (1.3.2-0.1~exp1) experimental; urgency=medium * Non-maintainer upload. * New upstream release 1.3.2. + The 1.3.x branch introduces libsharpyuv, which will be introduced as separate Debian binary packages. (Closes: #1040970) + CVE-2023-4863 is handled in this release. (LP: #2035220) * debian/gbp.conf: Use ignore-branch=True to avoid limitation on experimental branch. * debian/control: + Drop unnecessary build-dependency on autotools-related packages. + Add build-dependency on pkg-config. + Migrate buildsystem to cmake. (Closes: #1040972, LP: #2013083) + Apply RPATH-related hotfix before debhelper compat level 14. + Add new binary packages: libsharpyuv-dev, libsharpyuv0, libwebpdecoder3. * debian/libwebp-dev.install: Do not install static library anymore since CMake is not building them by default. * debian/rules: + Enforce --buildsystem=cmake. + Drop explicit option --enable-aligned, this option has been removed by libwebp upstream (see upstream ChangeLog). * debian/docs: Rename to libwebp-dev.docs to avoid confusion. * debian/patches: Drop all old patches, merged upstream. * debian/patches/: + 0001-CMakeLists.txt-Install-CMake-Config-to-arch-dep-loca.patch: Add patch to install CMake Config files to architecture-dependent location instead to retain Multi-Arch property of dev packages. * debian/copyright: Completely rewritten in machine-readable copyright format. -- Boyuan Yang Thu, 14 Sep 2023 22:22:30 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2037527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037527] Re: [Ffe] libwebp
** Description changed: - 9/13/2023: version 1.3.2 - This is a binary compatible release. - * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) + This is a binary compatible release. + * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 - This is a binary compatible release. - * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, - CVE-2023-1999) - * improve error reporting through WebPPicture error codes - * fix upsampling for RGB565 and RGBA in NEON builds - * img2webp: add -sharp_yuv & -near_lossless - * Windows builds: - - fix compatibility with clang-cl (#607) - - improve Arm64 performance with cl.exe - - add Arm64EC support - * fix webp_js with emcc >= 3.1.27 (stack size change, #614) - * CMake fixes (#592, #610, #612) - * further updates to the container and lossless bitstream docs (#581, #611) + This is a binary compatible release. + * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, + CVE-2023-1999) + * improve error reporting through WebPPicture error codes + * fix upsampling for RGB565 and RGBA in NEON builds + * img2webp: add -sharp_yuv & -near_lossless + * Windows builds: + - fix compatibility with clang-cl (#607) + - improve Arm64 performance with cl.exe + - add Arm64EC support + * fix webp_js with emcc >= 3.1.27 (stack size change, #614) + * CMake fixes (#592, #610, #612) + * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 - This is a binary compatible release. - * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv - functionality to other libraries; libwebp now depends on this library - * major updates to the container and lossless bitstream docs (#448, #546, - #551) - * miscellaneous warning, bug & build fixes (#576, #583, #584) + This is a binary compatible release. + * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv + functionality to other libraries; libwebp now depends on this library + * major updates to the container and lossless bitstream docs (#448, #546, + #551) + * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) + + Changes since mantic version 1.2.4-0.3 + == + libwebp (1.3.2-0.3) unstable; urgency=medium + + * Non-maintainer upload. + * Fix invalid incremental decoding check. (Closes: #1052447) + * Fix next is invalid pointer when WebPSafeMalloc fails + * Fix static analyzer warnings. + + -- Salvatore Bonaccorso Fri, 22 Sep 2023 09:41:18 +0200 + + libwebp (1.3.2-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. + (Closes: #1052355) + + -- Boyuan Yang Wed, 20 Sep 2023 15:59:13 -0400 + + libwebp (1.3.2-0.1) unstable; urgency=medium + + * Non-maintainer upload. + * Upload to unstable. + + -- Boyuan Yang Wed, 20 Sep 2023 11:03:28 -0400 + + libwebp (1.3.2-0.1~exp2) experimental; urgency=medium + + * Non-maintainer upload. + + [ Gianfranco Costamagna ] + * Also install .a files again. + * Make sure we have built and installed anim_dump and anim_diff. + (Closes: #1023482) + + -- Boyuan Yang Fri, 15 Sep 2023 14:41:40 -0400 + + libwebp (1.3.2-0.1~exp1) experimental; urgency=medium + + * Non-maintainer upload. + * New upstream release 1.3.2. + + The 1.3.x branch introduces libsharpyuv, which will be introduced + as separate Debian binary packages. (Closes: #1040970) + + CVE-2023-4863 is handled in this release. (LP: #2035220) + * debian/gbp.conf: Use ignore-branch=True to avoid limitation on + experimental branch. + * debian/control: + + Drop unnecessary build-dependency on autotools-related packages. + + Add build-dependency on pkg-config. + + Migrate buildsystem to cmake. (Closes: #1040972, LP: #2013083) + + Apply RPATH-related hotfix before debhelper compat level 14. + + Add new binary packages: libsharpyuv-dev, libsharpyuv0, + libwebpdecoder3. + * debian/libwebp-dev.install: Do not install static library anymore + since CMake is not building them by default. + * debian/rules: + + Enforce --buildsystem=cmake. + + Drop explicit option --enable-aligned, this option has been removed + by libwebp upstream (see upstream ChangeLog). + * debian/docs: Rename to libwebp-dev.docs to avoid confusion. + * debian/patches: Drop all old patches, merged upstream. + * debian/patches/: + + 0001-CMakeLists.txt-Install-CMake-Config-to-arch-dep-loca.patch: + Add patch to install
[Desktop-packages] [Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+attachment/5705142/+files/prevjournal.txt -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Daniel, Attached are the files from the two journal commands. I have 2 .crash files in /var/crash: _usr_bin_evolution.1000.crash _usr_bin_nm-connection-editor.1000.crash Is it worth doing the ubuntu-bug command on any/all of those? I do see 50 error reports at https://errors.ubuntu.com/user/ID. Clicking any of the "received" links says "Sorry, you are not a member of a group that is allowed to see the data from error reports. Please fill out this form to request access." Is it safe to post my whoopsie ID here for you to see the list? I do not have the symptoms of the workspace dots staying active as described in #2000644. I have had my system set to fixed, 10 workspaces since installation. There are no files in ~/.local/share/gnome-shell/extensions/ ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+attachment/5705141/+files/journal.txt -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27
[Desktop-packages] [Bug 2037621] Re: Resize chrome window error
It looks like the window is taller than the screen and the mutter constraints logic is in a loop? Please try maximizing the window to see if the problem stops. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037621 Title: Resize chrome window error Status in mutter package in Ubuntu: Incomplete Bug description: Link video record screen error when resize: https://file.io/IOScym0f5t43 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 14:54:31 2023 DistUpgraded: 2023-06-17 11:37:11,067 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Rembrandt [Radeon 680M] [17aa:3815] InstallationDate: Installed on 2023-05-12 (138 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 82SJ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-33-generic root=UUID=9f9d123f-7118-4e68-8df1-a4ff5450750e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-06-17 (103 days ago) dmi.bios.date: 07/26/2022 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: J8CN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76501 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 Pro 14ARH7 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrJ8CN29WW:bd07/26/2022:br1.29:efr1.29:svnLENOVO:pn82SJ:pvrIdeaPad5Pro14ARH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76501WIN:cvnLENOVO:ct10:cvrIdeaPad5Pro14ARH7:skuLENOVO_MT_82SJ_BU_idea_FM_IdeaPad5Pro14ARH7: dmi.product.family: IdeaPad 5 Pro 14ARH7 dmi.product.name: 82SJ dmi.product.sku: LENOVO_MT_82SJ_BU_idea_FM_IdeaPad 5 Pro 14ARH7 dmi.product.version: IdeaPad 5 Pro 14ARH7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2037621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037633] Re: Help browser produces empty windows under nvidia drivers on X11
This behavior is seen for both a dist-upgrade of Ubuntu 23.10 from 23.04 or for a clean install of Ubuntu 23.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2037633 Title: Help browser produces empty windows under nvidia drivers on X11 Status in yelp package in Ubuntu: New Bug description: The Help browser in the dock on Mantic produces an empty window without content when launch under X11 using the nvidia-driver-535 535.104.05-0ubuntu4 video drivers. If I logout and login back in under Wayland, the Help browser behaves normally and produces the expected content in its window. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3 Uname: Linux 6.5.0-6-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 05:33:27 2023 InstallationDate: Installed on 2023-09-22 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037633] [NEW] Help browser produces empty windows under nvidia drivers on X11
Public bug reported: The Help browser in the dock on Mantic produces an empty window without content when launch under X11 using the nvidia-driver-535 535.104.05-0ubuntu4 video drivers. If I logout and login back in under Wayland, the Help browser behaves normally and produces the expected content in its window. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3 Uname: Linux 6.5.0-6-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 05:33:27 2023 InstallationDate: Installed on 2023-09-22 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2037633 Title: Help browser produces empty windows under nvidia drivers on X11 Status in yelp package in Ubuntu: New Bug description: The Help browser in the dock on Mantic produces an empty window without content when launch under X11 using the nvidia-driver-535 535.104.05-0ubuntu4 video drivers. If I logout and login back in under Wayland, the Help browser behaves normally and produces the expected content in its window. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3 Uname: Linux 6.5.0-6-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 05:33:27 2023 InstallationDate: Installed on 2023-09-22 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037635] [NEW] Add support for Pi 5
*** This bug is a duplicate of bug 2037642 *** https://bugs.launchpad.net/bugs/2037642 Public bug reported: Backport support for new BCM2712 HW (used on Pi 5) to Mantic mesa. Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Description changed: - Placeholder + Backport support for new bcm2712 HW (used on Pi 5) to Mantic mesa. + Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 ** Description changed: - Backport support for new bcm2712 HW (used on Pi 5) to Mantic mesa. - Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 + Backport support for new BCM2712 HW (used on Pi 5) to Mantic mesa. + + Upstream MR: + https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 ** This bug has been marked a duplicate of bug 2037642 [FFe] Raspberry Pi 5 support -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037635 Title: Add support for Pi 5 Status in mesa package in Ubuntu: New Status in mesa source package in Mantic: New Bug description: Backport support for new BCM2712 HW (used on Pi 5) to Mantic mesa. Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
The rpiboot package can be skipped for now; according to upstream the updated package won't be ready at release. The separate bug LP: #2032178 will track updates if/when I can get the uploaded. ** No longer affects: rpiboot (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rpi-eeprom (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pipewire (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rpiboot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-raspi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware-raspi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcamera (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] [NEW] [FFe] Raspberry Pi 5 support
Public bug reported: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement ** Affects: libcamera (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-meta-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: mesa (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: pipewire (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: rpi-eeprom (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: linux-meta-raspi (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: libcamera (Ubuntu) Importance: Undecided Status: New ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: New ** Also affects: rpi-eeprom (Ubuntu) Importance: Undecided Status: New ** Also affects: rpiboot (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Description changed: [ Impact ] - * HWE for Raspberry Pi 5 https://raspberrypi.com/5 + * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] - * Private builds tested on all existing/supported Raspberry Pi SKUs in + * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants - * No regressions on any existing SKUs + * No regressions on any existing SKUs - * Test that Raspberry Pi 5 boards work + * Test that Raspberry Pi 5 boards work [ Where problems could occur ] - * Mesa is upgraded, and there are patches to mesa, the raspberry-pi + * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. - * libcamera has new build-depends for the raspberry-pi specific - provider which also affects pipewire to provide full webcam support. + * libcamera has new build-depends on new package libpisp for the + raspberry-pi specific provider which also affects pipewire to provide + full webcam support. - * These dependencies, will need to make their way into gnome platform + * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] - - * The proposed code changes have been tested in private, prior to public announcement + + * The proposed code changes have been tested in private, prior to + public announcement ** Summary changed: - Raspberry Pi 5 support + [FFe] Raspberry Pi 5 support -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
[Desktop-packages] [Bug 2037655] [NEW] dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs
Public bug reported: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Description changed: - On the latest Mantic beta using firefox spams the log with message: + On the latest 23.10 Mantic beta using firefox 118.0 spams the log with + message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" -- 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/2037655 Title: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs Status in firefox package in Ubuntu: New Bug description: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037340] Re: Four Screens
I can't think of a good solution here, but if you would like the same "safe graphics" mode that also happens to disable the GPU, then you can edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" and then run: sudo update-grub and reboot. Though performance will be poor. ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags added: radeon ** Summary changed: - Four Screens + [radeon] iMac a1311 is split into four screens -- 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/2037340 Title: [radeon] iMac a1311 is split into four screens Status in linux-hwe-6.2 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I apologize for any grammar issues, but I can barely see what I am typing. Essentially, when I installed Ubuntu, I had to do so in safe graphics mode, as the screen would otherwise split itself into four different displays that had small amounts of resolution and are rather pale. I managed to install it, but once that happend, and it restarted, it went back to being four screens. I am not sure what to do, as I cannot really read any lines of code. Thank you for your help. I am using an iMac a1311, with an HDD and installed from a flashed usb. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 20:33:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2023-09-24 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac10,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=be40ad74-149a-443c-99b3-2dbae10973a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268CC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268CC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2037340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037621] [NEW] Resize chrome window error
Public bug reported: Link video record screen error when resize: https://file.io/IOScym0f5t43 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 14:54:31 2023 DistUpgraded: 2023-06-17 11:37:11,067 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Rembrandt [Radeon 680M] [17aa:3815] InstallationDate: Installed on 2023-05-12 (138 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 82SJ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-33-generic root=UUID=9f9d123f-7118-4e68-8df1-a4ff5450750e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-06-17 (103 days ago) dmi.bios.date: 07/26/2022 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: J8CN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76501 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 Pro 14ARH7 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrJ8CN29WW:bd07/26/2022:br1.29:efr1.29:svnLENOVO:pn82SJ:pvrIdeaPad5Pro14ARH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76501WIN:cvnLENOVO:ct10:cvrIdeaPad5Pro14ARH7:skuLENOVO_MT_82SJ_BU_idea_FM_IdeaPad5Pro14ARH7: dmi.product.family: IdeaPad 5 Pro 14ARH7 dmi.product.name: 82SJ dmi.product.sku: LENOVO_MT_82SJ_BU_idea_FM_IdeaPad 5 Pro 14ARH7 dmi.product.version: IdeaPad 5 Pro 14ARH7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2037621 Title: Resize chrome window error Status in xorg package in Ubuntu: New Bug description: Link video record screen error when resize: https://file.io/IOScym0f5t43 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 14:54:31 2023 DistUpgraded: 2023-06-17 11:37:11,067 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Rembrandt [Radeon 680M] [17aa:3815] InstallationDate: Installed on 2023-05-12 (138 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 82SJ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-33-generic root=UUID=9f9d123f-7118-4e68-8df1-a4ff5450750e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-06-17 (103 days ago) dmi.bios.date: 07/26/2022 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: J8CN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76501 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 Pro 14ARH7 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrJ8CN29WW:bd07/26/2022:br1.29:efr1.29:svnLENOVO:pn82SJ:pvrIdeaPad5Pro14ARH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76501WIN:cvnLENOVO:ct10:cvrIdeaPad5Pro14ARH7:skuLENOVO_MT_82SJ_BU_idea_FM_IdeaPad5Pro14ARH7: dmi.product.family: IdeaPad
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
Thanks Ludovic, so for those smart cards, the pcscd interface has been merged in Snapd (but is apparently only available from 2.60.4 on, so currently you need the beta channel of it), and so I update the test case to a simpler: ---> snap refresh --beta snapd snap refresh --channel stable/pkcs chromium snap connect chromium:pcscd chromium --enable-logging=stderr >chr.log 2>&1 <--- -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
There you go, attached is the journal of the boot when I removed the workaround and got the screen stuck in the off state. I assume this is what you really wanted and not the journal of my current boot. I have since rebooted many times. The messages start at 21:45 which is when I managed to get the screen stuck. I like my privacy, so I also added --no-hostname. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5705055/+files/journal.txt -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
Andreas noticed in the duplicate report that > The chromium console log also shows a lot of these 404 errors for *.woff2 > fonts: > > GET > filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 > net::ERR_FILE_NOT_FOUND -- 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/2019045 Title: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar Status in chromium-browser package in Ubuntu: Triaged Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox or Google Chrome. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037581] Re: Missing ubuntu font when viewing some google docs
*** This bug is a duplicate of bug 2019045 *** https://bugs.launchpad.net/bugs/2019045 Thanks for the report, Andreas, this is a duplicate of LP:2019045, you noticed something important in the log and I'm passing your comment to that report. ** This bug has been marked a duplicate of bug 2019045 [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar -- 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/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037604] [NEW] Backport packages for 22.04.4 HWE stack
Public bug reported: [Impact] The graphics HWE stack from kinetic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-16 - new package in jammy - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, FIXME spirv-headers - needed by s-l-t-16 spirv-llvm-translator-16 - needed to bootstrap libclc from llvm spirv-llvm-translator-16 - needed for the actual libclc-16 after initial bootstrap [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.2.x in order to minimize the chance for those. ** Affects: directx-headers (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: - WIP + [Impact] + The graphics HWE stack from kinetic needs to be backported for 22.04.4 + + directx-headers + - build-dep of the new Mesa + + libdrm + - build-dep of the new Mesa + + llvm-16 + - new package in jammy + - build-dep of the new Mesa + + mesa + - new major release (23.2.x) + - new HW support, FIXME + + spirv-headers + - needed by s-l-t-16 + + spirv-llvm-translator-16 + - needed to bootstrap libclc from llvm + + spirv-llvm-translator-16 + - needed for the actual libclc-16 after initial bootstrap + + [Test case] + Install the new mesa on various hw, see that everything still works like before or better. + + + [Where things could go wrong] + This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.2.x in order to minimize the chance for those. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: [Impact] The graphics HWE stack from kinetic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-16 - new package in jammy - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, FIXME spirv-headers - needed by s-l-t-16 spirv-llvm-translator-16 - needed to bootstrap libclc from llvm spirv-llvm-translator-16 - needed for the actual libclc-16 after initial bootstrap [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037569] Re: udev issues with mantic beta
** Changed in: ubuntu-z-systems Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Triaged Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Triaged Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5174 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5168 -- 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/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
