https://bugs.kde.org/show_bug.cgi?id=388469
--- Comment #3 from Micha <mic...@sutkowski.pl> --- michal@misutbook:~$ valgrind systemsettings5 ==22941== Memcheck, a memory error detector ==22941== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==22941== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==22941== Command: systemsettings5 ==22941== QObject::connect: invalid null parameter ==22941== Invalid read of size 8 ==22941== at 0x2E80A043: KScreen::GetConfigOperation::start() (in /usr/lib/x86_64-linux-gnu/libKF5Screen.so.5.12.80) ==22941== by 0x8516451: QObject::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x658646B: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1) ==22941== by 0x658DD33: QApplication::notify(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1) ==22941== by 0x84E6DE7: QCoreApplication::notifyInternal2(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x84E955C: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x853FE52: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0xEE51FB6: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5400.1) ==22941== by 0xEE521EF: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5400.1) ==22941== by 0xEE5227B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5400.1) ==22941== by 0x853F47E: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x84E4E39: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==22941== ==22941== ==22941== Process terminating with default action of signal 11 (SIGSEGV) ==22941== Access not within mapped region at address 0x0 ==22941== at 0x2E80A043: KScreen::GetConfigOperation::start() (in /usr/lib/x86_64-linux-gnu/libKF5Screen.so.5.12.80) ==22941== by 0x8516451: QObject::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x658646B: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1) ==22941== by 0x658DD33: QApplication::notify(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1) ==22941== by 0x84E6DE7: QCoreApplication::notifyInternal2(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x84E955C: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x853FE52: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0xEE51FB6: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5400.1) ==22941== by 0xEE521EF: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5400.1) ==22941== by 0xEE5227B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5400.1) ==22941== by 0x853F47E: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== by 0x84E4E39: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==22941== If you believe this happened as a result of a stack ==22941== overflow in your program's main thread (unlikely but ==22941== possible), you can try to increase the size of the ==22941== main thread stack using the --main-stacksize= flag. ==22941== The main thread stack size used in this run was 8388608. ==22941== ==22941== HEAP SUMMARY: ==22941== in use at exit: 5,212,575 bytes in 51,583 blocks ==22941== total heap usage: 301,685 allocs, 250,102 frees, 55,757,021 bytes allocated ==22941== ==22941== LEAK SUMMARY: ==22941== definitely lost: 4,352 bytes in 17 blocks ==22941== indirectly lost: 1,377 bytes in 65 blocks ==22941== possibly lost: 15,487 bytes in 193 blocks ==22941== still reachable: 5,191,359 bytes in 51,308 blocks ==22941== of which reachable via heuristic: ==22941== newarray : 5,456 bytes in 32 blocks ==22941== multipleinheritance: 65,928 bytes in 83 blocks ==22941== suppressed: 0 bytes in 0 blocks ==22941== Rerun with --leak-check=full to see details of leaked memory ==22941== ==22941== For counts of detected and suppressed errors, rerun with: -v ==22941== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
