[Bug 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google released their updated fonts-noto-color-emoji Friday. We also need to update glib so that new non-emoji Unicode characters are handled correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 Other packages needed but don't affect UI - - node-unicode-data utf8proc + node-unicode-property-aliases + node-unicode-property-aliases-ecmascript + node-unicode-property-value-aliases + node-unicode-property-value-aliases-ecmascript + node-unicode-data which will start a small transition + node-esutils + node-json5 + node-regenerate-unicode-properties + node-regexpu-core + node-regjsparser maybe more universe packages Declined changes harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1989626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles
A bug from 2012, still affects me in 2022 on Ubuntu 22.04 and Linux Mint 21, using gvfs 1.48.2-0ubuntu1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/951585 Title: gvfsd-afp consumes 100% of processor cycles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990065] [NEW] Unicode 15.0 update for Gucharmap
Public bug reported: The GNOME Character Map (gucharmap) app seems to have been updated to Unicode 15.0 version. However, the package on Ubuntu is still the old one. I'll be more than happy if the gucharmap 15.0 will also available in the next update of the Ubuntu package. Gucharmap update commit on Gitlab: https://gitlab.gnome.org/GNOME/gucharmap/-/commit/36de4b20deb47bccd8434e36dcc48db8b9460e47 best wishes, Ilham ** Affects: gucharmap (Ubuntu) Importance: Undecided Status: New ** Tags: character map -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1990065 Title: Unicode 15.0 update for Gucharmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1990065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990024] Re: screenshot a window captures also a large border
Also click on 'Show Pointer' has no visible effect so is impossible to know if the pointer will be visible in the screenshot/screencast or not. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1990024 Title: screenshot a window captures also a large border To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_win
Also still randomly getting gnome crashes on Jammy. Desktop PC with single monitor (second monitor still connected via VGA but power cable removed - to try and workaround this bug). Seems to happen when the main monitor goes to sleep. Output of: journalctl -n 300 /usr/bin/gnome-shell ...// Sep 18 16:41:37 workstation2 gnome-shell[2424]: libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)) Sep 18 16:41:37 workstation2 gnome-shell[2424]: Bail out! libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)) Sep 18 16:41:37 workstation2 gnome-shell[2424]: GNOME Shell crashed with signal 6 ...// -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970917 Title: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_window_update_for_monitors_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989590] Re: Can't click on dock items if status drop-down is shown
I believe this is a gnome-shell bug. I am also unable to click the app name in the top bar or open the Activities Overview when the quick settings menu is open. See https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5887 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5887 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5887 ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome- shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989590 Title: Can't click on dock items if status drop-down is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990000] Re: gnome-shell crashed with SIGSEGV in getenv("STEMD_DEVICE_VERIFY_SYSFS")
It looks like libudev is passing bogus memory to getenv().
** Summary changed:
- gnome-shell crashed with SIGSEGV in __GI_getenv()
+ gnome-shell crashed with SIGSEGV in getenv("STEMD_DEVICE_VERIFY_SYSFS")
** Package changed: gnome-shell (Ubuntu) => udev (Ubuntu)
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/199
Title:
gnome-shell crashed with SIGSEGV in
getenv("STEMD_DEVICE_VERIFY_SYSFS")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/199/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990089] [NEW] Screen freeze when performing memory stress in Wayland mode
Public bug reported:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419,
fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, argc=1,
argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-chansey+X25
InstallationDate: Installed on 2022-09-06 (12 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: oem-priority
Importance: Critical
Assignee: jeremyszu (os369510)
Status: In Progress
** Affects: linux (Ubuntu)
[Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1982914 stella -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Attachment added: "strace-when-issue-happening" https://bugs.launchpad.net/bugs/1990089/+attachment/5616860/+files/strace-when-issue-happening -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Attachment added: "ftrace-when-issue-happening" https://bugs.launchpad.net/bugs/1990089/+attachment/5616861/+files/ftrace-when-issue-happening -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990089] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1990089 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2431 https://gitlab.gnome.org/GNOME/mutter/-/issues/2431 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2431 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6851 https://gitlab.freedesktop.org/drm/intel/-/issues/6851 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/6851 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989590] Re: Can't click on dock items if status drop-down is shown
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5887 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989590 Title: Can't click on dock items if status drop-down is shown To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982434] Re: Laptop completely freezes.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1982434 Title: Laptop completely freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
While this is a kernel bug, we will probably do a workaround in mutter before the kernel is ever fixed. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mutter (Ubuntu) Status: New => Opinion ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_win
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2554 ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Released ** Tags added: fixed-in-43.rc fixed-upstream ** No longer affects: gnome-shell (Ubuntu) ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970917 Title: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_window_update_for_monitors_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988488] Re: Screen freeze at the moment of login
Please attach a system log (from journalctl) showing the time at which the screen frozen. ** Tags added: vmwgfx ** Tags added: virtualbox -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze at the moment of login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1988488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988488] Re: Screen freeze at the moment of login
** Package changed: gdm3 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze at the moment of login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1988488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989726] Re: Only a quarter of the screen showing in VirtualBox
Also tracking in private bug 1989170. ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989726 Title: Only a quarter of the screen showing in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989726/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1
The only definite crash I can see here happened during GPU startup: [ 3020.788168] lapis gnome-shell[13120]: Created gbm renderer for '/dev/dri/card1' [ 3021.413765] lapis gnome-shell[13120]: GNOME Shell crashed with signal 11 [ 3021.413765] lapis gnome-shell[13120]: == Stack trace for context 0x555a549a04b0 == And then it restarted successfully: [ 3037.624313] lapis gnome-shell[22361]: Running GNOME Shell (using mutter 42.2) as a Wayland display server [ 3037.648641] lapis gnome-shell[22361]: Device '/dev/dri/card1' prefers shadow buffer [ 3037.951835] lapis gnome-shell[22361]: Added device '/dev/dri/card1' (nouveau) using non-atomic mode setting. [ 3037.953804] lapis gnome-shell[22361]: Device '/dev/dri/card0' prefers shadow buffer [ 3037.956366] lapis gnome-shell[22361]: Added device '/dev/dri/card0' (i915) using atomic mode setting. [ 3037.995604] lapis gnome-shell[22361]: Created gbm renderer for '/dev/dri/card1' [ 3038.005524] lapis gnome-shell[22361]: Created gbm renderer for '/dev/dri/card0' [ 3038.005728] lapis gnome-shell[22361]: Boot VGA GPU /dev/dri/card0 selected as primary So I believe nouveau may be to blame (it usually is). If you can then please disable the discrete GPU in the BIOS and retest. Please also check for crash reports per comment #2. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989325 Title: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989325/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990024] Re: screenshot a window captures also a large border
Upstream has decided this isn't a bug because that's how big the shadow really is: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5700 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5700 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5700 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5700 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1990024 Title: screenshot a window captures also a large border To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1990024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
