[konsole] [Bug 344119] 100% CPU usage after closing konsole, after upgrading to 3.0.1/KF5.6.0 with nvidia driver

2016-05-11 Thread Moritz Augustin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=344119 Moritz Augustin changed: What|Removed |Added CC|softw...@moritz-augustin.de | -- You are receiving this mail because: You

[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times

2016-05-20 Thread Moritz Augustin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=348569 Moritz Augustin changed: What|Removed |Added CC|softw...@moritz-augustin.de | -- You are receiving this mail because: You

[kate] [Bug 343629] write cursor does not move when keys are pressed

2016-01-15 Thread Moritz Augustin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343629 Moritz Augustin changed: What|Removed |Added CC||softw...@moritz-augustin.de --- Comment #23 f

[kwin] [Bug 358202] New: kwin often stops partially working (Function not implemented)

2016-01-19 Thread Moritz Augustin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358202 Bug ID: 358202 Summary: kwin often stops partially working (Function not implemented) Product: kwin Version: 5.5.3 Platform: Archlinux Packages OS: Linux

[kwin] [Bug 358202] kwin often stops partially working (Function not implemented)

2016-01-19 Thread Moritz Augustin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358202 --- Comment #2 from Moritz Augustin --- I do not think this is bug #353428. I have no drkonqi process open at all and kwin seems not to crash completely (e.g. I can still maximize/tile windows/move them to other virtual desktops using my hotkeys; or is

[plasmashell] [Bug 340447] [Plasma 5] Please add an xembed compatible system tray applet

2016-01-22 Thread Moritz Augustin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=340447 Moritz Augustin changed: What|Removed |Added CC||softw...@moritz-augustin.de --- Comment #12 f

[kwin] [Bug 358202] kwin often stops partially working (Function not implemented)

2016-02-02 Thread Moritz Augustin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358202 --- Comment #8 from Moritz Augustin --- Just to give you an update on this: it might be indeed true that clusterssh was responsible for the behaviour I have reported. At least the problem has not appeared again after closing clusterssh and restarting kw