SUMMARY When painting with some brushes, there is a message "Accessing uninitialized random source" (which always happened) and now it also prints a backtrace. STEPS TO REPRODUCE Unfortunately I'm not sure, I only noticed it hours later in the console and then couldn't reproduce. OBSERVED RESULT Backtrace and message. EXPECTED RESULT No backtrace, no message. SOFTWARE/OS VERSIONS Krita Version: 5.0.0-prealpha (git 9e8cccc) Languages: pl, pl_PL, pl Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.0-58-generic Pretty Productname: Linux Mint 20.1 Product Type: linuxmint Product Version: 20.1 Desktop: X-Cinnamon ADDITIONAL INFORMATION Accessing uninitialized random source! "[" "0: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaglobal.so.17(kisBacktrace()+0x4a) [0x7ffff58dde0a]" "1: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(KisPaintInformation::randomSource() const+0x12c) [0x7ffff5c9201c]" "2: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritalibbrush.so.17(KisImagePipeBrush::prepareForSeqNo(KisPaintInformation const&, int)+0x209) [0x7ffff42553d9]" "3: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/kritaplugins/kritadefaultpaintops.so(+0x39123) [0x7fffd160e123]" "4: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/kritaplugins/kritadefaultpaintops.so(KisDabRenderingQueue::addDab(KisDabCacheUtils::DabRequestInfo const&, double, double)+0x7b) [0x7fffd161401b]" "5: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/kritaplugins/kritadefaultpaintops.so(KisDabRenderingExecutor::addDab(KisDabCacheUtils::DabRequestInfo const&, double, double)+0x36) [0x7fffd1616c66]" "6: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/kritaplugins/kritadefaultpaintops.so(+0x33843) [0x7fffd1608843]" "7: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x2338a0) [0x7ffff5c948a0]" "8: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/kritaplugins/kritadefaultpaintops.so(+0x36e29) [0x7fffd160be29]" "9: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x232988) [0x7ffff5c93988]" "10: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x232ae1) [0x7ffff5c93ae1]" "11: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x232ae1) [0x7ffff5c93ae1]" "12: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x232ae1) [0x7ffff5c93ae1]" "13: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x232ae1) [0x7ffff5c93ae1]" "14: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x232ae1) [0x7ffff5c93ae1]" "15: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(KisPaintOp::paintBezierCurve(KisPaintInformation const&, QPointF const&, QPointF const&, KisPaintInformation const&, KisDistanceInformation*)+0x4e) [0x7ffff5c93b4e]" "16: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(KisPainter::paintPainterPath(QPainterPath const&)+0x28f) [0x7ffff5c80e4f]" "17: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaui.so.17(KisMaskedFreehandStrokePainter::paintPainterPath(QPainterPath const&)+0x23) [0x7ffff6f1b153]" "18: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaui.so.17(FreehandStrokeStrategy::doStrokeCallback(KisStrokeJobData*)+0x3f4) [0x7ffff6f12234]" "19: /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.17(+0x1e2cc3) [0x7ffff5c43cc3]" "20: /lib/x86_64-linux-gnu/libQt5Core.so.5(+0xc1f82) [0x7ffff475bf82]" "21: /lib/x86_64-linux-gnu/libQt5Core.so.5(+0xbe9d2) [0x7ffff47589d2]" "22: /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7ffff25e8609]" "23: /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7ffff43cc293]" "]" ""
Have you seen this again since? Which brushes were you using?
I remember that Dmitry actually fixed this quite recently. *** This bug has been marked as a duplicate of bug 445775 ***