 some people are getting the crash with realloc(): invalid next size. I guess that bug can be marked duplicate?
[10:15] <RikMills> BTW, as far as I can tell this was all started by mesa being bumped from 20.3.4 to 21.0.0
[12:32] <RikMills> also the gtk front end works fine. only the pyqt/kde front end crashes
[12:33] <mitya57> If it's related to mesa, then maybe it's something with the llvmpipe renderer.
[12:34] <RikMills> just realiesd I haven't linked the bug
[12:34] <mitya57> In any case I recommend you to obtain a stacktrace from valgrind or gdb with symbols.
[12:34] <RikMills> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1920665
[12:35] <RikMills> mitya57: yes, I think llvmpipe also, as it doesn't happen on my intel laptop run with full graphics support, but does if I run in low graphics mode
[12:40] <RikMills> mitya57: just setting up a VM with the symbols. I ran out of time to get to it yesterday
 https://matterbridge.lubuntu.me/a233a1da/file_2179.jpg
 That is what I get
 @RikMills What about gdb? Or valgrind without PYTHONMALLOC?
 I am just pastebinning the output without
 https://paste.ubuntu.com/p/gGJVX28pwx/ (re @mitya57: @RikMills What about gdb? Or valgrind without PYTHONMALLOC?)
 Still not much helpful :(
 Maybe try gdb because it at least prints the arguments, which may contain information about what Python code is executed.
 Also can you try running python3 -X faulthandler /usr/bin/ubiquity?
 what would the gdb command be?
 Forwarded from mitya57: gdb python3, then run /usr/bin/ubiquity (or whatever its name is)
 ubiquity needs sudo so that is not working
 or gain perms with pexec
 https://matterbridge.lubuntu.me/2338dc0c/file_2180.jpg
 sudo gdb python3?
 I tried that. One sec
 https://matterbridge.lubuntu.me/bbed2fe0/file_2181.jpg
 Oh, forks
 No ideas 😢
 Ok. Thanks all the same :)
 Maybe add prints and find which line or import causes the error?
 Mesa 21.0.1 bugfix is supposed to be out today, so I may try building that 1st (re @mitya57: Maybe add prints and find which line or import causes the error?)
 But yes, I have done that previously for something I forget
 Makes sense
 I am also not sure that having glibc with new patches stuck in proposed which mesa built with is not a problem
 Hmmm. maybe try updating my VM to proposed....
 Nope. That does not help
 Giving up for a bit. Thanks!