Description of problem: After installing the nvidia340 driver using MCC/Hardware and returning to the desktop, none of the Plasma GUI "leave" options are at all responsive. I was able to leave using the "shutdown now" command in konsole. Subsequent boots using the nvidia340 driver (after manually adding the "nokmsboot" kernel option) do not show the problem. This problem may be present in 32-bit installs as well, but I do not have a current way to test this. First noted with the sta2 Classical isos, as those have been the only isos used to put a Cauldron install on this hardware. Just as a point of information, the Mageia Classical installer always chooses the server kernel for this hardware, because the BIOS erroneously reports that ECC memory is installed.
This could be a duplicate of bug 20119. I assume you installed the nvidia340 driver the first time you booted into your new install, correct? If so, then please attach journal.txt that is the result of running, as root: journalctl -ab1 > journal.txt
Assignee: bugsquad => kdeComponent: Installer => RPM PackagesCC: (none) => mageiatools, marja11
I probably should have taken notes. I'm not sure now whether I did this on the first boot or not. I think so, this time. However, I have seen this behavior after installing from earlier isos, when I didn't install the nvidia driver on the first boot, but afterward. Each time, I saw it only in the same session when I installed the driver, no matter which one that was. I will see if I can find the journal where this happened, and attach it.
Created attachment 8879 [details] Journal from first boot after install Yes, it WAS the first boot. I did do a lot of stuff before installing the driver, and as I recall I attempted the reboot right after installing it.
I am quite willing to do another install and try this again, this time not installing the driver until the second boot. Just let me know, and give me a few hours to arrange to do it.
(In reply to Thomas Andrews from comment #4) > I am quite willing to do another install and try this again, this time not > installing the driver until the second boot. Just let me know, and give me a > few hours to arrange to do it. It's confusing. I do see 3 plasmashell "TypeErrors" and 74 such errors: [marja@localhost Downloads]$ grep 'QXcbConnection: XCB error: 3 (BadWindow)' 20153journal | wc -l 74 [marja@localhost Downloads]$ (btw, Herman's journal output of bug 20119 shows that error 49 times) However, non of those errors are near when you install the nvidia340 driver. @ Thomas Yeah, it would be nice if you could run updates and do everything else like you're used to in the first boot, except installing the driver, which will be done after booting the 2nd time. I'm very curious when you hit this bug, then.
OK. I've done another install. Things didn't go quite as planned, but I think I have everything here. Install went OK. Tried to set up my usual mirror, but that failed, probably because it was re-syncing. So, I removed that one and went with an alternative. Got updates, which included a new kernel, so I would have rebooted before installing the 340 driver, anyway. I checked each closing option before actually doing so, and it closed OK. There was a delay before the next boot, and when I got there and checked for updates again there were several, including plasma-workspace. On the off chance that it might make a difference, I rebooted once more. this time I went after the nvidia driver. It seemed to install without incident. I closed MCC, and tried it again from the panel icon, and it worked. Closed it again, and tried to leave. Got a message that the ksmserver-logout-greeter had closed unexpectedly. I sent the information from kcrash to a file, and will be attaching it here. BTW, on the fourth boot, the first with the nvidia driver, I checked, and "nokmsboot" had not been added to the kernel options. I added it manually.
Created attachment 8887 [details] Journal from the first boot after a new install.
Created attachment 8888 [details] Journal from the second boot Updates included plasma-workspace, so I did another boot.
Created attachment 8889 [details] Journal from the third boot. This is the boot where the nvidia driver was installed, and where I run into the bug.
Created attachment 8890 [details] file created by kcrash
Still valid as of a half hour ago, but not just when the driver is installed. Problems with kernel and dkms update builds resulted in a boot where the system dropped back into nouveau. Subsequent boots continued to use nouveau, even after the build problems had been corrected, until I used MCC/Hardware/Set up the graphics" to re-select the proprietary nvidia340 driver. No software was downloaded and installed, but there was a period of hard drive activity before getting notice that the process had completed. Upon leaving MCC to reboot, the "Leave" function did not work. I received an error message similar to (may not have letter cases correct) "KSMserver-logout-greeter closed unexpectedly," with a bug-shaped icon. Another bug-shaped icon appeared in the taskbar. I used "reboot" in Konsole to do the reboot, and things seemed to work OK after that.
I think here are two separate bugs. For the Nvidia, do you think it is this: https://bugs.mageia.org/show_bug.cgi?id=20604 ? As for the Plasma logout options not working after update, i have seen that several times and i think also when neither kernel nor graphics driver got updated. Lazily, I never dug into the logs, just issued "reboot" in a console.
CC: (none) => fri
(In reply to Morgan Leijström from comment #12) > I think here are two separate bugs. > > For the Nvidia, do you think it is this: > https://bugs.mageia.org/show_bug.cgi?id=20604 ? I agree. I should have referenced that bug, but didn't. I only mentioned it to explain why I was there again, choosing the proprietary driver, again. The situation from Bug 20604 appears to be resolved, at least on my system. > > As for the Plasma logout options not working after update, i have seen that > several times and i think also when neither kernel nor graphics driver got > updated. Lazily, I never dug into the logs, just issued "reboot" in a > console. The problem is, users who don't know to do that aren't going to be very happy with the situation, and are going to wonder about stability elsewhere. It should be fixed, preferably before we release the RC.
Do you have an idea about what specifically triggers this? To me it seems to do with plasma updates but that is just an impression I have had it more times on the workstation where i use nvidia-current, than on my laptops with 340 (but i also update workstation more frequently) And it happens without using MCC, and without changing driver, and also when nvidia still works afterwards (it do not not change to nouveau).
No idea. So far, I've only seen it under the conditions I reported, at least as of Plasma 5.8.x. I don't THINK I saw it with earlier Plasmas, but I can't remember for sure. Now that I think of it, I did see something similar when testing the Mageia5 isos, when trying to leave the first boot, but I doubt it's the same thing.
I now found it need no plasma/KDE updates to fail logging out Now in my workstation - which yesterday falled back to nouveau after update then - now updated to kernel 4.9.20-2 and then in MCC selected the nvidia-latest. Then clicking the menu to logout makes a window popup saying ksmserver-logout-greeter died. Information from that window (i have gdb installed): Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5a6dfab840 (LWP 22897))] Thread 4 (Thread 0x7f5a62f21700 (LWP 22900)): #0 0x00007f5a7d1ee52a in idleTimerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #1 0x00007f5a774d121d in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x00007f5a774d1b93 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x00007f5a774d1d6c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x00007f5a7d1eee1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #5 0x00007f5a7d19a48a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #6 0x00007f5a7cfd43bc in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x00007f5a7e719915 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x00007f5a7cfd8ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x00007f5a779f466d in start_thread () at /lib64/libpthread.so.0 #10 0x00007f5a7c8f1e4d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f5a63722700 (LWP 22899)): #0 0x00007f5a7c8e600d in poll () at /lib64/libc.so.6 #1 0x00007f5a774d1c64 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x00007f5a774d1d6c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x00007f5a7d1eee1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #4 0x00007f5a7d19a48a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #5 0x00007f5a7cfd43bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x00007f5a80040635 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x00007f5a7cfd8ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x00007f5a779f466d in start_thread () at /lib64/libpthread.so.0 #9 0x00007f5a7c8f1e4d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f5a68eca700 (LWP 22898)): #0 0x00007f5a7c8e600d in poll () at /lib64/libc.so.6 #1 0x00007f5a78256902 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00007f5a78258657 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x00007f5a6b572be9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x00007f5a7cfd8ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x00007f5a779f466d in start_thread () at /lib64/libpthread.so.0 #6 0x00007f5a7c8f1e4d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f5a6dfab840 (LWP 22897)): [KCrash Handler] #6 0x00007f5a7c82f818 in raise () at /lib64/libc.so.6 #7 0x00007f5a7c830f2a in abort () at /lib64/libc.so.6 #8 0x00007f5a7cfc0f6e in () at /lib64/libQt5Core.so.5 #9 0x00007f5a7ebdb5cb in () at /lib64/libQt5Quick.so.5 #10 0x00007f5a7ebe31ba in QSGThreadedRenderLoop::handleExposure(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #11 0x00007f5a7ebe359b in QSGThreadedRenderLoop::exposureChanged(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #12 0x00007f5a7d4e9e7b in QWindow::event(QEvent*) () at /lib64/libQt5Gui.so.5 #13 0x00007f5a7ec150c5 in QQuickWindow::event(QEvent*) () at /lib64/libQt5Quick.so.5 #14 0x0000000000408901 in KSMShutdownDlg::event(QEvent*) () #15 0x00007f5a7daaed0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #16 0x00007f5a7dab3e76 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #17 0x00007f5a7d19c618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #18 0x00007f5a7d4df9c7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /lib64/libQt5Gui.so.5 #19 0x00007f5a7d4e04cd in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib64/libQt5Gui.so.5 #20 0x00007f5a7d4bf72b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Gui.so.5 #21 0x00007f5a6b5a7d90 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #22 0x00007f5a774d1a97 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #23 0x00007f5a774d1cc8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #24 0x00007f5a774d1d6c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #25 0x00007f5a7d1eedf6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #26 0x00007f5a7d19a48a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #27 0x00007f5a7d1a27d1 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #28 0x0000000000405c7f in main ()
Please install the debug packages and paste a new backtrace
CC: (none) => mageia
I have recently seen the non-functioning leave option in a VM during multiple upgrade tests from 5 to 6 (KDE -> Plasma) using urpmi (net upgrade). After upgrade is completed no GUI method to reboot works, but there is no problem from root tty (or terminal iirc).
CC: (none) => zen25000
(In reply to Nicolas Lécureuil from comment #17) > Please install the debug packages and paste a new backtrace What packages are they?
ksmserver-logout-greeter is part of package plasma-workspace, so i will install plasma-workspace-debuginfo (from the repo core debug), and try to reproduce.
Done :) First i made full update, not much since yesterday, but incl new plasma-workspace, and installed plasma-workspace-debuginfo. No new nvidia nor kernel since last boot, and not tried changing to nvidia. -> Reboot using menu worked. Now after reboot In MCC I selected default NVIDIA Geforce 420 series and later, priprietary driver. Now (not rebooted yet) I again tried to reboot by menu, but now the dialog about crashed ksmserver-logout-greeter shows up. In it I select (drop down button at bottom of dialog) to debug by gdb, and issue reboot again, and in dialog tab "Developer information" it say the crash information is useable, and list: Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f58194a7840 (LWP 4993))] Thread 4 (Thread 0x7f581247e700 (LWP 4996)): #0 0x00007f58229ccc40 in g_main_context_acquire () at /lib64/libglib-2.0.so.0 #1 0x00007f58229cdb35 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x00007f58229cdd6c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x00007f58286eae1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #4 0x00007f582869648a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #5 0x00007f58284d03bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x00007f5829c15915 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x00007f58284d4ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x00007f5822ef066d in start_thread () at /lib64/libpthread.so.0 #9 0x00007f5827dede4d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f5812c7f700 (LWP 4995)): #0 0x00007f5827de200d in poll () at /lib64/libc.so.6 #1 0x00007f58229cdc64 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x00007f58229cdd6c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x00007f58286eae1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #4 0x00007f582869648a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #5 0x00007f58284d03bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x00007f582b53c635 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x00007f58284d4ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x00007f5822ef066d in start_thread () at /lib64/libpthread.so.0 #9 0x00007f5827dede4d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f58143c6700 (LWP 4994)): #0 0x00007f5827de200d in poll () at /lib64/libc.so.6 #1 0x00007f5823752902 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00007f5823754657 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x00007f5816a6ebe9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x00007f58284d4ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x00007f5822ef066d in start_thread () at /lib64/libpthread.so.0 #6 0x00007f5827dede4d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f58194a7840 (LWP 4993)): [KCrash Handler] #6 0x00007f5827d2b818 in raise () at /lib64/libc.so.6 #7 0x00007f5827d2cf2a in abort () at /lib64/libc.so.6 #8 0x00007f58284bcf6e in () at /lib64/libQt5Core.so.5 #9 0x00007f582a0d75cb in () at /lib64/libQt5Quick.so.5 #10 0x00007f582a0df1ba in QSGThreadedRenderLoop::handleExposure(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #11 0x00007f582a0df59b in QSGThreadedRenderLoop::exposureChanged(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #12 0x00007f58289e5e7b in QWindow::event(QEvent*) () at /lib64/libQt5Gui.so.5 #13 0x00007f582a1110c5 in QQuickWindow::event(QEvent*) () at /lib64/libQt5Quick.so.5 #14 0x0000000000408901 in KSMShutdownDlg::event(QEvent*) (this=0x1319410, e=0x7ffc41d8bb30) at /usr/src/debug/plasma-workspace-5.8.6/ksmserver/shutdowndlg.cpp:231 #15 0x00007f5828faad0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #16 0x00007f5828fafe76 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #17 0x00007f5828698618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #18 0x00007f58289db9c7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /lib64/libQt5Gui.so.5 #19 0x00007f58289dc4cd in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib64/libQt5Gui.so.5 #20 0x00007f58289bb72b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Gui.so.5 #21 0x00007f5816aa3d90 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #22 0x00007f58229cda97 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #23 0x00007f58229cdcc8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #24 0x00007f58229cdd6c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #25 0x00007f58286eadf6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #26 0x00007f582869648a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #27 0x00007f582869e7d1 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #28 0x0000000000405c7f in main(int, char**) (argc=6, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.8.6/ksmserver/logout-greeter/main.cpp:221
#6 0x00007f5827d2b818 in raise () at /lib64/libc.so.6 #7 0x00007f5827d2cf2a in abort () at /lib64/libc.so.6 #8 0x00007f58284bcf6e in () at /lib64/libQt5Core.so.5 #9 0x00007f582a0d75cb in () at /lib64/libQt5Quick.so.5 #10 0x00007f582a0df1ba in QSGThreadedRenderLoop::handleExposure(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #11 0x00007f582a0df59b in QSGThreadedRenderLoop::exposureChanged(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #12 0x00007f58289e5e7b in QWindow::event(QEvent*) () at /lib64/libQt5Gui.so.5 Please install the needed debuginfo packages too
(Also note that it always during the last days: after i have selected to use nvidia proprietary driver using MCC, at next boot it fall back to nouveau. So i guess what triggers the problem is some nvidia driver install problem - but user should be able lo log out anyway!) I installed debuginfo for all .so. files...: libc.so.6 & libthread_db.so.1 -> glibc-debuginfo libQt5Core.so.5 & libQt5Gui.so.5 -> qtbase5-debuginfo libQt5Quick.so.5 -> qtdeclarative5-debuginfo libglib-2.0.so.0 -> glib2.0-debuginfo libxcb.so.1 -> libxcb-debuginfo ...except there is no debuginfo package for neither /usr/lib64/nvidia-current/libGL.so.1 /usr/lib64/nvidia-current/tls/libnvidia-tls.so.375.39 Result: it got three stars about usefulness, and the report is: Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f3381bc7840 (LWP 5246))] Thread 4 (Thread 0x7f3376b11700 (LWP 5252)): #0 0x00007f338b6189dc in __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x00007f338b612ab6 in __GI___pthread_mutex_lock (mutex=0x7f338a9ce470) at ../nptl/pthread_mutex_lock.c:116 #2 0x00007f338a749e7c in () at /usr/lib64/nvidia-current/libGL.so.1 #3 0x00007f338a74edb1 in () at /usr/lib64/nvidia-current/libGL.so.1 #4 0x00007f338a74f2c8 in () at /usr/lib64/nvidia-current/libGL.so.1 #5 0x00007f3385dcb102 in () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.375.39 #6 0x00007f338b131790 in read (__nbytes=16, __buf=0x7f3376b10b80, __fd=<optimized out>) at /usr/include/bits/unistd.h:44 #7 0x00007f338b131790 in g_wakeup_acknowledge (wakeup=0x7f33700025a0) at gwakeup.c:210 #8 0x00007f338b0ed76e in g_main_context_check (context=context@entry=0x7f33680009b0, max_priority=2147483647, fds=fds@entry=0x7f3368002e70, n_fds=n_fds@entry=1) at gmain.c:3707 #9 0x00007f338b0edc08 in g_main_context_iterate (context=context@entry=0x7f33680009b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3926 #10 0x00007f338b0edd6c in g_main_context_iteration (context=0x7f33680009b0, may_block=may_block@entry=1) at gmain.c:3990 #11 0x00007f3390e0ae1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7f33680008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #12 0x00007f3390db648a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f3376b10d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #13 0x00007f3390bf03bc in QThread::exec() (this=this@entry=0x147f820) at thread/qthread.cpp:500 #14 0x00007f3392335915 in QQmlThreadPrivate::run() (this=0x147f820) at qml/ftw/qqmlthread.cpp:141 #15 0x00007f3390bf4ff9 in QThreadPrivate::start(void*) (arg=0x147f820) at thread/qthread_unix.cpp:365 #16 0x00007f338b61066d in start_thread (arg=0x7f3376b11700) at pthread_create.c:334 #17 0x00007f339050de4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f3377312700 (LWP 5251)): #0 0x00007f339050200d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f338b0edc64 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f3370019270, timeout=<optimized out>, context=0x7f33700009b0) at gmain.c:4228 #2 0x00007f338b0edc64 in g_main_context_iterate (context=context@entry=0x7f33700009b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3924 #3 0x00007f338b0edd6c in g_main_context_iteration (context=0x7f33700009b0, may_block=may_block@entry=1) at gmain.c:3990 #4 0x00007f3390e0ae1b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7f33700008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x00007f3390db648a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f3377311d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #6 0x00007f3390bf03bc in QThread::exec() (this=this@entry=0x7f3393ccdd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #7 0x00007f3393c5c635 in QDBusConnectionManager::run() (this=0x7f3393ccdd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #8 0x00007f3390bf4ff9 in QThreadPrivate::start(void*) (arg=0x7f3393ccdd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:365 #9 0x00007f338b61066d in start_thread (arg=0x7f3377312700) at pthread_create.c:334 #10 0x00007f339050de4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f337cae6700 (LWP 5247)): #0 0x00007f339050200d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f338be72902 in poll (__timeout=-1, __nfds=1, __fds=0x7f337cae5c90) at /usr/include/bits/poll2.h:46 #2 0x00007f338be72902 in _xcb_conn_wait (c=c@entry=0x141cc80, cond=cond@entry=0x141ccc0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479 #3 0x00007f338be74657 in xcb_wait_for_event (c=0x141cc80) at xcb_in.c:693 #4 0x00007f337f18ebe9 in QXcbEventReader::run() (this=0x142fc70) at qxcbconnection.cpp:1331 #5 0x00007f3390bf4ff9 in QThreadPrivate::start(void*) (arg=0x142fc70) at thread/qthread_unix.cpp:365 #6 0x00007f338b61066d in start_thread (arg=0x7f337cae6700) at pthread_create.c:334 #7 0x00007f339050de4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f3381bc7840 (LWP 5246)): [KCrash Handler] #6 0x00007f339044b818 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x00007f339044cf2a in __GI_abort () at abort.c:89 #8 0x00007f3390bdcf6e in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1648 #9 0x00007f3390bdcf6e in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffd52ec6400, msg=msg@entry=0x7f339297c1c5 "%s") at global/qlogging.cpp:790 #10 0x00007f33927f75cb in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) (this=this@entry=0x147efa0, window=0x148f570, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:262 #11 0x00007f33927ff1ba in QSGThreadedRenderLoop::handleExposure(QQuickWindow*) (this=this@entry=0x147efa0, window=window@entry=0x148f570) at scenegraph/qsgthreadedrenderloop.cpp:946 #12 0x00007f33927ff59b in QSGThreadedRenderLoop::exposureChanged(QQuickWindow*) (this=0x147efa0, window=0x148f570) at scenegraph/qsgthreadedrenderloop.cpp:884 #13 0x00007f3391105e7b in QWindow::event(QEvent*) (this=this@entry=0x148f570, ev=ev@entry=0x7ffd52ec6820) at kernel/qwindow.cpp:2098 #14 0x00007f33928310c5 in QQuickWindow::event(QEvent*) (this=this@entry=0x148f570, e=e@entry=0x7ffd52ec6820) at items/qquickwindow.cpp:1492 #15 0x0000000000408901 in KSMShutdownDlg::event(QEvent*) (this=0x148f570, e=0x7ffd52ec6820) at /usr/src/debug/plasma-workspace-5.8.6/ksmserver/shutdowndlg.cpp:231 #16 0x00007f33916cad0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x148f570, e=0x7ffd52ec6820) at kernel/qapplication.cpp:3804 #17 0x00007f33916cfe76 in QApplication::notify(QObject*, QEvent*) (this=0x7ffd52ec6b90, receiver=0x148f570, e=0x7ffd52ec6820) at kernel/qapplication.cpp:3561 #18 0x00007f3390db8618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=receiver@entry=0x148f570, event=event@entry=0x7ffd52ec6820) at kernel/qcoreapplication.cpp:1015 #19 0x00007f33910fb9c7 in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (event=0x7ffd52ec6820, receiver=0x148f570) at ../../src/corelib/kernel/qcoreapplication.h:228 #20 0x00007f33910fb9c7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) (e=0x1699900) at kernel/qguiapplication.cpp:2741 #21 0x00007f33910fc4cd in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) (e=<optimized out>) at kernel/qguiapplication.cpp:1723 #22 0x00007f33910db72b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) (flags=...) at kernel/qwindowsysteminterface.cpp:653 #23 0x00007f337f1c3d90 in userEventSourceDispatch(GSource*, GSourceFunc, gpointer) (source=<optimized out>) at eventdispatchers/qeventdispatcher_glib.cpp:70 #24 0x00007f338b0eda97 in g_main_dispatch (context=0x7f3378001710) at gmain.c:3203 #25 0x00007f338b0eda97 in g_main_context_dispatch (context=context@entry=0x7f3378001710) at gmain.c:3856 #26 0x00007f338b0edcc8 in g_main_context_iterate (context=context@entry=0x7f3378001710, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3929 #27 0x00007f338b0edd6c in g_main_context_iteration (context=0x7f3378001710, may_block=may_block@entry=1) at gmain.c:3990 #28 0x00007f3390e0adf6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x146a520, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #29 0x00007f3390db648a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffd52ec6ad0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #30 0x00007f3390dbe7d1 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1285 #31 0x00007f33910f28ec in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1607 #32 0x00007f33916c7f15 in QApplication::exec() () at kernel/qapplication.cpp:2979 #33 0x0000000000405c7f in main(int, char**) (argc=6, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.8.6/ksmserver/logout-greeter/main.cpp:221
Strange, it seems it first need to fail and revert to nouveau on boot, then after setting it again to nvidia it fail logging out. I also found that while nvidia was working on kernel 4.9.14, it does not after being selected again if it was running that kernel... https://bugs.mageia.org/show_bug.cgi?id=20604#c18
After installing the full Plasma 5.12.2 update, the problem described when I opened this bug has disappeared. Before, all I had to do to trigger this bug was to go to MCC/Hardware/ Set up the graphical server, then select the driver to trigger the question about whether I wanted to use the proprietary driver. A "Yes" answer did not (apparently) trigger the installation of anything. But when I attempted a reboot or shutdown, the "leave" buttons would not work. I just tried it again, after updating Plasma, and as I said, the original problem has disappeared. Thinking of marking it as resolved, but I'm thinking perhaps confirmation from another user would be a good idea first.
Version: Cauldron => 6
It's back. After installing the new drakxtools for testing, I told the system to switch from the nvidia340 driver to nouveau. "Leave" would not work, and I rebooted using the "reboot" command. After the reboot, I switched back to the nvidia340 driver, and again I had to use the reboot command.
I think i see this after having updated kernel - On my workstation which use nvidia-current driver.
CC: (none) => heninj
Now i experienced this after having updated the nividia driver only ( https://bugs.mageia.org/show_bug.cgi?id=23490#c4 ) I then opened konsole, become root, and issued journalctl -f , and tried again. The following is the output: aug 28 10:33:31 svarten ksmserver-logout-greeter[30441]: QGLXContext: Failed to create dummy context aug 28 10:33:31 svarten ksmserver-logout-greeter[30441]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:31: ReferenceError: model is not defined aug 28 10:33:31 svarten kernel: NVRM: API mismatch: the client has the version 390.87, but NVRM: this kernel module has the version 390.77. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. aug 28 10:33:31 svarten kernel: NVRM: API mismatch: the client has the version 390.87, but NVRM: this kernel module has the version 390.77. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. aug 28 10:33:31 svarten ksmserver-logout-greeter[30441]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) aug 28 10:33:31 svarten audit[30441]: ANOM_ABEND auid=4294967295 uid=10702 gid=10790 ses=4294967295 pid=30441 comm="ksmserver-logou" exe="/usr/libexec/ksmserver-logout-greeter" sig=6 res=1 aug 28 10:33:32 svarten kernel: audit: type=1701 audit(1535445211.816:464): auid=4294967295 uid=10702 gid=10790 ses=4294967295 pid=30441 comm="ksmserver-logou" exe="/usr/libexec/ksmserver-logout-greeter" sig=6 res=1 aug 28 10:33:31 svarten kwin_x11[3962]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 45943, resource id: 111149066, major code: 15 (QueryTree), minor code: 0 I then as normal user in konsole issued reboot, and after reboot all is OK.
This bug still exists on Mageia 7 as of the Round 3 Beta2 test isos, but the symptoms are different. After a successful install without the nvidia340 driver and test with nouveau, I used MCC to install the nvidia340 driver. When I went to reboot, using the "leave" option of the dsktop context menu, instead of the normal "logout, shutdown, reboot, hibernate" options, I was presented with a small box that said "ksmserver" and a button marked "shutdown." Clicking on the button shuts down the computer, as I would expect.
Still in effect in Mageia 7 as of today, and it has gone back to the old behavior.
Hi, thanks for reporting this bug. We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to CLOSED:OLD
Resolution: (none) => OLDCC: (none) => ouaurelienStatus: NEW => RESOLVED
As per comment 30 and my vague memory it is valid on Mageia 7 which we still support.
Status: RESOLVED => REOPENEDVersion: 6 => 7Resolution: OLD => (none)
(In reply to Morgan Leijström from comment #32) > As per comment 30 and my vague memory it is valid on Mageia 7 which we still > support. Yeah, you're right.
CC: ouaurelien => (none)
I don't see it any longer, but that's only because I have removed all my nvidia cards and replaced them with Radeon cards.
My old nvidia laptop is out of duty. Asking for help on qa list.
Fixed in Mageia 8. When the nvidia driver is updated, the current loaded Kernel module has version mismatch with the one on the disk. So there is API mismatch. Plasma uses OpenGL and can't establish correct connection to driver. So, it fails miserably. This is fixed for ksmserver-logout-greeter, which switches to software rendered backend gracefully. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Status: REOPENED => RESOLVEDResolution: (none) => FIXEDCC: (none) => ouaurelien