[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad
I've set up a dual Nvidia system and cannot reproduce any crashes.
The second Nvidia card fails to display anything if a monitor is
attached but that's basically the same as bug 1978905, and the same
experimental patch
(https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3416) mostly
fixes that
Setting to low because high-end Nvidia datacenter hardware should be
using Xorg instead for the foreseeable future.
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter
Private bug 2016299 now has more complete stack traces.
--
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/2015386
Title:
NVIDIA quad-GPU system crashes starting Wayland session
To man
Bug 2016299 is a little helpful but strange it couldn't retrace beyond:
StacktraceTop:
__strlen_avx2_rtm () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
_mesa_hash_string (_key=0x0) at ../src/util/hash_table.c:662
_mesa_hash_table_search (ht=0x55b6f40fefe0, key=0x0) at
../src/util/hash_tabl
** Tags added: nvidia-wayland
--
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/2015386
Title:
NVIDIA quad-GPU system crashes starting Wayland session
To manage notifications about th
The .crash file from comment 11 has been submitted via ubuntu-bug in bug
2016299 - I'll leave it to the developers to determine which one should
be the dupe.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bug
Comment #11 is still the same as comment #3:
#0 __pthread_kill_implementation (no_tid=0, signo=11,
threadid=140206817158592) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=11, threadid=140206817158592) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=140206817158592
