[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
Same when using DisplayLink adapter via both EVDI or UDL. Crashes most of the times when GPU file (/dev/dri/cardX) is created. Gnome logs: dladmin-XPS-13-9360 gnome-shell[3367]: St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) dladmin-XPS-13-9360 gnome-shell[3367]: Bail out! St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) dladmin-XPS-13-9360 gnome-shell[3367]: GNOME Shell crashed with signal 6 dladmin-XPS-13-9360 gnome-shell[3367]: == Stack trace for context 0x55b2530dd150 == dladmin-XPS-13-9360 gnome-shell[3367]: #0 55b2549ae9d8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:206 (2d1dccd7c880 @ 142) dladmin-XPS-13-9360 gnome-shell[3367]: #1 55b2549ae950 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:124 (2d1dccd7ca10 @ 12) dladmin-XPS-13-9360 gnome-shell[3367]: #2 7ffe81569ef0 b resource:///org/gnome/shell/ui/background.js:695 (1caa9dce13d0 @ 155) dladmin-XPS-13-9360 gnome-shell[3367]: #3 7ffe81569fb0 b resource:///org/gnome/shell/ui/layout.js:471 (1caa9dce06a0 @ 74) dladmin-XPS-13-9360 gnome-shell[3367]: #4 55b2549ae8b8 i resource:///org/gnome/shell/ui/layout.js:541 (1caa9dce04c0 @ 62) dladmin-XPS-13-9360 gnome-shell[3367]: #5 7ffe8156aa80 I self-hosted:850 (341e9140a600 @ 423) GDB backtrace attached. ** Attachment added: "gdb backtrace" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+attachment/5427820/+files/backtrace.log -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
Fix in Xorg: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/447#note_515426 -- 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/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
Adding movie depicting the problem. And it happens without actually moving the mouse, after dragging the window. ** Attachment added: "IMG_1245.MOV" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870512/+attachment/5375562/+files/IMG_1245.MOV -- 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/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
Fair point, but question is if it's software cursor from Xserver's perspective. NVidia driver might be blending the cursor in, while "emulating HW cursor" on the Xorg's end, right? -- 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/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
A recording would preferably be better, a screenshot might not give the full picture. Anyway, sure, I shall post it. The case I'm describing is more extreme, the squares are way bigger and flickering constantly, most of the time effectively preventing usage of the machine, such messy it gets. Plus, is the other user also using SW cursor? In the case described here it's related purely to that. -- 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/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
I guess the bug on Xorg's end is pretty self-explanatory: https://gitlab.freedesktop.org/xorg/xserver/-/issues/828 The fix for Xorg's has been smoked-tested recently, seems to be working fine. ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #828 https://gitlab.freedesktop.org/xorg/xserver/-/issues/828 -- 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/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874818] Re: Please pull Mutter/Wayland fixes for desktop freeze
Tested on Dell XPS13 (Intel GPU) and Precision M3800 (Intel/Nvidia-nouveau), with evdi-backed displays mostly focusing on enabling/disabling screens, both by system settings as well as ACPI events (lid closing/opening). Looks fine so far. -- 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/1874818 Title: Please pull Mutter/Wayland fixes for desktop freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873401] Re: Gnome Shell lock-up on GPU hotplug
Consulted the bug on #gnome-shell IRC. Next step is to track down the event that actually triggers execution of cogl_glib_source_dispatch. It's possible it simply does not arrive. BTW, this does not rule out Xorg as potential culprit, it might be simply not delivering the expected event. This is yet to be checked. -- 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/1873401 Title: Gnome Shell lock-up on GPU hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873401] Re: xorg lock-up on GPU hotplug
OK, I'm totally sure it's a freeze. Moreover, gnome-shell stack trace looks normal, event loop runs just fine. I can generate and provide core file if needed. What I managed to debug so far, is that in case of multiple /dev/dri/cardX being created frame_cb in meta-stage-x11.c:296 is not called which simply results in the screen being stalled. Debugging it up the stack trace leads to conclusion, that cogl_glib_source_dispatch in cogl-glib-source.c:133 is not called at all for some reason. Natural assumption would be to track that function down, unless there's sth more you can recommend me? -- 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/1873401 Title: xorg lock-up on GPU hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873401] Re: xorg lock-up on GPU hotplug
Point is, there is no crash file. Graphical environment is not responsive, but nothing seems to have crashed. If there's a stacktrace or core file needed, no problem, I can rebuild in debug mode, attach debugger and gather those. -- 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/1873401 Title: xorg lock-up on GPU hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
