[plasmashell] [Bug 391531] Desktop wallpaper is black and I cannot interact with the desktop
https://bugs.kde.org/show_bug.cgi?id=391531 --- Comment #4 from kafei <matthewisrip...@gmail.com> --- Created attachment 111867 --> https://bugs.kde.org/attachment.cgi?id=111867=edit output from running plasmashell After I ran plasmashell in a terminal, my wallpaper is appearing on both monitors again. I've attached the output anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391531] Desktop wallpaper is black and I cannot interact with the desktop
https://bugs.kde.org/show_bug.cgi?id=391531 --- Comment #3 from kafei <matthewisrip...@gmail.com> --- xwininfo output on the black background: xwininfo: Window id: 0x1ef (the root window) (has no name) Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 3840 Height: 1080 Depth: 24 Visual: 0x21 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x20 (installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +0+0 -0+0 -0-0 +0-0 -geometry 3840x1080+0+0 xwininfo on the desktop with wallpaper: xwininfo: Window id: 0x1e00016 "Desktop — Plasma" Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 1920 Height: 1080 Depth: 32 Visual: 0x7a Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x1e00015 (not installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +0+0 -1920+0 -1920-0 +0-0 -geometry 1920x1080+0+0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389397] Desktop not updating properly after quicktiling a maximized window
https://bugs.kde.org/show_bug.cgi?id=389397 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from kafei <matthewisrip...@gmail.com> --- This bug no longer happens since bug 376104 was fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391531] Desktop wallpaper is black and I cannot interact with the desktop
https://bugs.kde.org/show_bug.cgi?id=391531 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com --- Comment #1 from kafei <matthewisrip...@gmail.com> --- I've also just started getting this bug in the past week. No wallpaper appears on my primary display and right-click doesn't bring up the context menu, but the panel is still drawn. On my secondary monitor, the wallpaper renders fine and the context menu can still be brought up. I'm not exactly sure when it started, it might have been after the plasma 5.12.4 update? System info: Arch Linux Plasma 5.12.4 Frameworks 5.44 Qt 5.10.1 Nvidia proprietary driver 390.48 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389397] Desktop not updating properly after quicktiling a maximized window
https://bugs.kde.org/show_bug.cgi?id=389397 --- Comment #3 from kafei <matthewisrip...@gmail.com> --- Created attachment 110107 --> https://bugs.kde.org/attachment.cgi?id=110107=edit qdbus Kwin support infomation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389397] Desktop not updating properly after quicktiling a maximized window
https://bugs.kde.org/show_bug.cgi?id=389397 --- Comment #2 from kafei <matthewisrip...@gmail.com> --- Created attachment 110106 --> https://bugs.kde.org/attachment.cgi?id=110106=edit Corruption on the left window after quicktiling the right one back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389397] Desktop not updating properly after quicktiling a maximized window
https://bugs.kde.org/show_bug.cgi?id=389397 --- Comment #1 from kafei <matthewisrip...@gmail.com> --- Created attachment 110105 --> https://bugs.kde.org/attachment.cgi?id=110105=edit One window maximized. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389397] New: Desktop not updating properly after quicktiling a maximized window
https://bugs.kde.org/show_bug.cgi?id=389397 Bug ID: 389397 Summary: Desktop not updating properly after quicktiling a maximized window Product: kwin Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: matthewisrip...@gmail.com Target Milestone: --- Created attachment 110104 --> https://bugs.kde.org/attachment.cgi?id=110104=edit Two quicktiled windows. If I have two quicktiled windows side-by-side, and I maximize one of them and quicktile it back to where it was before, the other window remains partially covered by the maximized texture. It won't go away until I bring the corrupted window into focus, and then everything is normal again. Unfortunately when I try to take a screenshot with spectacle, the corruption goes away, so I had to take some pictures with my phone. I can't remember exactly when this started happening, but I think it was with Plasma 5.11. It happens under both OpenGL and XRender. System info: Arch Linux Nvidia proprietary driver 387.34-21 Plasma 5.11.5 Frameworks 4.42.0 Qt 5.10.0 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 389005] Startup & Shutdown scripts not working
https://bugs.kde.org/show_bug.cgi?id=389005 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com --- Comment #8 from kafei <matthewisrip...@gmail.com> --- BingMyBong, do you have "#!/bin/sh" at the start of your script? My startup script also stopped working last month, and after adding "#!/bin/sh" it started running during startup again. Though I wonder why that wasn't necessary before. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work
https://bugs.kde.org/show_bug.cgi?id=378523 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376155] "Quick tile window to the left/right" de-maximizes the window without tiling as a first action since plasma 5.9.0
https://bugs.kde.org/show_bug.cgi?id=376155 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com --- Comment #7 from kafei <matthewisrip...@gmail.com> --- This bug is still present in plasma 5.9.3. Yichao, did you ever get around to submitting your patch? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com --- Comment #29 from kafei <matthewisrip...@gmail.com> --- This bug is still present with Plasma 5.9.2 and KF5 5.31. Same as what everyone else here described: after adding a TODO to my personal calendar, I tried enabling the "PIM Events plugin" in the Digital Clock widget. When I hit "apply", plasmashell used up all of my RAM and began swapping out to disk. Killing plasmashell was the only solution. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375396] Opening files with krunner can spawn subprocesses which use 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375396 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from kafei <matthewisrip...@gmail.com> --- I still haven't been able to reproduce this over the past week, and can't reproduce it now with Plasma 5.9.2, so I'm going to close this. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375396] Opening files with krunner can spawn subprocesses which use 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375396 --- Comment #3 from kafei <matthewisrip...@gmail.com> --- I seem to be unable to reproduce this bug after updating to Plasma 5.9.1. There isn't much in the changelog related to krunner, but perhaps the bug was elsewhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369142] Crash in QQuickItem::isEnabled on startup
https://bugs.kde.org/show_bug.cgi?id=369142 --- Comment #19 from kafei <matthewisrip...@gmail.com> --- I don't believe I've had this crash occur since I upgraded to Plasma 5.8.4, and I definitely haven't had it occur with Plasma 5.8.5. I just checked through all the duplicates, and all of them report a plasma version <5.8.4, so it's possible the crash was fixed in that version. Fwiw, I was never able to get the crash to occur under Valgrind. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375396] Opening files with krunner can spawn subprocesses which use 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375396 --- Comment #1 from kafei <matthewisrip...@gmail.com> --- Created attachment 103580 --> https://bugs.kde.org/attachment.cgi?id=103580=edit Open file handles for krunner parent and child It's strange how krunner has open file handles to /dev/nvidia0 and the like... I suppose krunner somehow uses GPU acceleration? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375396] New: Opening files with krunner can spawn subprocesses which use 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375396 Bug ID: 375396 Summary: Opening files with krunner can spawn subprocesses which use 100% CPU Product: krunner Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: matthewisrip...@gmail.com Target Milestone: --- Created attachment 103579 --> https://bugs.kde.org/attachment.cgi?id=103579=edit htop screenshot of krunner cpu usage My system was acting sluggish today, so I opened htop to discover that krunner had pegged all 4 of my cores at 100% usage! It seemed to have spawned 4 subprocesses, each of which was using 100% of a core. I restarted my PC and my CPU usage was normal again. I managed to reproduce the bug as follows (with opening krunner by pressing alt+space): * Start okular through krunner: CPU usage normal * Search for a PDF through krunner and open it in the previous okular instance: one core starts running at 100% * Search and open a second PDF: a second core starts running at 100% * Try opening a few more PDFs: no change in CPU usage, still 2 cores pegged at 100% * Open gwenview through krunner: no change * Try opening another PDF: a third core starts running at 100% * Open spectacle through krunner: a fourth core starts running at 100% So the bug is reproducible after using krunner enough times, but not every usage results in another subprocess being spawned using 100% CPU. I've attached a screenshot of htop, as well as the open file handles for both the parent krunner process and one of the children using 100% CPU. Bug 364268 also seems to describe this problem, however I can confirm that the bug does not only happen when opening OpenGL apps. System specs: Kernel version: 4.8.13-1-ARCH plasma version: 5.8.5 kf5 version: 5.30.0 kapps version: 16.12.1 CPU: i5-4690K GPU: Nvidia GTX 970 with proprietary driver, version 375.26 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 375131] baloo hangs up forever when it reachs a corrupted file.
https://bugs.kde.org/show_bug.cgi?id=375131 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com --- Comment #1 from kafei <matthewisrip...@gmail.com> --- I believe I have also been hit by this bug. Today baloo_file_extractor suddenly started using 100% CPU and didn't stop. Running `balooctl status` gave the following output: Baloo File Indexer is running Indexer state: Idle Indexed 11547 / 11548 files Current size of index is 947.69 MiB Which looks to me like it's hung on a particular file, but I'm not sure how to figure out which file that is. The contents of /proc/baloo_file_extractor_pid/fd gave the following, which didn't seem to indicate the offending file: 0 -> pipe:[17073] 1 -> pipe:[17074] 10 -> anon_inode:inotify 11 -> /home/matt/.local/share/baloo/index 12 -> /home/matt/.local/share/baloo/index 13 -> /proc/1053/mounts 14 -> socket:[17086] 15 -> socket:[18879] 16 -> /home/matt/.local/share/baloo/index-lock 17 -> /home/matt/.local/share/baloo/index 18 -> /home/matt/.local/share/baloo/index 2 -> pipe:[17075] 3 -> socket:[17080] 4 -> anon_inode:[eventfd] 5 -> anon_inode:[eventfd] 6 -> socket:[17082] 7 -> socket:[17894] 8 -> anon_inode:[eventfd] 9 -> socket:[18877] Even after restarting, baloo_file_extractor immediately starts and hangs in the same way. The only way to stop it is to kill the process. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 --- Comment #4 from kafei <matthewisrip...@gmail.com> --- This bug appears fixed on my end in 5.8.4, I rebooted a few times and got my correct monitor configuration every time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369142] plasma crashed when i loging to system
https://bugs.kde.org/show_bug.cgi?id=369142 --- Comment #5 from kafei <matthewisrip...@gmail.com> --- It does not happen every time. After a couple of tries, I did get the crash to occur with the same characteristics as before (black right monitor) by starting plasmashell manually. However, when I managed to catch the same situation running plasmashell under valgrind it did not crash... It's possible the race doesn't occur when running under valgrind. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369142] plasma crashed when i loging to system
https://bugs.kde.org/show_bug.cgi?id=369142 --- Comment #3 from kafei <matthewisrip...@gmail.com> --- Created attachment 101696 --> https://bugs.kde.org/attachment.cgi?id=101696=edit plasmashell crash stack trace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369142] plasma crashed when i loging to system
https://bugs.kde.org/show_bug.cgi?id=369142 kafei <matthewisrip...@gmail.com> changed: What|Removed |Added CC||matthewisrip...@gmail.com --- Comment #2 from kafei <matthewisrip...@gmail.com> --- I can confirm this bug; after installing Linux 4.8.3 and rebooting, plasmashell crashed 3 times in a row. My right monitor was completely black except I could mouse over it, just like the description in Bug 370916. My stack trace is also very similar to the one in 370916, but differs slightly from the one in this report. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 --- Comment #2 from kafei <matthewisrip...@gmail.com> --- Created attachment 101636 --> https://bugs.kde.org/attachment.cgi?id=101636=edit After switching primary display to HDMI monitor and back to DP monitor -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 --- Comment #1 from kafei <matthewisrip...@gmail.com> --- Created attachment 101635 --> https://bugs.kde.org/attachment.cgi?id=101635=edit Desktop layout after reboot -- You are receiving this mail because: You are watching all bug changes.
