[Spectacle] [Bug 443398] Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode.
https://bugs.kde.org/show_bug.cgi?id=443398 --- Comment #5 from datta.sand...@gmail.com --- I have a similar problem on Manjaro i3 (v 22.1.0). The first invocation of spectacle disappears when the rectangle selection tool is selected and take a screenshot button is pressed but relaunching spectacle and trying again works! I too have multiple monitors (3 to be precise). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443398] Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode.
https://bugs.kde.org/show_bug.cgi?id=443398 datta.sand...@gmail.com changed: What|Removed |Added CC||datta.sand...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 451041] Kdevelop crash just after a LMB in editor on a source line
https://bugs.kde.org/show_bug.cgi?id=451041 --- Comment #1 from Sandeep --- Created attachment 147957 --> https://bugs.kde.org/attachment.cgi?id=147957=edit New crash information added by DrKonqi kdevelop (5.8.220380 (22.03.80)) using Qt 5.15.3 - What I was doing when the application crashed: Clicked on a line with left mouse button, and it crashed. -- Backtrace (Reduced): #4 0x7f3f64fd3a74 in QAccessible::queryAccessibleInterface(QObject*) () at /usr/lib/libQt5Gui.so.5 #5 0x7f3f64fd40d2 in QAccessibleEvent::accessibleInterface() const () at /usr/lib/libQt5Gui.so.5 #6 0x7f3f64fcfc85 in QAccessible::updateAccessibility(QAccessibleEvent*) () at /usr/lib/libQt5Gui.so.5 #7 0x7f3f62f4493b in KateViewInternal::cursorMoved() () at /usr/lib/libKF5TextEditor.so.5 #8 0x7f3f62f3c8a4 in KateViewInternal::updateCursor(KTextEditor::Cursor, bool, bool, bool) () at /usr/lib/libKF5TextEditor.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 451041] Kdevelop crash just after a LMB in editor on a source line
https://bugs.kde.org/show_bug.cgi?id=451041 Sandeep changed: What|Removed |Added CC||sandy.8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396946] Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off
https://bugs.kde.org/show_bug.cgi?id=396946 --- Comment #8 from Sandeep --- It doesn't seem to happen anymore with recent KDE versions. I'm pretty sure it's no longer an issue. You can go ahead and close this bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432306] New: kscreen doctor does not recognize outpu.MONITOR.primary.true
https://bugs.kde.org/show_bug.cgi?id=432306 Bug ID: 432306 Summary: kscreen doctor does not recognize outpu.MONITOR.primary.true Product: KScreen Version: git Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: kscreen-bugs-n...@kde.org Reporter: datta.sand...@gmail.com Target Milestone: --- SUMMARY It seems kscreen-doctor is not able to set or unset the primary status of a monitor. This is clear from the parsePositionalArgs() function in doctor.cpp. I am assuming this is an oversight. If so, please enable support for like output.MONITOR.primary.true/false (or something better). STEPS TO REPRODUCE 1. kscreen-doctor output.DP-4.Primary.true OBSERVED RESULT Unable to parse arguments: output.DP-4.Primary.true EXPECTED RESULT Set DP-4 as primary monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE 5.20.5 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78/0 Qt Version: 5.15.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 419291] New: KDevelop crashes while parsing project files
https://bugs.kde.org/show_bug.cgi?id=419291 Bug ID: 419291 Summary: KDevelop crashes while parsing project files Product: kdevelop Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.15.0 Frameworks Version: 5.68.0 Operating System: Linux 5.6.0-rc6-1-git-07763-gccaaaf6fe5a5 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Looking at a different application, when KDevelop crashed -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1dac0f6180 (LWP 2008))] Thread 28 (Thread 0x7f1d01ffb700 (LWP 2180)): #0 0x7f1dbcff5cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1dbff5ee04 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f1dbff5eee2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1dbc57d289 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1dbc580d1b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f1dbc57ee5c in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f1dbff58f06 in () at /usr/lib/libQt5Core.so.5 #12 0x7f1dbcfef46f in start_thread () at /usr/lib/libpthread.so.0 #13 0x7f1dbfbd93d3 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f1d027fc700 (LWP 2179)): #0 0x7f1dbcff5cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1dbff5ee04 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f1dbff5eee2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1dbc57d289 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1dbc580d1b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7f1dbc57c47e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7f1dbc580d71 in () at /usr/lib/libKF5ThreadWeaver.so.5 #25 0x7f1dbc57c47e in
[plasmashell] [Bug 372789] Plasma freezes with black screen when logging out
https://bugs.kde.org/show_bug.cgi?id=372789 --- Comment #45 from Sandeep --- (In reply to Ongun Kanat from comment #44) > BTW, is there any Wayland protocol or something similar proposed to kill > sessions after sometime prevent similar lockouts? No, this doesn't have anything to do with Wayland protocol AFAIK. It seems to be a bug within KWin/Plasma. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 390151] Crash on exit [wl_proxy_destroy, wl_map_insert_at]
https://bugs.kde.org/show_bug.cgi?id=390151 Sandeep changed: What|Removed |Added CC|sandy.8...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 173668] KDE must show Ksysguard main window with Ctrl+Esc
https://bugs.kde.org/show_bug.cgi?id=173668 Sandeep changed: What|Removed |Added CC||sandy.8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394189] KWin crashes on pressing Alt + Tab
https://bugs.kde.org/show_bug.cgi?id=394189 Sandeep changed: What|Removed |Added Resolution|BACKTRACE |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Sandeep --- I no longer face the bug, it was fixed a while back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398494] KDE either freezes/crashes after launching Steam
https://bugs.kde.org/show_bug.cgi?id=398494 --- Comment #6 from Sandeep --- I was able to reproduce the crash a few times, but gdb doesn't show a backtrace of any sort - the only output I can see is about threads getting destroyed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398494] KDE either freezes/crashes after launching Steam
https://bugs.kde.org/show_bug.cgi?id=398494 Sandeep changed: What|Removed |Added Version|5.13.5 |5.13.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398494] KDE either freezes/crashes after launching Steam
https://bugs.kde.org/show_bug.cgi?id=398494 --- Comment #5 from Sandeep --- I was able to reproduce kwin freezing up as mentioned below - obtained the backtrace by ssh'ing from another system - so the kernel and other low level software are fine, but Plasma/KWin is frozen. #0 0x7f1cc1ea0bb1 in poll () at /usr/lib/libc.so.6 #1 0x7f1cc210f180 in () at /usr/lib/libxcb.so.1 #2 0x7f1cc2110b3f in () at /usr/lib/libxcb.so.1 #3 0x7f1cc2110c51 in xcb_wait_for_reply () at /usr/lib/libxcb.so.1 #4 0x7f1cc34f2cb0 in KWin::Shadow::readX11ShadowProperty(unsigned int) () at /usr/lib/libkwin.so.5 #5 0x7f1cc34f4ed8 in KWin::Shadow::createShadowFromX11(KWin::Toplevel*) () at /usr/lib/libkwin.so.5 #6 0x7f1cc34f5b69 in KWin::Shadow::createShadow(KWin::Toplevel*) () at /usr/lib/libkwin.so.5 #7 0x7f1cc35418b6 in KWin::Toplevel::getShadow() () at /usr/lib/libkwin.so.5 #8 0x7f1cc25ca0c0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #9 0x7f1cc303329b in KWayland::Server::SurfaceInterface::Private::swapStates(KWayland::Server::SurfaceInterface::Private::State*, KWayland::Server::SurfaceInterface::Private::State*, bool) () at /usr/lib/libKF5WaylandServer.so.5 #10 0x7f1cc303375c in KWayland::Server::SurfaceInterface::Private::commit() () at /usr/lib/libKF5WaylandServer.so.5 #11 0x7f1cbae641c8 in ffi_call_unix64 () at /usr/lib/libffi.so.6 #12 0x7f1cbae63c2a in ffi_call () at /usr/lib/libffi.so.6 #13 0x7f1cbe1156ff in () at /usr/lib/libwayland-server.so.0 #14 0x7f1cbe1120a3 in () at /usr/lib/libwayland-server.so.0 #15 0x7f1cbe113702 in wl_event_loop_dispatch () at /usr/lib/libwayland-server.so.0 #16 0x7f1cc300132f in KWayland::Server::Display::Private::dispatch() () at /usr/lib/libKF5WaylandServer.so.5 #17 0x556497efc687 in () #18 0x556497efa305 in () #19 0x7f1cc1dd4223 in __libc_start_main () at /usr/lib/libc.so.6 #20 0x556497efb19e in _start () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372789] Plasma freezes with black screen when logging out
https://bugs.kde.org/show_bug.cgi?id=372789 --- Comment #34 from Sandeep --- I forgot to mention, it's been working fine for me, for a few months now - no black screen when logging out. However, it looks like the Plasma session does get stuck and fails to close entirely - not sure if that's related. It doesn't seem to cause problems. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398494] KDE either freezes/crashes after launching Steam
https://bugs.kde.org/show_bug.cgi?id=398494 --- Comment #4 from Sandeep --- Thanks! I will try it out when it crashes again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398494] KDE either freezes/crashes after launching Steam
https://bugs.kde.org/show_bug.cgi?id=398494 --- Comment #2 from Sandeep --- Since the desktop as a whole crashes or freezes, I am not able to obtain a backtrace through Plasma's normal crash reporting mechanism. Is there a log file or other place where kwin/Plasma writes the crash backtrace to? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398494] KDE either freezes/crashes after launching Steam
https://bugs.kde.org/show_bug.cgi?id=398494 Sandeep changed: What|Removed |Added CC||sandy.8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398494] New: KDE either freezes/crashes after launching Steam
https://bugs.kde.org/show_bug.cgi?id=398494 Bug ID: 398494 Summary: KDE either freezes/crashes after launching Steam Product: kwin Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: --- I use Plasma on Wayland. Whenever I launch the latest versions of "Steam (Runtime)" - the latest version with the UI refresh, the chat window always pops up. It always fails to login. If I close Steam's chat window while it's still in the process of logging in, when the login operation fails, the chat window automatically pops up again, showing that it's failed to login. At this point, one of the following happens: 1. The whole desktop freezes and I cannot switch to a TTY either, but I can Ctrl + Alt + PrtScr + REISUB to reboot the machine 2. Plasma crashes and the display manager's login screen is shown again This only happens on Plasma on Wayland. I tested, and it does not happen on Plasma on X11, or GNOME on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397170] KDeveloper crashes while folding code
https://bugs.kde.org/show_bug.cgi?id=397170 --- Comment #2 from Sandeep --- I haven't been able to reproduce the crash so far. It was just a random crash that happened one time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385026] Pointer lock interferes with games
https://bugs.kde.org/show_bug.cgi?id=385026 --- Comment #7 from Sandeep --- Are you facing this bug? https://bugs.kde.org/show_bug.cgi?id=35 I still get that from time to time. The patch (https://phabricator.kde.org/D13466) to fix that is supposedly in kwin 5.13.1+, but kwin 5.13.1+ still exhibits that buggy behaviour from time to time. I compiled kwin 5.13.3 with that patch, and that seemed to conclusively fix that problem for me. Maybe you can try compiling 5.13.4 with that patch and see if it works for you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385026] Pointer lock interferes with games
https://bugs.kde.org/show_bug.cgi?id=385026 --- Comment #5 from Sandeep --- Actually, the bug was fixed in kwayland 5.48+. If you upgrade to that and kwin 5.13.0+, the pointer lock problem is mostly solved. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397170] KDeveloper crashes while folding code
https://bugs.kde.org/show_bug.cgi?id=397170 Sandeep changed: What|Removed |Added CC||sandy.8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397170] New: KDeveloper crashes while folding code
https://bugs.kde.org/show_bug.cgi?id=397170 Bug ID: 397170 Summary: KDeveloper crashes while folding code Product: kdevelop Version: 5.2.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: --- Application: kdevelop (5.2.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.12-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Manually folding code by clicking the arrow on the vertical bar to the left of the text editor -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f938395ee00 (LWP 4232))] Thread 23 (Thread 0x7f930cff9700 (LWP 4454)): #0 0x7f93ab329991 in poll () at /usr/lib/libc.so.6 #1 0x7f93a26ab523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93a26ab63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f93ab853054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f93ab7fe94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f93ab647a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f93a95583f6 in () at /usr/lib/libKDevPlatformLanguage.so.52 #7 0x7f93ab651b45 in () at /usr/lib/libQt5Core.so.5 #8 0x7f93a4e94a8d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f93ab334823 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f930dffb700 (LWP 4451)): #0 0x7f93a4e9aaec in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f93ab6522fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f93a0c95139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f93a0c99009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f93a0c941fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f93a0c97059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f93ab651b45 in () at /usr/lib/libQt5Core.so.5 #7 0x7f93a4e94a8d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f93ab334823 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f930e7fc700 (LWP 4450)): #0 0x7f93a4e9aaec in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f93ab6522fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f93a0c95139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f93a0c99009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f93a0c941fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f93a0c99062 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f93a0c941fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f93a0c97059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f93ab651b45 in () at /usr/lib/libQt5Core.so.5 #9 0x7f93a4e94a8d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f93ab334823 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f930effd700 (LWP 4449)): #0 0x7f93a4e9aaec in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f93ab6522fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f93a0c95139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f93a0c99009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f93a0c941fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f93a0c97059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f93ab651b45 in () at /usr/lib/libQt5Core.so.5 #7 0x7f93a4e94a8d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f93ab334823 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f930f7fe700 (LWP 4448)): #0 0x7f93a4e9aaec in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f93ab6522fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f93a0c95139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at
[kwin] [Bug 396946] Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off
https://bugs.kde.org/show_bug.cgi?id=396946 --- Comment #5 from Sandeep --- This also happens if the monitor is turned off, and then turned on while KDE is running. Let me know if you need any other information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396946] Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off
https://bugs.kde.org/show_bug.cgi?id=396946 Sandeep changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from Sandeep --- I've provided the request info, please see my earlier comments. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396946] Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off
https://bugs.kde.org/show_bug.cgi?id=396946 --- Comment #3 from Sandeep --- Here's a bunch of photos, and a video that shows the corruption I'm talking about - https://photos.app.goo.gl/ZEFEf3jA7u5r4Brw8 The system becomes unusable, but I am able to force a restart using Ctrl + Alt + PrtScr + REISUB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396946] Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off
https://bugs.kde.org/show_bug.cgi?id=396946 Sandeep changed: What|Removed |Added CC||sandy.8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396946] Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off
https://bugs.kde.org/show_bug.cgi?id=396946 --- Comment #2 from Sandeep --- (In reply to David Edmundson from comment #1) > what gets corrupted? Please add a screenshot I can't take a screenshot, but will take a photo and attach it here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396946] New: Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off
https://bugs.kde.org/show_bug.cgi?id=396946 Bug ID: 396946 Summary: Display corruption occurs if system is resumed from suspend/standby/sleep while monitor is off Product: kwin Version: 5.13.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: --- Details --- Linux version: 4.17.10 Plasma, kwin : 5.13.3 SDDM: 0.18.0 Plasma Wayland session, started from SDDM Steps to reproduce -- * Suspend computer * Turn off electrical power supply to monitor * Resume computer * Turn on electrical power supply to monitor Observe display corruption - switching TTY's doesn't help either. Does not happen when using Gnome, with GDM or SDDM. Consistently occurs when using Plasma on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 396907] New: Amarok crashes when user clicks on Help ---> Diagnostics, while running under Wayland
https://bugs.kde.org/show_bug.cgi?id=396907 Bug ID: 396907 Summary: Amarok crashes when user clicks on Help ---> Diagnostics, while running under Wayland Product: amarok Version: kf5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: kf5 Happens on Amarok master branch, atleast at commit 453aa79e03fc512abcca5b2109a2aecce6dab314 (and most likely older). I did a little digging, and found that it crashes specifically at this line. DiagnosticDialog.cpp - Line 127 aPhononBackend->property( "X-KDE-PhononBackendInfo-Version", QVariant::String ).toString(), // & Backend -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 396907] Amarok crashes when user clicks on Help ---> Diagnostics, while running under Wayland
https://bugs.kde.org/show_bug.cgi?id=396907 Sandeep changed: What|Removed |Added CC||sandy.8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 396020] New: KTorrent crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=396020 Bug ID: 396020 Summary: KTorrent crashes when exiting Product: ktorrent Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: sandy.8...@gmail.com Target Milestone: --- Application: ktorrent (5.1.0) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Closed KTorrent - right clicked on KTorrent icon in taskbar notifications panel, and clicked quit. KTorrent crashed immediately after. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffbd988c5c0 (LWP 1828))] Thread 2 (Thread 0x7ffbc2fc3700 (LWP 1830)): #0 0x7ffbd3971ea9 in poll () at /usr/lib/libc.so.6 #1 0x7ffbccb1a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ffbccb1a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ffbd483b054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ffbd47e694c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ffbd462fa99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ffbd5c7a976 in () at /usr/lib/libQt5DBus.so.5 #7 0x7ffbd4639b45 in () at /usr/lib/libQt5Core.so.5 #8 0x7ffbcf43c075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7ffbd397c53f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7ffbd988c5c0 (LWP 1828)): [KCrash Handler] #6 0x7ffbc551ac39 in () at /usr/lib/libwayland-client.so.0 #7 0x7ffbc5516933 in wl_proxy_destroy () at /usr/lib/libwayland-client.so.0 #8 0x7ffbc3e09dd9 in KWayland::Client::PlasmaWindow::release() () at /usr/lib/libKF5WaylandClient.so.5 #9 0x7ffbc3e09dfb in KWayland::Client::PlasmaWindow::~PlasmaWindow() () at /usr/lib/libKF5WaylandClient.so.5 #10 0x7ffbc3e09efa in KWayland::Client::PlasmaWindow::~PlasmaWindow() () at /usr/lib/libKF5WaylandClient.so.5 #11 0x7ffbd480fa3b in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #12 0x7ffbd4818995 in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #13 0x7ffbc3e0a4ca in KWayland::Client::PlasmaWindowManagement::~PlasmaWindowManagement() () at /usr/lib/libKF5WaylandClient.so.5 #14 0x7ffbd480fa3b in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #15 0x7ffbd4818995 in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #16 0x7ffbb278efb4 in () at /usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so #17 0x7ffbd38bcf2c in __run_exit_handlers () at /usr/lib/libc.so.6 #18 0x7ffbd38bd05a in () at /usr/lib/libc.so.6 #19 0x7ffbd38a7072 in __libc_start_main () at /usr/lib/libc.so.6 #20 0x55e65f48189a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394189] KWin crashes on pressing Alt + Tab
https://bugs.kde.org/show_bug.cgi?id=394189 --- Comment #1 from Sandeep <sandy.8...@gmail.com> --- So..I rebuilt KWin debug build, and now it doesn't crash.well, I will try using it as is for the next few days, and see what happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394189] KWin crashes on pressing Alt + Tab
https://bugs.kde.org/show_bug.cgi?id=394189 Sandeep <sandy.8...@gmail.com> changed: What|Removed |Added CC||sandy.8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394189] New: KWin crashes on pressing Alt + Tab
https://bugs.kde.org/show_bug.cgi?id=394189 Bug ID: 394189 Summary: KWin crashes on pressing Alt + Tab Product: kwin Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: --- KWin consistently crashes whenever I attempt to switch windows using Alt + Tab. I have attempted to use gdb to get a stack trace, but for some reason the entire system hangs if I attach gdb to kwin and reproduce the crash (can't even switch to a VT). The best I have is this: Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. 0x7f90c30f8bc4 in QPlatformWindow::setGeometry(QRect const&) () from /usr/lib/libQt5Gui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385026] Pointer lock interferes with games
https://bugs.kde.org/show_bug.cgi?id=385026 --- Comment #2 from Sandeep <sandy.8...@gmail.com> --- Well, when I say menu, it's not the usual context menu that you get when you use the right mouse button click. It's more like a separate screen that shows game menu with options like settings, resume, quit etc. Is there any way for me to capture these requests? If I build KWin debug build, are there any logs I can enable to find out if the app is requesting it a second time? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385026] New: Pointer lock interferes with games
https://bugs.kde.org/show_bug.cgi?id=385026 Bug ID: 385026 Summary: Pointer lock interferes with games Product: kwin Version: 5.10.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: --- KWin automatically locks the pointer for some games (I guess to prevent the pointer from escaping the window, so that relative mouse movement can work) - however, this causes problems in games like Left 4 Dead 2 and Jotun, when we access the game menu. Here's what happens: 1) I tap Escape once, to pause the game and access the game menu 2) For some reason, KWin thinks the game menu is a separate window, and the pointer is locked to the game menu 3) I resume the game - and am unable to move the mouse in the game (whereas it worked fine before opening the menu) The same also applies if we try to open the Steam overlay while in the game. Can we turn off pointer lock setting somewhere, or manually override it and tell it which window to lock? Some kind of shortcut key to enable pointer lock manually for currently focused window would be nice. Is it possible to configure it to show the notice for a smaller period of time (1-2 seconds instead of 3-5 like it is now)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372789] Plasma freezes with black screen when logging out
https://bugs.kde.org/show_bug.cgi?id=372789 --- Comment #12 from Sandeep <sandy.8...@gmail.com> --- I tried out KDE Neon, the developer unstable edition. Tried to reproduce the problem once, worked fine there. Either the problem is fixed, or because the conditions are different (Neon runs much older kernel, mesa etc. than my Arch Linux system) the problem can't be reproduced. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372789] Plasma freezes with black screen when logging out
https://bugs.kde.org/show_bug.cgi?id=372789 Sandeep <sandy.8...@gmail.com> changed: What|Removed |Added CC||sandy.8...@gmail.com --- Comment #10 from Sandeep <sandy.8...@gmail.com> --- I can confirm that I face this bug too. I am running Arch Linux, here are the software versions: plasma-desktop - 5.10.5 plasma-framework - 5.38.0 Linux kernel version - 4.12.10 Qt version - 5.9.1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381793] New: Repeated crash of Kate application
https://bugs.kde.org/show_bug.cgi?id=381793 Bug ID: 381793 Summary: Repeated crash of Kate application Product: kate Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: ku...@ikm.uni-hannover.de Target Milestone: --- Application: kate (16.08.2) (Compiled from sources) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: The system was idle. And I was working on internet. When I started using Kate, it suddenly hanged up. This happen several times, sometimes Kate doesnt work for days. - Unusual behavior I noticed: Sometimes, while working on a code, Kate suddenly hangs up and I have to restart my system. No other application also works. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". To enable execution of this file add add-auto-load-safe-path /global/linux/usrlibs/gcc/4.8.1/lib64/libstdc++.so.6.0.18-gdb.py line to your configuration file "/home/kumar/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/kumar/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" [Current thread is 1 (Thread 0x2b3511327dc0 (LWP 16776))] Thread 2 (Thread 0x2b35304a5700 (LWP 16778)): #0 0x2b3516a5949d in poll () at /lib64/libc.so.6 #1 0x2b351a4c5314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x2b351a4c542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x2b3515f7532b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x2b3515f22fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x2b3515d5df1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x2b3515a491d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x2b3515d629e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x2b351a013734 in start_thread () at /lib64/libpthread.so.0 #9 0x2b3516a61d3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x2b3511327dc0 (LWP 16776)): [KCrash Handler] #6 0x010c2070 in () #7 0x2b3515f2d3c9 in QMetaObject::cast(QObject*) const () at /usr/lib64/libQt5Core.so.5 #8 0x2b351249f46f in () at /usr/lib64/libKF5XmlGui.so.5 #9 0x2b3515f24d6d in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x2b35146fde78 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x2b351470249a in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x2b3515f24fc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x2b35147005cc in QApplication::setActiveWindow(QWidget*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x2b35147007d3 in QApplicationPrivate::notifyActiveWindowChange(QWindow*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x2b3514f13b95 in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () at /usr/lib64/libQt5Gui.so.5 #16 0x2b3514f13eed in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5 #17 0x2b3514ef5eeb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #18 0x2b352464abc0 in () at /usr/lib64/libQt5XcbQpa.so.5 #19 0x2b351a4c5134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #20 0x2b351a4c5388 in () at /usr/lib64/libglib-2.0.so.0 #21 0x2b351a4c542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #22 0x2b3515f7530c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #23 0x2b3515f22fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #24 0x2b3515f2aec6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #25 0x0044896b in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379597] New: Black screen after unlocking, when using Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=379597 Bug ID: 379597 Summary: Black screen after unlocking, when using Plasma Wayland session Product: kwin Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: sandy.8...@gmail.com Target Milestone: --- Environment: Arch Linux 64 bit KWin 5.9.5, GPU drivers: radeonsi, i965 Steps to reproduce -- * Log in to Plasma Wayland through SDDM * Lock the screen * Enter password in SDDM and unlock screen Expected results Desktop shows up Actual results -- Black screen Potential duplicate of https://bugs.kde.org/show_bug.cgi?id=377152 ? It's been 1.5 months since that report was closed, and I'm still facing this bug, so either the fix hasn't been released in a stable version yet, or it hasn't been fixed yet. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 377152] [Wayland] Resuming session after screen lock results in black screen
https://bugs.kde.org/show_bug.cgi?id=377152 Sandeep <sandy.8...@gmail.com> changed: What|Removed |Added CC||sandy.8...@gmail.com --- Comment #4 from Sandeep <sandy.8...@gmail.com> --- Hello, I was wondering if/when this fix will be released in a stable version? I am using 5.9.5, and I am still facing this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378452] Escape key not detected by several games in wayland
https://bugs.kde.org/show_bug.cgi?id=378452 Sandeep <sandy.8...@gmail.com> changed: What|Removed |Added CC||sandy.8...@gmail.com --- Comment #13 from Sandeep <sandy.8...@gmail.com> --- I am also facing the issue on KWin 5.9.5 and XWayland 1.19.3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358209] KDevelop crashes while importing new project
https://bugs.kde.org/show_bug.cgi?id=358209 --- Comment #2 from Sandeep <sandy.8...@gmail.com> --- Tried out 5.0.3, KDevelop still crashes when attempting to import a project from Project --> Open/Import project -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358209] KDevelop crashes while importing new project
https://bugs.kde.org/show_bug.cgi?id=358209 Sandeep <sandy.8...@gmail.com> changed: What|Removed |Added CC||sandy.8...@gmail.com --- Comment #1 from Sandeep <sandy.8...@gmail.com> --- Hello, I was wondering if this was fixed already? I still see this on KDevelop 5.0.2 -- You are receiving this mail because: You are watching all bug changes.
