[kwin] [Bug 404617] KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 --- Comment #8 from Arjun Menon --- I can't reproduce this bug anymore. After I update all my packages, KWin stopped crashing, and Plasma started crashing instead: https://bugs.kde.org/show_bug.cgi?id=405406 But as two people pointed out, the source of these troubles is the proprietary Nvidia driver. I uninstalled the Nvidia driver; and now everything (ie. Nouveau) works perfectly! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405406] Plasma Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=405406 --- Comment #2 from Arjun Menon --- You are right. This bug was fixed after I uninstalled the proprietary Nvidia driver! Hurray! Nouveau is doing its job well! I'm so happy. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404617] KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 --- Comment #7 from Arjun Menon --- Well, KWin doesn't crash after sleep, as of now -- Plasma does instead. I created a ticket for the Plasma crash here: https://bugs.kde.org/show_bug.cgi?id=405406 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405406] Plasma Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=405406 Bug 405406 depends on bug 404617, which changed state. Bug 404617 Summary: KWin Crashes After Waking Up From Sleep https://bugs.kde.org/show_bug.cgi?id=404617 What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|BACKTRACE |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404617] KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 Arjun Menon changed: What|Removed |Added Resolution|BACKTRACE |--- Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED --- Comment #5 from Arjun Menon --- I'll need to compile KDE from sources to have debug symbols, so getting this backtrace will take awhile. Is it fine if I re-open this bug, so that the Bug Janitor doesn't automatically "resolve" this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404617] KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 Arjun Menon changed: What|Removed |Added Blocks||405406 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=405406 [Bug 405406] Plasma Crashes After Waking Up From Sleep -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405406] Plasma Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=405406 Arjun Menon changed: What|Removed |Added Depends on||404617 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=404617 [Bug 404617] KWin Crashes After Waking Up From Sleep -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404617] KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 --- Comment #4 from Arjun Menon --- Hi Martin Flöser, I'll try to look into what I need to do, in order to install debug symbols for KDE/Plasma on Arch Linux. Sorry for the late response. I had switched to using Windows for the past few weeks, and just switched back to Arch Linux today. Out of habit, I ran the command to update all my packages soon after logging in. It was too late before I remembered that I needed to reproduce this bug. I ended up with the latest KDE and Plasma packages as a result. I've only been using Arch Linux for less than a day, but now, instead of KWin crashing, Plasma is crashing. I created a new bug report for it: https://bugs.kde.org/show_bug.cgi?id=405406 I also want to make a note that sleep/wake on Plasma/KDE was working fine previously, until November 2018. I had no problems whatsoever with sleep/wake. I had been exclusively using Arch Linux on my laptop for several months in 2018. My laptop went through many sleep/wake cycles with no issues. I almost never restarted Linux, or even exited/restarted Plasma. I always just put my laptop to sleep, and woke up it later. This problem started after I re-installed Arch Linux in February this year. There was a period, from November 2018 to February 2019, during which I was using Windows instead of Linux. Also, since Arch Linux uses sytemd, my guess is that the underlying command issued by Plasma for sleeping is probably `systemctl suspend` or something similar (but I haven't checked the Plasma sources on this though). Hi Vlad Zagorodniy, My laptop has an integrated Intel GPU: Intel® UHD Graphics 620. This Intel GPU is on the CPU die itself. The CPU on my laptop is the Intel Core i7 8550U. Here is the spec page for the 8550U: https://ark.intel.com/content/www/us/en/ark/products/122589/intel-core-i7-8550u-processor-8m-cache-up-to-4-00-ghz.html My laptop also has a dedicated GPU: Nvidia MX150. I have the official closed-source Nvidia driver on Linux (and not nouveau). But I don't think the Nvidia MX150 is ever active or being used. I once tried to run a game (0 A.D.) on the Nvidia GPU using `optirun` (c.f. Nvidia Optimus), but it actually ran super-slow! Even glxgears ran horribly slow on the Nvidia GPU compared to the Intel GPU. It's weird because the Nvidia GPU is a lot more powerful than the Intel GPU. I never investigated and figured out why the Nvidia GPU was super-slow on Linux. Why I stopped using Linux from Nov 2018 to Feb 2019 The story of why I had to switch to Windows for 4 months (from Nov '18 to Feb '19) is a long one, but I'll share it here, for some context. This is a bit long and rather tengetial, so please feel free to skip it. Sometime in November 2018, I was running a long-overdue update of all my packages (ie `pacman -Syu`). While some package was installing, Plasma crashed. I was in the middle of reading an article online, and Plasma suddenly crashed suddenly (with a lot of error messages), and brought me back to the shell (on Arch). My theory is that it happened because pacman (the Arch Linux package manager) was probably literally overwriting/replacing Plasma binaries, while the system was running. Also, because, my package update process was running on Konsole, I think when KDE crashed, it killed the package update process in the middle of whatever it was doing. After this happened, I think I tried to finish my update, and then rebooted my computer. But when I rebooted, the system wouldn't boot. The interrupted system update actually corrupted my Arch Linux installation. I spent several hours trying to fix it, but eventually gave up, and switched to Windows for several months (until February 2019). I had some important job interviews coming up, and I couldn't spend all my time trying to fix my Arch Linux installation. Initially, I found out that the vmlinuz image itself was broken (and non-bootable). But I fixed that / got the kernel to build properly; but after that, the next problem was that my initramfs was partially broken. The Arch Linux mkinitcpio command (https://wiki.archlinux.org/index.php/mkinitcpio) wasn't working properly, and was throwing errors while building. It would build an initramfs that lacked support for decrypting a dm-crypt partition. So I couldn't actually boot my system -- even if I could access it from an Arch Linux installation USB. Anyways, because of my job interviews, I switched to Windows for a while. Later on, in February 2019, I spent some more time trying to fix my broken Arch Linux installation, but finally decided it wasn't worth my time anymore, so I backed up my home directory, and set up everything from scratch. Ever since coming back to Arch Linux + KDE/Plasma (in February 2019), I've had this intractable sleep/wake problem. Thank you, both of you, for looking into these bugs, Arjun -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405406] New: Plasma Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=405406 Bug ID: 405406 Summary: Plasma Crashes After Waking Up From Sleep Product: plasmashell Version: 5.15.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: arjungme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.2) Qt Version: 5.12.1 Frameworks Version: 5.56.0 Operating System: Linux 5.0.0-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: My computer woke up, after sleeping. I was running Arch Linux, with all of latest KDE and Plasma packages (as of March 12, 2019), when this happened I recently (today; on March 12, 2019), updated all of packages (ran `pacman -Syu`), and therefore have all the latest packages. But previously, before I updated to the latest packages, KWin consistently crashed after waking up from sleep. I created a bug report for it here: https://bugs.kde.org/show_bug.cgi?id=404617#c0 This is the second time accidentally (out of habit) earlier today, and that time, I didn't get an opportunity to create this bug report. Plasma was a lot more broken. The whole taksbar was blanked out. But K Menu still worked, so I logged out, and logged back in. - Unusual behavior I noticed: Google Chrome always stops working when this happnes, but Firefox continues to work. Google Chrome stops rendering anything, so you have a blank/frozen window. After a while, KDE/Plasma shows that it has stopped responding and asks me if I want to terminate Google Chrome. I terminate it, and restart it, to get it working again. - Custom settings of the application: My computer has a 4K screen. I have a 17-inch HP Envy 17t laptop. The screen shows up as connected through an eDP port. Because it's a 4K screen, I have a KDE/Plasma configured with a scaling factoe 2.2 Furthermore, the icons have been configured to be scaled up as well. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa2602f46c0 (LWP 5930))] Thread 30 (Thread 0x7fa1c584a700 (LWP 31282)): #0 0x7fa264750afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa265651c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa265651d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa26739f92d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa26739fb9c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa26564b96c in () at /usr/lib/libQt5Core.so.5 #6 0x7fa26474aa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa265335b23 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7fa1c6ffd700 (LWP 17414)): #0 0x7fa264750afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa265651c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa265651d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa26739f92d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa26739fb9c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa26564b96c in () at /usr/lib/libQt5Core.so.5 #6 0x7fa26474aa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa265335b23 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7fa1c67fc700 (LWP 9868)): #0 0x7fa264750afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa265651c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa265651d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa26739f92d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa26739fb9c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa26564b96c in () at /usr/lib/libQt5Core.so.5 #6 0x7fa26474aa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa265335b23 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7fa1c77fe700 (LWP 9828)): #0 0x7fa264750afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa265651c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa265651d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa26739f92d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa26739fb9c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa26564b96c in () at /usr/lib/libQt5Core.so.5 #6 0x7fa26474aa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa265335b23 in clone () at
[kwin] [Bug 404617] New: KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 Bug ID: 404617 Summary: KWin Crashes After Waking Up From Sleep Product: kwin Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: arjungme...@gmail.com Target Milestone: --- Application: kwin_x11 (5.15.1) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.20.10-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I put my computer to sleep through the K Start Menu. When it wakes up, KWin consistently crashs. I'm running Arch Linux, with all of the latest stable Plasma and other KDE applications. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f516b1f2840 (LWP 871))] Thread 5 (Thread 0x7f51523d3700 (LWP 970)): #0 0x7f51717c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f51722c928c in () at /usr/lib/libQt5Script.so.5 #2 0x7f51722c92a9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f515b895700 (LWP 965)): #0 0x7f5173e6ad16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f51729e2bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f51729e408b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f517298fb2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f51727d3569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f5170f7b969 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f51727d496c in () at /usr/lib/libQt5Core.so.5 #7 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f5169a35700 (LWP 936)): #0 0x7f5173e6ad16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f51729e2bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f51729e408b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f517298fb2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f51727d3569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f51709e0ba6 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f51727d496c in () at /usr/lib/libQt5Core.so.5 #7 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f516aa96700 (LWP 928)): #0 0x7f5173e6ac21 in poll () at /usr/lib/libc.so.6 #1 0x7f51726f8630 in () at /usr/lib/libxcb.so.1 #2 0x7f51726fa2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f516adbe949 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f51727d496c in () at /usr/lib/libQt5Core.so.5 #5 0x7f51717bea9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f5173e75b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f516b1f2840 (LWP 871)): [KCrash Handler] #6 0x7f51724d5739 in () at /usr/lib/libkwin4_effect_builtins.so.1 #7 0x7f51724d57f6 in () at /usr/lib/libkwin4_effect_builtins.so.1 #8 0x7f51724d6df8 in () at /usr/lib/libkwin4_effect_builtins.so.1 #9 0x7f51724d7812 in () at /usr/lib/libkwin4_effect_builtins.so.1 #10 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #11 0x7f5172446ffa in () at /usr/lib/libkwin4_effect_builtins.so.1 #12 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #13 0x7f517253a51d in KWin::Effect::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwineffects.so.12 #14 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #15 0x7f517253a51d in KWin::Effect::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwineffects.so.12 #16 0x7f5173be0774 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #17 0x7f5173bcac3d in KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #18 0x7f5173be0605 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at
[braindump] [Bug 331088] Braindump crash during normal usage
https://bugs.kde.org/show_bug.cgi?id=331088 Arjun Menon changed: What|Removed |Added CC||arjungme...@gmail.com --- Comment #3 from Arjun Menon --- Wow, it's been 4.5 years. I'd completely forgotten about this. I had to look up what Braindump was again. I guess I ended up not using it, after exploring it a bit. I still use KDE (on my personal laptop) on top of Arch Linux everyday, but I'm always on the latest version (Arch being Arch). So even if I downloaded Braindump, the bug probably doesn't exist anymore. In any case, I suppose someone that's actually working on Braindump should look into this bug. The description I provided (back in 2014) has enough detail to try to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
