[Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936703] Re: screen keyboard doesn't work on authentication window
** Tags added: 2-in-1 apport-collected jammy oem-priority wayland- session ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High -- 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/1936703 Title: screen keyboard doesn't work on authentication window To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
They are used for different platform of different OEM. The OEM platform owner tracks specific platform bugs by platform tag in the private bug and we are not able to share the platform information cross OEM. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
okay, I can confirmed it works with latest packages from Jammy. In both 'Launch using Discrete Graphics Card' and '__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia' cases. But it doesn't work for firefox (mine is a snap version) so I think we are good to close this or switch to affect firefox. ** Changed in: oem-priority Status: Incomplete => Invalid -- 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/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2003169 -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000459] Re: Only half of menu if right-clicks mouse on the desktop if scaling screen
** Attachment added: "sosreport-u-ThinkStation-P360-Tower-2022-10-24-cldksuc.tar.xz" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000459/+attachment/5637719/+files/sosreport-u-ThinkStation-P360-Tower-2022-10-24-cldksuc.tar.xz ** Tags added: oem-priority originate-from-1993786 sutton ** Summary changed: - Only half of menu if right-clicks mouse on the desktop if scaling screen + Only shows half of menu if right-clicks mouse on the desktop if scaling screen -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000459] Re: Only half of menu if right-clicks mouse on the desktop if scaling screen
** Attachment added: "menu.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000459/+attachment/5637717/+files/menu.jpg -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000459] Re: Only half of menu if right-clicks mouse on the desktop if scaling screen
** Attachment added: "issue video.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000459/+attachment/5637716/+files/issue%20video.mp4 -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000459] [NEW] Only shows half of menu if right-clicks mouse on the desktop if scaling screen
Public bug reported: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% ** Affects: oem-priority Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1993786 sutton -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Tags added: nvidia-wayland -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+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-1992736 -- 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
** Tags added: originate-from-1992116 -- 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 1990262] Re: Screen reset randomly when moving cursors
** Attachment added: "sosreport-ubuntu-2022-09-07-zluxqrd.tar" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+attachment/5617344/+files/sosreport-ubuntu-2022-09-07-zluxqrd.tar -- 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/1990262 Title: Screen reset randomly when moving cursors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990262] Re: Screen reset randomly when moving cursors
** Attachment added: "20220907_145805.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+attachment/5617343/+files/20220907_145805.mp4 -- 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/1990262 Title: Screen reset randomly when moving cursors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990262] [NEW] Screen reset randomly when moving cursors
Public bug reported: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1990262 Title: Screen reset randomly when moving cursors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+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
The correct fix should in kernel driver or GPU firmware. Please track on drm-intel#6851. ** Changed in: oem-priority Status: In Progress => 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
** 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] 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
** 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] [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
[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
After some checks, it seems because data_device_start_drag() doesn't support MetaWaylandTouch. The fix will impact the mutter architecture and it's more likely a feature request in mutter so far. It can be workaround by either sync MetaWaylandPointer motion and MetaWaylandTouch when meta_wayland_seat_update() or meta_wayland_seat_handle_event() with some tweaks. or some changes in meta_wayland_data_device_start_drag(). As maintainer mentions[1] the drag feature is refactoring part.1: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2068 part.2: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2099 part.3: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2100 and this issue might be fixed in part.5... For both workaround look not suitable with the maintainer's design. I prefer to wait until the refactoring completed by maintainer. [1] https://gitlab.gnome.org/GNOME/mutter/-/issues/2393#note_1532698 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2393 https://gitlab.gnome.org/GNOME/mutter/-/issues/2393 ** Changed in: oem-priority Assignee: jeremyszu (os369510) => (unassigned) -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2025 https://gitlab.gnome.org/GNOME/mutter/-/issues/2025 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2025 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Also affects: gnome-shell-extension-desktop-icons-ng Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell-extension-desktop-icons-ng -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active
Daniel, Thus, does the PPA from comment#14 can fix your case? if it doesn't, then probably there are two issues or other patch(s) are needed. -- 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/1976204 Title: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Aleksandr, sound more likely the other issue. Since this issue is fixed, could you please report the other with attaching logs? -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I can confirmed the original issue gone after installing the version from comment#37 ** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to clutter-gst-3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
looks like nvidia-drm is not built in nvidia-340. could you report the other bug for it takes 10 seconds when booting in nvidia-340? and we can leave the information there. -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
nope, drm is not nvidia_drm. I don't have 5.4 + nvidia-340 environment. Thus, I would like to get more information from you. Could you please share 1. dkms status 2. find /lib/modules/$(uname -r) -name 'nvidia*' 3. your "/var/lib/dkms/" probably have nvidia-340 build log with your current kernel, could you please share the contents from the directory? (e.g. /var/lib/dkms/tp_smapi/kernel-5.14.0-1036-oem-x86_64) -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
but it doesn't show in your lsmod. how about `modinfo nvidia_drm`? -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
update: no transition plan for nvidia-340. Then let's see why your nvidia-drm gone. -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
ok, I aware the `nvidia-drm` should support in nvidia-340. Did you blacklist it? Can you check the nvidia-drm whether presenting in your system? you could probably found it under find ... /lib/modules/$(uname -r)/... -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Hi, I aware you don't have "nvidia_drm" which is needed for gdm as well. u-d-c was wait the "nvidia_drm" be probed and your nvidia driver is 340 is quite old as what I known. FWIK, the legacy driver should be nvidia-390 and the next is 470. I wondering why nvidia-340 is not yet be transited to 390 or newer. Hi Alberto, Will nvidia-340 be transited? -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Hi, would you please share: 1. lspci -nvk 2. /var/log/gpu-manager.log 3. journalctl -b -k 4. dpkg -l | grep nvidia 5. lsmod | grep nvidia -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
after upgrading to 42.0-1ubuntu7 and can not reproduce this issue (default X). Selected to Wayland can not reproduce this issue as well. ** Changed in: oem-priority Status: Incomplete => Fix Committed -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Hi Macros, would you please share the output of `journalctl -b` when issuing happening? -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Hi Marcos, For bug description: --- [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 --- It should be workaround by adding "NVreg_PreserveVideoMemoryAllocations". Would you please share $ cat /proc/driver/nvidia/params ? -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
For comment#10: NVreg_TemporaryFilePath means to use the specific path, if you didn't specify it then it will default to use /tmp. (if your /tmp has enough space to use then it's fine) FWIK, the firefox is now from snap and the stable firefox is disable Wayland. Thus, it could be the other problem. --- For comment#11: Looks like the other issue, probably attach the log on a new bug report? -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Copied the finding from https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 since this bug is created long time. Pieces of log ``` 四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00: GPU-581d669f-ec00-4588-ca5f-15ab24136974 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: Shader Program Header 18 Error 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405840=0x8204 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405848=0x8000 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=1270, Graphics Exception: ChID 0010, Class c597, Offset , Data ``` For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. Tried 510.60 as well and the problem is persistent. ** Tags added: jiayi wayland -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969566] Re: Default to Xorg on NVIDIA-only systems
and for https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 as well. BTW, I think we should say "on nvidia as boot_vga systems"? Says, Hybrid desktop (boot from intel or boot from nvidia) or nvidia only laptops or other scenarios. Hybrid desktop boot from nvidia is needed to be considered in this case, and when we talking about chassis_type then it means the rule needs to consider to check chassis_type from dmi-table. If chassis_type is not mandatory condition, then we can prevent to make it complex. -- 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/1969566 Title: Default to Xorg on NVIDIA-only systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
Hi Michael, do you mean the patch to disable wayland on nVidia? -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Changed in: oem-priority Status: Confirmed => Fix Released -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969142] Re: Display glitch after resume on Wayland if boot vga is nvidia
** Description changed: [Steps to reproduce] 1. Install Jammy and dist-ugprade 2. systemctl suspend 3. press power button to resume [Expect result] system resume smoothly [Actual result] display glitch (please see the attachment) + + Pieces of log + ``` + 四 14 22:55:10 kernel: NVRM: GPU at PCI::01:00: GPU-581d669f-ec00-4588-ca5f-15ab24136974 + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: Shader Program Header 18 Error + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405840=0x8204 + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=798, Graphics Exception: ESR 0x405848=0x8000 + 四 14 22:55:10 kernel: NVRM: Xid (PCI::01:00): 13, pid=1270, Graphics Exception: ChID 0010, Class c597, Offset , Data + ``` For GDM, it needs at least https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1429657 to protect issue happens. For Mutter, a related patch is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341/diffs could cover if nvidia is secondary GPU. For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 23:51:06 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-14T22:23:09.064003 -- 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/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969142] Re: Display glitch after resume on Wayland if boot vga is nvidia
** Attachment added: "FD78E3EA-8F81-4B58-B27A-F864F5CA5480.jpg" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142/+attachment/5580753/+files/FD78E3EA-8F81-4B58-B27A-F864F5CA5480.jpg ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- 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/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969142] [NEW] Display glitch after resume on Wayland if boot vga is nvidia
Public bug reported: [Steps to reproduce] 1. Install Jammy and dist-ugprade 2. systemctl suspend 3. press power button to resume [Expect result] system resume smoothly [Actual result] display glitch (please see the attachment) For GDM, it needs at least https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171#note_1429657 to protect issue happens. For Mutter, a related patch is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341/diffs could cover if nvidia is secondary GPU. For nvidia-driver, u-d-c, we need to follow https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html to setup the parameters after some checks. I appended the parameters: options nvidia NVreg_TemporaryFilePath=/run options nvidia NVreg_PreserveVideoMemoryAllocations=1 and then the problem solved. 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: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 23:51:06 2022 InstallationDate: Installed on 2022-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-14T22:23:09.064003 ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy jiayi nvidia oem-priority wayland -- 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/1969142 Title: Display glitch after resume on Wayland if boot vga is nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Confirmed the gnome will not crash but the system will back to gdm login screen in 1st hot-plugging. Report the bug https://bugs.launchpad.net/oem-priority/+bug/1969121 -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
Confirmed the gnome will not crash but the system will back to gdm login screen in 1st hot-plugging. Report the bug https://bugs.launchpad.net/oem-priority/+bug/1969121 ** Changed in: oem-priority Status: Confirmed => Fix Released -- 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/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
** Description changed: [Steps to reproduce] 1. Install Jammy daily build 2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037 3. reboot with no attach monitor 4. attach monitor after booting [Expect result] external monitor works directly [Actual result] system go back to gdm login screen [Additional information] - the external port is connecting to dGPU. + 1. the external port is connecting to dGPU. + 2. happens on wayland only + 3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 21:22:47 2022 InstallationDate: Installed on 2022-04-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Tags added: nvidia-wayland wayland wayland-session ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969121] [NEW] System fallback to gdm login screen when hot-plugging a external monitor in 1st time
Public bug reported: [Steps to reproduce] 1. Install Jammy daily build 2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037 3. reboot with no attach monitor 4. attach monitor after booting [Expect result] external monitor works directly [Actual result] system go back to gdm login screen [Additional information] 1. the external port is connecting to dGPU. 2. happens on wayland only 3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 21:22:47 2022 InstallationDate: Installed on 2022-04-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy jiayi nvidia nvidia-wayland oem-priority wayland wayland-session ** Also affects: oem-priority Importance: Undecided Status: New ** 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
** Tags added: jiayi oem-priority ** Also affects: oem-priority Importance: Undecided Status: New -- 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/1967450 Title: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
The related issue reported when using Xorg: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966050 -- 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/1967450 Title: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Daniel, In this case, do we have any ticket for nvidia to fix the GBM issue? We would like to highlight this to nVidia. -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Daniel, Thanks for sharing! If there is a patch either from salsa or PPA then I can help to verify it in my case. ** Tags added: jiayi -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Importance: High => Critical ** Tags added: jiayi 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/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Follow-up from comment#12, I can reproduce this issue on I+N (external hdmi port wires to dGPU) on DELL-Precision-7760. --- 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc27c980 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bf50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 三 31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: assertion 'width > 0' failed 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faf74004130 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce03b87330 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55cdffba6760 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc2f7df0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc23df40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Created gbm renderer for '/dev/dri/card1' 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create gbm_surface: Operation not permitted 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: GNOME Shell crashed with signal 5 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: == Stack trace for context 0x55cdfef5c180 == 三 31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to create fallback offscreen framebuffer: Failed to create texture 2d due to size/format constraint ... 三 31 10:57:56 ubuntu-Precision-7760 gnome-shell[5958]: Running GNOME Shell (using mutter 42.beta) as a Wayland display server --- Which also break the auto-login feature (after auto-login, gnome restart then screen back to gdm login shell) $ dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42~beta-1ubuntu2 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42~beta-1ubuntu2 amd64window manager library from the Mutter window manager ii mutter-common 42~beta-1ubuntu2 all shared files for the Mutter window manager Hi Daniel, Do you have a PPA could try your patch like this https://gitlab.gnome.org/vanvugt/mutter/-/commit/8354289650aa3ae0c531820d3a95251b627f9eb4 ? ** Changed in: oem-priority Status: New => 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Changed in: oem-priority Status: Confirmed => Fix Released -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966050] Re: [nvidia] Display content "overflows" when using fractional scaling
This issue comes from OEM partner which certifying with Ubuntu 20.04. We may still need to consider a fix in X for 20.04 or switching to X from gdm in 22.04. -- 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/1966050 Title: [nvidia] Display content "overflows" when using fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
ok, I arranged one machine to give it a try. I will share the result here later. BTW, I'm not able to check bug 1965246 -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Daniel, I tried it on my DELL XPS 9510 which is I+N platform but I didn't meet this issue on Jammy daily build (with dist-upgrade). Did you change anything? e.g. upgrade gnome-shell or mutter to 42 beta? ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Tested impish version ``` ubuntu-drivers-common: Installed: 1:0.9.2.4~0.21.10.1 ``` and the log shows ``` ... Takes 660ms to wait for nvidia udev rules completed. ``` thus, the result is PASS. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Tested focal version ``` ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.6 ``` and the log shows ``` ... Takes 640ms to wait for nvidia udev rules completed. ``` thus, the result is PASS. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
** Changed in: oem-priority Status: Triaged => Fix Released -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
Also submit MP to salsa https://salsa.debian.org/gnome-team/gdm/-/merge_requests/14 -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
This issue has been fixed in 510.54. For installed incorrect version, please see comment#16. ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Fix Released ** No longer affects: gdm3 (Ubuntu) -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
Report a bug as https://bugs.launchpad.net/oem-priority/+bug/1964747 -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
It seems a regression since https://launchpad.net/ubuntu/+source/nvidia- graphics-drivers-510/510.54-0ubuntu0.18.04.1 because of ``` * debian/templates/control.in: - Set XB-Support to PB (production branch). ``` Checking with maintainer on https://chat.canonical.com/canonical/pl/5bheikgti78qixw1jn9yjq16bc -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support PBheader, cannot determine support level Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid Support PBheader, cannot determine support level Mar 14 02:38:53 ubuntu ubiquity: Reading package lists... Mar 14 02:38:53 ubuntu ubiquity: Mar 14 02:38:53 ubuntu ubiquity: Building dependency tree... Mar 14 02:38:53 ubuntu ubiquity: Mar 14 02:38:53 ubuntu ubiquity: Reading state information... Mar 14 02:38:53 ubuntu ubiquity: Mar 14 02:38:53 ubuntu ubiquity: The following additional packages will be installed: Mar 14 02:38:53 ubuntu ubiquity: binutils binutils-common binutils-x86-64-linux-gnu libbinutils libctf-nobfd0 Mar 14 02:38:53 ubuntu ubiquity: libctf0 libnvidia-cfg1-470 libnvidia-common-470 libnvidia-compute-470 ... It looks like detected the nvidia-510 but choosing 470. -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
In daily build: kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 470.103.01 From comment#2: kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 510.39.01 In latest ubuntu archive: kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 510.54 This issue can be fixed if executing: sudo ubuntu-drivers install nvidia:510 Thus, the issue is be fixed by latest nvidia driver. We need to see whether the u-d-c didn't choose 510 in this case. (I did connect to internet during the instalaltion) $ ubuntu-drivers list WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid Support PBheader, cannot determine support level nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-510-server, (kernel modules provided by linux-modules-nvidia-510-server-generic-hwe-20.04) -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
Still could reproduce this issue with Jammy daily build (3/13) $ sha256sum ~/Downloads/jammy-desktop-amd64.iso 1c46933bf1837e6427f994676c60d54515c6ce011276dbfe4c5a63e427fdc2c5 /home/jeremysu/Downloads/jammy-desktop-amd64.iso 1. Install third-part drivers during the installation. 2. After installation, don't choose a mode specifically, it'll use X because of u-d-c patch. 3. sudo apt dist-upgrade 4. reboot with choosing to Wayland. 5. there is no output. -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
** Tags added: jiayi -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
** Tags added: jiayi -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
Hi Daniel, yes, in hybrid system, different BIOS have their own way to configure it. We just need to make sure the memory point of efifb passed from BIOS is correct one and it's correct in this case, the boot_vga is dGPU. I'll risk this issue on upstream to discuss and share the upstream bug here. -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Hi Seb, FWIK, the fix from gdm is not mandatory. The display-manager (inside u-d-c) will handle it. but if any flavor which doesn't use u-d-c then gdm upstream also provide this commit https://gitlab.gnome.org/GNOME/gdm/-/commit/ecbd9694458194e24f356ba9d37fc4f3a515c3dd#note_1402863 to fix this issue in GDM. Says, if no one from a flavor (which doesn't use u-d-c) reports this issue then we don't hurry to SRU gdm patches. -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
I did a review on the upstream MP that Daniel shared. It looks to me that the upstream intend to disable Wayland in many of scenarios. It contains a case: (proprietary nvidia) + (hybrid graphics) + (laptop) It make me feel curious that why only impact "hybrid laptop" but "hybrid desktop/workstation". In the other hand, that patch is also what Ubuntu needs to aware. It refers to https://download.nvidia.com/XFree86/Linux-x86_64/460.39/README/powermanagement.html for something like nvidia-hibernate (Wayland will be disabled if we doesn't enable them) -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
*** This bug is a duplicate of bug 1959888 *** https://bugs.launchpad.net/bugs/1959888 Hi Daniel, This issue is talking about I+N desktop. It may not same as a hybrid laptop. -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
Hi Daniel, The patch from comment#1 is from upstream. https://gitlab.gnome.org/GNOME/gdm/-/commit/dda2fbb175ca00fc4f6c4e3c149464a570e1dca4 -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Tags removed: gdm3 ** Tags added: nvidia -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach
** Tags added: nvidia-wayland -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach
** Attachment added: "journal-b.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701/+attachment/5565824/+files/journal-b.txt ** Tags added: oem-priority originate-from-1956556 sutton ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] [NEW] [NVIDIA][Wayland] graphic target not able to reach
Public bug reported: [Steps to reproduce] 1. Have an I+N desktop. 2. Attach monitor to dGPU (nvidia) 3. install jammy daily build with enable third-party (to install nvidia-510) 4. dist-upgrade 5. reboot the system and make sure the system starts with Wayland [Expected result] System launch gdm login screen without problem [Actual result] System stuck with blackscreen [Other information] $ systemctl list-jobs JOB UNIT TYPE STATE 140 system-getty.slice start waiting 2 multi-user.targetstart waiting 1 graphical.target start waiting 165 plymouth-quit-wait.service start running 8 setvtrgb.service start waiting 110 systemd-update-utmp-runlevel.service start waiting 6 jobs listed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 [modified: lib/udev/rules.d/61-gdm.rules] ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 5 00:15:24 2022 InstallationDate: Installed on 2022-01-20 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220109) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-03-04T20:36:36.997559 ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority originate-from-1956556 sutton -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
@Daniel, So for lp:#1959888, user confirmed it seems be fixed by nvidia-510. It makes sense on the patch. The patch from comment#1 is indeed enable Wayland only if nvidia-510. -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
** Summary changed: - [Wayland][Nvidia] gdm default use Xorg in 22.04 + [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04
** Description changed: + [Impact] + + * In Ubuntu 22.04, gdm should use Wayland by default even if proprietary nVidia driver is in use. + * gdm upstream prefers Wayland if nvidia version newer than (or equal) to 510. It same as Ubuntu's strategy[1]. + + [Test Plan] + + Steps: + 1. Download jammy daily build + 2. Install nvidia driver by selecting "install third-party packages.." during the installation. + 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. + + [Where problems could occur] + * If nVidia GPU doesn't support Wayland then it will be a problem but it doesn't means this patch leads a regression, instead, the problem should always there as it is if the user switches to Wayland mode no matter default mode. + * This ticket switches the default mode to Wayland. If there is a problem then user will encounter it after the installation which has bad experience. + * However, it's not regression because Jammy is a new LTS version and we decide to switch to Wayland. If a problem occurs, then we fix it. + + --- + [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland (at least with nvidia-510) [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: - Ubuntu Jammy should use Wayland as default with nVidia + [1] Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04
Test on my P350 with nvidia-510 on Jammy daily build with dist-upgrade. ** Patch added: "gdm.rules-Prefer-Wayland-with-NVIDIA-510.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1962523/+attachment/5564288/+files/gdm.rules-Prefer-Wayland-with-NVIDIA-510.debdiff ** Changed in: oem-priority Status: In Progress => Triaged -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04
** Description changed: [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] - gdm using wayland + gdm using wayland (at least with nvidia-510) [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: - Installed: 41.3-1ubuntu2 - Candidate: 41.3-1ubuntu2 - Version table: - *** 41.3-1ubuntu2 500 - 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 41.3-1ubuntu2 + Candidate: 41.3-1ubuntu2 + Version table: + *** 41.3-1ubuntu2 500 + 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 100 /var/lib/dpkg/status Reference: Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: Confirmed => In Progress -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] [NEW] [Wayland][Nvidia] gdm default use Xorg in 22.04
Public bug reported: [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Tags added: oem-priority -- 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/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Description changed:
[Impact]
- * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
- * After applying the fix, it got pass within 90 reboot cycles.
+ * After applying the fix, it got pass within 1000+ reboot cycles.
+ * Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
+
+ [Fix]
+ * The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
+ * Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
+ * gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
- * The patch checkes device/boot_vga with tag "master-of-seat". If a system
without any GPU as boot_vga then it will wait 10 seconds in the loop.
- * I tried to detach all monitors from the system and the boot_vga still
exist (default to use iGPU, the first device found during initialization)
- * I don't think they will a case which boot_vga doesn't exist in this moment
because:
- In drivers/gpu/vga/vgaarb.c (linux package)
- vga_arb_select_default_device() has a fallback function to determine the
boot_vga device to prevent firmware doesn't pass correct efifb to linux-kernel.
+ * there is not potential regression from my mind but it will lead the boot
time be longer.
+ * In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
+ * I think the stability is important than performance in this case.
+
+ [Other Info]
+ * For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
u-d-c for focal ** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562740/+files/0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
u-d-c for impish ** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562739/+files/0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
u-d-c patch for jammy ** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562733/+files/0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => jeremyszu (os369510) -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
yes, FWIK, we incline to provide the LTS branch (stable) for Ubuntu users. For some cutting edge graphic cards, which will use 495 (since 470 doesn't support) and the 495 will eventually upgrade to next LTS version (FWIK, 510) in the future. The installation logic is implemented in ubuntu-drivers-common. -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Changed in: oem-priority Status: In Progress => Confirmed -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Description changed:
[Impact]
* In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 90 reboot cycles.
[Where problems could occur]
* The patch checkes device/boot_vga with tag "master-of-seat". If a system
without any GPU as boot_vga then it will wait 10 seconds in the loop.
* I tried to detach all monitors from the system and the boot_vga still
exist (default to use iGPU, the first device found during initialization)
* I don't think they will a case which boot_vga doesn't exist in this moment
because:
In drivers/gpu/vga/vgaarb.c (linux package)
vga_arb_select_default_device() has a fallback function to determine the
boot_vga device to prevent firmware doesn't pass correct efifb to linux-kernel.
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
+ debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
+ upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
+
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
When I build the 536491641, I use meson build. When 1c9e4c93d, I use gbp buildpackage. Thus, I tried dh_quilt_patch then gbp buildpackage on 1c9e4c93d. The issue is gone. Based on above test, I think it's likely related to debian/rules. Something cause it (or has higher fail rate) happens. Also report the bug to debian mailing list. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131 ** Bug watch added: Debian Bug tracker #1004131 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131 -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
The issue is happening in debian/ubuntu only. Thus, I'm not sure the upstream is correct place to discuss instead of debian/ubuntu. This commit (536491641) works good. | * 1c9e4c93d (HEAD, refs/bisect/bad) New upstream release | * 4106a87d5 Update upstream source from tag 'upstream/41.0' | |\ | | * 5fcf89011 (debian/upstream/latest) New upstream version 41.0 | | |\ | | | * 536491641 (tag: 41.0, refs/bisect/good-536491641156ba88beab2c881278b09e52df6813) 41.0 The difference between 1c9e4c93d .. 536491641 that is only debian/* (we don't care .gitignore) -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
I tried the upstream gdm on focal (60 reboot cycles) and can not
reproduce the issue.
I'm trying jammy and could reproduce this issue.
Let me build upstream version on jammy.
** Description changed:
[Impact]
* In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
- count="$(cat /home/u/count)"
+ count="$(cat /home/ubuntu/count)"
count=$((count+1))
- echo $count | tee /home/u/count
+ echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 90 reboot cycles.
[Where problems could occur]
* The patch checkes device/boot_vga with tag "master-of-seat". If a system
without any GPU as boot_vga then it will wait 10 seconds in the loop.
* I tried to detach all monitors from the system and the boot_vga still
exist (default to use iGPU, the first device found during initialization)
* I don't think they will a case which boot_vga doesn't exist in this moment
because:
In drivers/gpu/vga/vgaarb.c (linux package)
vga_arb_select_default_device() has a fallback function to determine the
boot_vga device to prevent firmware doesn't pass correct efifb to linux-kernel.
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
