[plasmashell] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 --- Comment #12 from Massimo Callegari --- Without notifications, CPU usage is definitely at normal levels -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 --- Comment #10 from Massimo Callegari --- Which one is the notification widget and how do I remove it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 --- Comment #7 from Massimo Callegari --- > Are you using plasma-browser-integration? Yes, 5.16.0 Requested logs attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 --- Comment #6 from Massimo Callegari --- Created attachment 120981 --> https://bugs.kde.org/attachment.cgi?id=120981&action=edit dbus-monitor log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 --- Comment #5 from Massimo Callegari --- Created attachment 120980 --> https://bugs.kde.org/attachment.cgi?id=120980&action=edit plasmasheel log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 Massimo Callegari changed: What|Removed |Added Platform|Kubuntu Packages|Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 Massimo Callegari changed: What|Removed |Added Product|frameworks-knotifications |plasmashell Component|general |Task Manager Assignee|kdelibs-b...@kde.org|h...@kde.org CC||plasma-b...@kde.org Version|5.59.0 |5.16.0 Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 --- Comment #1 from Massimo Callegari --- For the record, the process eating up all the CPU is plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 408771] CPU @100% while downloading large files with Chrome
https://bugs.kde.org/show_bug.cgi?id=408771 Massimo Callegari changed: What|Removed |Added Summary|Download a large file keeps |CPU @100% while downloading |CPU @100% |large files with Chrome -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 408771] New: Download a large file keeps CPU @100%
https://bugs.kde.org/show_bug.cgi?id=408771 Bug ID: 408771 Summary: Download a large file keeps CPU @100% Product: frameworks-knotifications Version: 5.59.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: massimocalleg...@yahoo.it CC: kdelibs-b...@kde.org Target Milestone: --- I'm a bit surprised nobody reported this yet. It bothers me since months, but I can't really tell exactly from which Frameworks version. STEPS TO REPRODUCE 1. Open Google Chrome (my version is 75.0.3770.90, but any version will do) 2. go to a page where you can download a large file (e.g. https://download.qt.io/official_releases/qt/5.12/5.12.3/) 3. download a >1GB file 4. Enjoy your CPU going at 100% just to show a green bar progressing 5. (bonus) Enjoy your laptop ventilation going crazy for the whole download duration OBSERVED RESULT CPU cores going @100% EXPECTED RESULT A network download must not bother a CPU at all. There is clearly a bug in the notification system (in particular the progress bar system) where someone forgot to add a sleep call when polling the download progress. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.16 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 384561] Dolphin copy operation is 4,5x slower than cp
https://bugs.kde.org/show_bug.cgi?id=384561 --- Comment #18 from Massimo Callegari --- Hey guys, I have repeated both the initial tests: cp vs Dolphin KDE Plasma 5.12, KDE Frameworks 5.43.0, Qt 5.9.3, Dolphin 17.12.2 cp took 7 minutes, 31 seconds Dolphin took 9 minutes, 57 seconds Excellent result ! @Jaime Torres, thanks a lot again for looking into this. I'm pretty sure many users will appreciate this performance gain as much as I do ! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 384561] Dolphin copy operation is 4,5x slower than cp
https://bugs.kde.org/show_bug.cgi?id=384561 --- Comment #13 from Massimo Callegari --- First and foremost, @Jaime Torres: thanks a lot for looking into this ! > @Massimo: It would be nice as feedback, if the upcoming KDE Frameworks v5.43 > fixes this for you - just to be sure your problem is truly fixed :-) Will surely do. I tried to avoid flaming this thread, but now I'd like to clarify my comment #3. I never asked for a fix in 3 months. I am a (Qt) developer too and I know how this works. However, as a developer I try to quickly identify the real issues from the fake ones. In a few days/weeks I try at least to reproduce the issue and give it a priority. This way I know where I have to concentrate my efforts. Moreover if I'm working on something, I tend to forget everything else, so "marking" an issue with a priority helps my memory months later. What I complained about is that in 3 months no one changed the status of this issue to 'confirmed', meaning (to me) no one tried to reproduce it. This is the best way to loose an issue report that can help KDE to get better among other 27000+. And because of this, I found Nate's comment quite ridiculous: > There are currently 27,062 open bugs across all of KDE[1]. This seems like an > important one, to be sure, but it competes with 27,061 others. This means there is no priority assignment and all those 27062 bugs have the same weight. As for me fixing the issue...no way ! I already contributed to KDE many years ago (Kate's Symbol Viewer plugin is mine) and I know how difficult is even to prepare the KDE build environment. Plus, I am already swamped with my project issues, and I believe I already did my job -as user- by dedicating time to open this issue report as much accurately as possible. I am frustrated, yes, because I use KDE since 15 years and as a user it hurts me to see how Plasma is still not in shape, even after a dozen of minors. I see changelogs of new versions saying "new breeze theme, new panel design, etc" and it makes me angry when I know there are core issues to be fixed first. In conclusion, no harsh from my side. I know for sure there are excellent developers behind KDE that dedicate an awful amount of their personal time to this project. I only wish there could be a better priority system in place. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382812] Mouse icon artifacts block display of desktop content
https://bugs.kde.org/show_bug.cgi?id=382812 --- Comment #25 from Massimo Callegari --- @Morgan Cox I didn't say it's a solution. It's another dirty workaround to compensate a SDDM bug. Turns out XRender compositing affects VLC too which is pretty bad. Another 'workaround' is to use 'slim' instead of SDDM. I thought about opening a ticket in the SDDM GitHub page...but they have 200+ open issues and doesn't seem they care that much. I think SDDM should be abandoned for good. And I do totally understand your comment about Linux newbies. At the moment I don't feel suggesting Neon/Plasma to anyone either. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382812] Mouse icon artifacts block display of desktop content
https://bugs.kde.org/show_bug.cgi?id=382812 --- Comment #23 from Massimo Callegari --- Sorry, broken link. That should be https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382812] Mouse icon artifacts block display of desktop content
https://bugs.kde.org/show_bug.cgi?id=382812 --- Comment #22 from Massimo Callegari --- For the sake of it, and since restarting SDDM every time is VERY annoying, there's another workaround found here https://bugs.launchpad.net/ubuntu/+sour ... ug/1684240 - #16 Go to KDE System Settings -> Display and Monitor -> Compositor (left side) -> set "Rendering Backend" to XRender -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 384561] Dolphin copy operation is 4,5x slower than cp
https://bugs.kde.org/show_bug.cgi?id=384561 --- Comment #3 from Massimo Callegari --- Almost 3 months and nobody cares about this. No comments, no status change. No wonder why KDE is so buggy when developers don't actually listen to their software users. I use KDE since 15 years and instead of improving, KDE is degrading into something unusable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384561] Dolphin copy operation is 4,5x slower than cp
https://bugs.kde.org/show_bug.cgi?id=384561 --- Comment #2 from Massimo Callegari --- 2 weeks and no signs of life for such an epic bug. Wow. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384561] Dolphin copy operation is 4,5x slower than cp
https://bugs.kde.org/show_bug.cgi?id=384561 --- Comment #1 from Massimo Callegari --- I forgot to mention that the target filesystem is NTFS on an external USB 2 3.5" hard disk -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384561] New: Dolphin copy operation is 4,5x slower than cp
https://bugs.kde.org/show_bug.cgi?id=384561 Bug ID: 384561 Summary: Dolphin copy operation is 4,5x slower than cp Product: dolphin Version: 17.08.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: massimocalleg...@yahoo.it CC: elvis.angelac...@kde.org Target Milestone: --- KDE Neon 5.10, KDE Frameworks 5.37.0, Qt 5.9.1, Dolphin 17.08.0 Source filesystem: ext4 Target filesystem: NTFS Prepare a copy test folder with 5 large files like this: # mkdir copytest # cd copytest/ # for i in `seq -w 1 5`; do dd if=/dev/urandom of=file-$i.bin bs=1M count=4196; done # cd .. First observation: if Dolphin is open on 'copytest' during the above operation, it hangs until the operation is finished. Copy test folder with the cp command like this: # date; cp -r copytest/ /media/user/ExternUSBDrive/; sync; date On my PC I got: sun 10 sep 2017, 13.40.14, CEST sun 10 sep 2017, 13.47.36, CEST Total time: 7 minutes, 22 seconds Do the same operation with Dolphin: - right click on 'copytest' -> Copy - go to external USB drive - right click -> Paste - minimize Dolphin - don't do anything else and watch the green bar slowly progressing Total time: 31 minutes, 12 seconds The CPU usage is ridicolous too: cp stays around 20%, while Dolphin stays around 40% This is an example with just 20GB of data, which is nothing nowadays. Sometimes it occurs to me to copy 150GB of data, which would mean something like 53 minutes (cp) against more than 4 hours (Dolphin) I suspect there is a severe issue with KDE filesystem watchers, which is the only thing that can make the difference in such a basic operation where you just need to do fread -> fwrite. However, I'd expect that minimizing Dolphin would disable every FS watcher. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382812] Mouse icon artifacts block display of desktop content
https://bugs.kde.org/show_bug.cgi?id=382812 --- Comment #13 from Massimo Callegari --- (In reply to Martin Flöser from comment #10) > Please stop reporting further comments in this report. THIS IS A BUG CAUSED > BY THE UPDATE OF THE NVIDIA DRIVER! IT IS NOT A BUG IN OUR SOFTWARE! > > Reporting here just doesn't reach those who could fix it. > > Thank YOU! Instead, writing in caps will help to fix the issue, will it ? I confirm this has nothing to do with nVidia drivers, and I suspect too this has been caused by xserver-xorg-core-hwe (just checked my logs) In any case, as I stated before, Gnome didn't suffer from this update, while KDE (or sddm) did. And again, as KDE Neon users, where else would we report this issue ? YOU guys provide KDE Neon. YOU take the responsibility for the mess that untested package deliveries cause to your users. Otherwise everybody in this world would be able to make a distro and then point the finger when things go wrong. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382812] Mouse icon artifacts block display of desktop content
https://bugs.kde.org/show_bug.cgi?id=382812 Massimo Callegari changed: What|Removed |Added CC||massimocalleg...@yahoo.it --- Comment #5 from Massimo Callegari --- Guys, I have the same exact issue and I have no idea why you keep on saying this is "resolved". (https://bugs.kde.org/show_bug.cgi?id=382865) Gnome works perfectly on the same computer, with the same Xorg and nVidia drivers. This is clearly a KDE bug appeared a few days ago, most likely after an Xorg update. Note that I am using KDE Neon too, so isn't the Neon team responsible to test and certify upstream packages before delivering them to the masses, to guarantee a consistent KDE experience ? Or are we really left to ourselves even on a KDE product ? For the record, this issue makes it impossible to use KDE, so I am using Gnome these days, which is disgusting for me after 15 years of KDE. You're really letting us down with this "point the finger" game. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382865] weird mouse cursors
https://bugs.kde.org/show_bug.cgi?id=382865 --- Comment #7 from Massimo Callegari --- Gnome works perfectly. Same computer, same video driver. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382865] weird mouse cursors
https://bugs.kde.org/show_bug.cgi?id=382865 --- Comment #5 from Massimo Callegari --- Been able to capture a full screenshot with mouse cursor. I was just Alt-tabbing between windows -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382865] weird mouse cursors
https://bugs.kde.org/show_bug.cgi?id=382865 --- Comment #4 from Massimo Callegari --- Created attachment 106938 --> https://bugs.kde.org/attachment.cgi?id=106938&action=edit With mouse cursor -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382865] weird mouse cursors
https://bugs.kde.org/show_bug.cgi?id=382865 --- Comment #3 from Massimo Callegari --- Created attachment 106928 --> https://bugs.kde.org/attachment.cgi?id=106928&action=edit Beautiful KDE -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382865] weird mouse cursors
https://bugs.kde.org/show_bug.cgi?id=382865 --- Comment #2 from Massimo Callegari --- This is happening to me too after an update 2 days ago. It seems related to the hardware cursor back buffering. If I try to capture a screenshot with mouse cursor included, the issue can't be seen. The attached screenshot shows an unwanted rectangle displayed after I scrolled the list up. Needless to say this is seriously annoying and it happens constantly, on every mouse move Dell Inspiron 15 7000 series. Nvidia GeForce GTX 960M card. KDE Neon 5.10. Plasma 5.10.4, Frameworks 5.36.0, Qt 5.9.1, Kernel 4.10.0. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382865] weird mouse cursors
https://bugs.kde.org/show_bug.cgi?id=382865 Massimo Callegari changed: What|Removed |Added CC||massimocalleg...@yahoo.it --- Comment #1 from Massimo Callegari --- Created attachment 106927 --> https://bugs.kde.org/attachment.cgi?id=106927&action=edit Mouse cursor issue -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 364849] Tooltip Text in several qt apps such as Amarok and Krusader is unreadable (white on white) with the Breeze/Breeze Dark color schemes
https://bugs.kde.org/show_bug.cgi?id=364849 Massimo Callegari changed: What|Removed |Added CC||massimocalleg...@yahoo.it --- Comment #4 from Massimo Callegari --- Same here. KDE Neon LTS, vanilla settings (default Breeze theme) All GTK apps (e.g. FileZilla, Inkscape) have white on light gray tooltips, making it impossible to understand what toolbar icons do. Screenshot: http://pasteboard.co/Lj6iwlO7E.png -- You are receiving this mail because: You are watching all bug changes.
