380288 2017-05-28 20:37:45 +0000 Systemsettings - "Erscheinungsbild" ... "Arbeitsbereich-Design" crashes when trying to open. 2017-06-02 02:28:24 +0000 1 1 2 Applications systemsettings general 5.8.6 Mint (Ubuntu based) Linux RESOLVED DUPLICATE 346519 drkonqi NOR crash --- 0 wolfganggosejacob plasma-bugs-null 0 oldest_to_newest 1678146 0 wolfganggosejacob 2017-05-28 20:37:45 +0000 Application: systemsettings5 (5.8.6) Qt Version: 5.6.1 Frameworks Version: 5.33.0 Operating System: Linux 4.4.0-53-generic x86_64 Distribution: Linux Mint 18.1 Serena -- Information about the crash: - using Mint 18.1 / 64 Bit - very fresh installation (2 hours - updates are installed) - no additional programs installed now I wanted to configure my system I was able to configure keyboard and mouse with success... => while changing to "Erscheinungsbild" ... "Arbeitsbereich-Design" the application crashed. (sorry, no english terms available) The application crashes every time after a new try. Almost all applications of this window will open without errors. => "Anzeige und Monitor" will also crash! - total TWO of all settings. I'll try next: reboot -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa035f75900 (LWP 10237))] Thread 4 (Thread 0x7f9ff6765700 (LWP 10428)): #0 0x00007fa03262bb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fa02f30f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fa02f30f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fa032f5337b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007fa032efbffa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fa032d249e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007fa0316806b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x00007fa032d29808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fa02f8306ba in start_thread (arg=0x7f9ff6765700) at pthread_create.c:333 #9 0x00007fa03263782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fa01a069700 (LWP 10241)): #0 0x00007fa02f30c41b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007fa02f30e8bb in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fa02f30f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fa02f30f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fa032f5337b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fa032efbffa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007fa032d249e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007fa0360c9515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x00007fa032d29808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007fa02f8306ba in start_thread (arg=0x7fa01a069700) at pthread_create.c:333 #10 0x00007fa03263782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa0228ba700 (LWP 10240)): #0 0x00007fa03262bb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fa0300a6c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007fa0300a88d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007fa025442d29 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007fa032d29808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fa02f8306ba in start_thread (arg=0x7fa0228ba700) at pthread_create.c:333 #6 0x00007fa03263782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa035f75900 (LWP 10237)): [KCrash Handler] #6 0x00007fa032566428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x00007fa03256802a in __GI_abort () at abort.c:89 #8 0x00007fa032d10f41 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007fa03191afe3 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x00007fa03192310a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007fa0319234f3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x00007fa033e52b25 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x00007fa031956d85 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x00007fa03442dafc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x00007fa034433036 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x00007fa032efe2a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007fa033e47fdd in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x00007fa033e48bcd in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x00007fa033e2678b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #20 0x00007fa025478d40 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x00007fa02f30f197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007fa02f30f3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x00007fa02f30f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x00007fa032f5335f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007fa032efbffa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007fa032f046bc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x000000000040c193 in ?? () #28 0x00007fa032551830 in __libc_start_main (main=0x40bd90, argc=1, argv=0x7ffe096341e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe096341d8) at ../csu/libc-start.c:291 #29 0x000000000040c209 in _start () Possible duplicates by query: bug 379578, bug 379557, bug 378589, bug 378240, bug 377996. Reported using DrKonqi 1678148 1 wolfganggosejacob 2017-05-28 21:05:08 +0000 a) AFTER a reboot the access to both applications was possible. b) an other application prevent to reboot by GUI. Sending an error-report wasn't possible because the application didn't have such function. reboot by console (# shutdown) It seems that the update needs a reboot. BUT I think I did a reboot after changing the display-driver from nvidia (open source) to the recommended one. There was a hint to do a reboot and I followed to complete the installation of the driver. perhaps he wanted a second one ;) 1678177 2 wolfganggosejacob 2017-05-29 06:52:20 +0000 Now I remember my decision about the reboot after installing the nvidia driver. I wanted to change some settings first and reboot afterwards. He wanted to make a reboot first to initialize the plugins. RESULT 1: --------- a) A warning after the driver installation should be presented, that the two plugins will fail if they should be used. (simple variant) b) System settings will lock "all" plugins which are affected by a elementary driver replacement. But I think this requires a (complex?) monitoring. (professional variant) RESULT 2: --------- It's my very first issue for bug-tracking. First I had to register to a new site which I don't know. I think it would be much more easier if new incidents could be parked in bugtracking-portal and the registration could be done later... OR the full registration could be done in the dialog box, which presents the fault. In this situation I havened had any mail-account on my computer and couldn't register from this fresh installed computer. Please report this point to anyone who is responsible to implement such a feature for == > new (bugtracking) users on fresh installed computers. Make the barrier smaller for new reporters. ;) My problem seems to be "solved". 1678927 3 cfeck 2017-06-02 02:28:24 +0000 *** This bug has been marked as a duplicate of bug 346519 ***