[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 --- Comment #18 from whoopsdecade --- (In reply to whoopsdecade from comment #14) > For the record I haven't had this error in a while. Currently on > plasmashell 5.27.1 > Qt: 5.15.8 > KDE Frameworks: 5.103.0 > kf5-config: 1.0 > KDE Connect 1.22.1 (Android) Forgot to add: Android 10 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 --- Comment #14 from whoopsdecade --- For the record I haven't had this error in a while. Currently on plasmashell 5.27.1 Qt: 5.15.8 KDE Frameworks: 5.103.0 kf5-config: 1.0 KDE Connect 1.22.1 (Android) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 452970] Powerdevil is not respecting 'Screen energy saving' and 'Suspend session' settings
https://bugs.kde.org/show_bug.cgi?id=452970 --- Comment #2 from whoopsdecade --- (In reply to Nate Graham from comment #1) > Screen locking is separate from going to sleep automatically. You can adjust > the screenlocking time in System Settings > Workspace Behavior > Screen > Locking. > > Does that help? It seems those settings can contradict each other. You're right, it seems the screen was getting locked by the 'Screen Locking' before the Powerdevil settings came into play. Perhaps it would be helpful if one or the other screen informed you of this inside the settings manager? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 452970] New: Powerdevil is not respecting 'Screen energy saving' and 'Suspend session' settings
https://bugs.kde.org/show_bug.cgi?id=452970 Bug ID: 452970 Summary: Powerdevil is not respecting 'Screen energy saving' and 'Suspend session' settings Product: Powerdevil Version: 5.24.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jcdop...@gmail.com Target Milestone: --- SUMMARY For a couple of releases now I've been noticing that Powerdevil is not respecting 'Screen energy saving' and 'Suspend session' settings. It doesn't seem to matter how many minutes I set under 'Switch off after' and 'Automaticallt [lock screen] after' respectively. It always seems to switch/lock the screen off after 5 or so minutes. STEPS TO REPRODUCE 1. Change the 'Screen energy saving' and 'Suspend session' settings to a very high amount of minutes say 30 2. Stop interacting with your desktop OBSERVED RESULT Screen turns off/locks after around 5 minutes ignoring your setting. EXPECTED RESULT Screen should turn off/lock after 30 minutes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 plasmashell 5.24.3 Qt: 5.15.2 KDE Frameworks: 5.91.0 kf5-config: 1.0 ADDITIONAL INFORMATION I saw bug #357288 which seems very similar marked as RESOLVED FIXED, doesn't seem like it is for me. Let me know if it's better to reopen that one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #42 from whoopsdecade --- I don't seem to be getting this memory leak on Fedora 34, KDE info: Qt: 5.15.2 KDE Frameworks: 5.85.0 kf5-config: 1.0 BUT I also changed machines to a 11gen Intel i7 w/ Xe graphics from an 8th gen i7 so who knows if that has anything to do with it but with an uptime of 31 days, with close to the same use, plasmashell has never gone over 350m in memory. Sitting at 281M now so it's fluctuating depending on use which it's good. One less thing to worry about :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #37 from whoopsdecade --- @Iyán: why don't you drop the snark and run heaptrack yourself? I already did my bit. Or just keep running interference for the KDE team here, that will surely help solve the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #33 from whoopsdecade --- Btw, the workaround I've been using is setting up a script to run every couple of days or so to restart plasmashell automatically: kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell It's not as traumatic as other options to restart plasmashell that I tried. Your windows get reordered and that's about it. I can't even tell when it ran and it keeps plasmashell memory usage in check. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #32 from whoopsdecade --- Unfortunately the KDE team is not interested in even acknowledging this issue. I think they know of this bug and can reproduce it easily they just don't want to acknowledge it. I managed to get a co-worker to reproduce it on his own machine with no knowledge of his setup, I simply told him to not power-off his machine for several days and the memory leak was very apparent: plasmashell memory consumption ballooned. In short, it's a widespread memory leak but either very few people use KDE or very few use KDE and leave the PC powered on for more than a single day. Such a shame. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435618] Plasmashell crashes when clicking a widget in the system notification area
https://bugs.kde.org/show_bug.cgi?id=435618 --- Comment #2 from whoopsdecade --- Created attachment 137514 --> https://bugs.kde.org/attachment.cgi?id=137514=edit corebacktrace from crash report tool I added the corebacktrace I copied out of the crash report tool. Is that what you mean? You guys ask for stuff but never point someone to how to get it. I'm not sure an average user would know how to fish out some of the stuff you ask for sometimes. Is there a wiki somewhere with that information? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435618] New: Plasmashell crashes when clicking a widget in the system notification area
https://bugs.kde.org/show_bug.cgi?id=435618 Bug ID: 435618 Summary: Plasmashell crashes when clicking a widget in the system notification area Product: plasmashell Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jcdop...@gmail.com Target Milestone: 1.0 SUMMARY Very often, usually when I'm playing music (rhythmbox) and I click the plasma notification tray area (can be the mmedia player system tray widget or just the network widget) plasmashell crashes and restarts. STEPS TO REPRODUCE 1. Play music (not sure if this is necessary). 2. Click the media player system tray widget for info about song playing or player control. 3. Do this every once in a while OBSERVED RESULT plasmashell crashes and restarts again. EXPECTED RESULT Current player information. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 32 plasmashell 5.18.5 Qt: 5.14.2 KDE Frameworks: 5.75.0 kf5-config: 1.0 ADDITIONAL INFORMATION User Logs (from the crash tool): --Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: file:///usr/lib64/qt5/qml/org/kde/plasma/components.3/ComboBox.qml:138:13: Unable to assign [undefined] to QQmlComponent* Apr 11 11:21:58 inspiron plasmashell[473440]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:140:25: Unable to assign [undefined] to int Apr 11 11:21:58 inspiron plasmashell[473440]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:132: TypeError: Value is undefined and could not be converted to an object Apr 11 11:21:58 inspiron plasmashell[473440]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:154:25: Unable to assign [undefined] to bool Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:21:58 inspiron plasmashell[473440]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:22:00 inspiron plasmashell[1741268]: kf.coreaddons: Expected JSON property "X-Plasma-ContainmentCategories" to be a string list. Treating it as a list with a single entry: "panel" org.kde.plasma.desktop.defaultPanel Apr 11 11:22:00 inspiron plasmashell[1741268]: kf.coreaddons: Expected JSON property "X-Plasma-ContainmentCategories" to be a string list. Treating it as a list with a single entry: "panel" org.kde.plasma.desktop.emptyPanel Apr 11 11:22:00 inspiron plasmashell[1741268]: kf.coreaddons: Expected JSON property "X-Plasma-ContainmentCategories" to be a string list. Treating it as a list with a single entry: "panel" org.kde.plasma.desktop.appmenubar Apr 11 11:22:00 inspiron plasmashell[1741268]: kf.plasma.quick: Applet preload policy set to 1 Apr 11 11:22:00 inspiron plasmashell[1741268]: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated Apr 11 11:22:00 inspiron plasmashell[1741268]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:430:13: QML ToolButton: Binding loop detected for property "icon.height" Apr 11 11:22:00 inspiron plasmashell[1741268]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:410:17: QML ToolButton: Binding loop detected for property "icon.height" Apr 11 11:22:00 inspiron plasmashell[1741268]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:397:17: QML ToolButton: Binding loop detected for property "icon.height" Apr 11 11:22:00 inspiron plasmashell[1741268]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:384:17: QML ToolButton: Binding loop detected for property "icon.height" Apr 11 11:22:00 inspiron plasmashell[1741268]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:371:17: QML ToolButton: Binding loop detected for property "icon.height" Apr 11 11:22:00 inspiron plasmashell[1741268]:
[plasma-pa] [Bug 434170] Volume keys do not push volume to 150%
https://bugs.kde.org/show_bug.cgi?id=434170 --- Comment #4 from whoopsdecade --- >ostensibly to make it easier to find. :) Isn't it always -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 434170] Volume keys do not push volume to 150%
https://bugs.kde.org/show_bug.cgi?id=434170 --- Comment #2 from whoopsdecade --- Seems like the setting I was looking for was moved. Now it's on the tray widget as a checkbox titled "Raise maximum volume" I can reach 150% volume after enabling that. -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 434170] New: Volume keys do not push volume to 150%
https://bugs.kde.org/show_bug.cgi?id=434170 Bug ID: 434170 Summary: Volume keys do not push volume to 150% Product: pulseaudio-qt Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: jcdop...@gmail.com Target Milestone: --- Not sure if this is where this bug should go. I looked over the sections and this one seemed the closest. SUMMARY Volume keys do not respect the volume limit set in the "configure audio volume" screen. STEPS TO REPRODUCE 1. go to "configure audio volume" screen (right click sound icon in the tray area). 2. set the volume to 130% or any percentage past 100%. 3. increase the volume using your laptop's volume keys. OBSERVED RESULT Volume level is automatically decreased to 100% and won't go above that. EXPECTED RESULT Volume level should go over 130% (or whatever percentage you set) until it reaches the maximum of 150%. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 KDE plasmashell 5.20.5 Qt: 5.15.2 KDE Frameworks: 5.79.0 kf5-config: 1.0 ADDITIONAL INFORMATION Upgraded from Fedora 32 KDE. Any workarounds would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #28 from whoopsdecade --- Heaptrack finished, I uploaded the new file to the same dropbox url. The end result was 433.63MB! Is that normal? Heaptrack was taking too long so I did put the laptop to sleep in between, not sure if that had an effect. Plasmashell was consuming 1.3GB by the end of the heaptrack. In any case, it's here: https://www.dropbox.com/s/6u6q6ato6jr2k7o/heaptrack.plasmashell.495556.gz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #27 from whoopsdecade --- RE: heaptrack file. The rendering backend is set to software and it's been that way since it was recommended here, just got around to doing the heaptrack. Throughout this time I saw plasmashell leak memory just the same as before, maybe leaking at a lower rate but leaking nonetheless. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #26 from whoopsdecade --- The plasmashell process is consuming 1.1GB right now with system uptime of 20 days. The plasmashell memory consumption just keeps increasing, steadily, over time denoting a memory leak as reported. I have never seen it consume something as dramatic as 7gb in 5 days but it's clear to me if I don't restart the session for 120 days it could get close to that (if plasmashell doesn't restart itself as it does every now and then :sigh:). The heaptrack was uploaded here https://www.dropbox.com/s/6u6q6ato6jr2k7o/heaptrack.plasmashell.495556.gz since even compressed it's around 52MBs. It encompasses a couple of hours. Please note that heaptrack is still running but I don't know if it is supposed to finish by itself or if it's just going to keep running while the process is still going. Please let me know so I can kill it or leave it running for longer if you need me to. If you need anything else please just let me know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 whoopsdecade changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #25 from whoopsdecade --- I set the backend to software and I'm still seeing continuous increase in memory consumption from plasmashell. This is after reinstalling OS.. these are my libraries now: plasmashell 5.18.3 Qt: 5.13.2 KDE Frameworks: 5.68.0 kf5-config: 1.0 I'll try to compile heaptrack and post that in the following days. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] New: Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 Bug ID: 419897 Summary: Error when accessing filesystem. sshfs finished with exit code 1 Product: kdeconnect Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: jcdop...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Pair device 2. Enable file permissions on Android device 3. Try to browse file system from Dolphin OBSERVED RESULT "Error when accessing filesystem. sshfs finished with exit code 1" EXPECTED RESULT Browsing the filesystem on my phone. SOFTWARE/OS VERSIONS Android: Oreo Linux/KDE Plasma: Fedora 32 plasmashell 5.18.3 Qt: 5.13.2 KDE Frameworks: 5.68.0 kf5-config: 1.0 ADDITIONAL INFORMATION I can see the folders I enabled on the kdeconnect android app but when I try to browse them I get the aforementioned error. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #20 from whoopsdecade --- I'm on a Dell Inpsiron 15 Intel i7-8550U for what it's worth. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #17 from whoopsdecade --- (In reply to Iyán Méndez Veiga from comment #16) > KDE Plasma: 5.18.2 > KDE Frameworks: 5.67.0 > Qt: 5.14.1 > Kernel: 5.5.5 Can you post the massif output? It would help them debug this. PD: I seriously don't know why they seem to be ignoring this... I'm sure this issue is widespread but people stay mum or just don't pay attention until you have a popular publication write an article on it (like the gnome a few years ago). -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 416142] New: Getting error message saying: "Sign in with Google temporarily disabled for this app"
https://bugs.kde.org/show_bug.cgi?id=416142 Bug ID: 416142 Summary: Getting error message saying: "Sign in with Google temporarily disabled for this app" Product: kio-gdrive Version: 1.2.7 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: jcdop...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. add a @gmail.com account OBSERVED RESULT Error message saying: "Sign in with Google temporarily disabled for this app. This app has not been verified yet by Google in order to use Google Sign In." EXPECTED RESULT My Drive account being added. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: plasmashell 5.15.5 Qt: 5.12.5 KDE Frameworks: 5.64.0 kf5-config: 1.0 ADDITIONAL INFORMATION First time setting Drive under KDE. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #14 from whoopsdecade --- Current KDE info: plasmashell 5.15.5 Qt: 5.12.5 KDE Frameworks: 5.59.0 kf5-config: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 whoopsdecade changed: What|Removed |Added Attachment #112455|0 |1 is obsolete|| Attachment #112730|0 |1 is obsolete|| Attachment #112931|0 |1 is obsolete|| --- Comment #13 from whoopsdecade --- Created attachment 124118 --> https://bugs.kde.org/attachment.cgi?id=124118=edit massif output 3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 whoopsdecade changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #12 from whoopsdecade --- I updated KDE and I'm still experiencing what seems like a memory leak. Which was expected because I do not use the extension linked to the previous bug someone mentioned.. anyways, I'm attaching a new massif output. Please check it out. Plasmashell is sitting at 1.2GB from an initial <200MB and it just keeps going up and up. It's kept happening all this while btw I just had not posted anything. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407305] A bunch of "unused" sessions after login in and out of an account while leaving one open in the background
https://bugs.kde.org/show_bug.cgi?id=407305 --- Comment #3 from whoopsdecade --- Sometimes when I try to go back to the previous user the screen just stays blank, no login occurs and it just hangs there and I have to force-restart my machine. Changing user sessions is basic guys and it has always been very unreliable in Plasma, you need to figure this out. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407305] A bunch of "unused" sessions after login in and out of an account while leaving one open in the background
https://bugs.kde.org/show_bug.cgi?id=407305 whoopsdecade changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407305] A bunch of "unused" sessions after login in and out of an account while leaving one open in the background
https://bugs.kde.org/show_bug.cgi?id=407305 whoopsdecade changed: What|Removed |Added CC||jcdop...@gmail.com --- Comment #2 from whoopsdecade --- Created attachment 121486 --> https://bugs.kde.org/attachment.cgi?id=121486=edit Unused sessions It's not resolved yet. This screenshot is from today on Plasma 5.15.5. I've also had it happen several times before. It eventually cleans up but it's not predictable.. and if I select one of the "unused" sessions the session might never log the second user in (remains loading the desktop, blank screen) and I have to use the hotkey to get back to the first user and kill the other users processes. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 407305] New: A bunch of "unused" sessions after login in and out of an account while leaving one open in the background
https://bugs.kde.org/show_bug.cgi?id=407305 Bug ID: 407305 Summary: A bunch of "unused" sessions after login in and out of an account while leaving one open in the background Product: ksmserver Version: 5.14.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ui Assignee: unassigned-b...@kde.org Reporter: jcdop...@gmail.com Target Milestone: --- SUMMARY Logging in and out of a session while leaving a second one "locked" creates a bunch of "unused" sessions. STEPS TO REPRODUCE 1. Login to account A and switch users (should stay in background 2. Log in to account B and then log out 3. Open account A once again and switch users, you will see an "unused" session in the menu. 4. Repeat the same process N times and you will get N "unused" sessions. OBSERVED RESULT https://i.imgur.com/vS4MOWD.jpg EXPECTED RESULT Just switching users with no "unused" sessions. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.55.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION I'm Fedora 29 KDE spin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 whoopsdecade changed: What|Removed |Added CC|jcdop...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393912] The Activities switcher steal the focus after I switch using meta+tab and after that it does not autohide
https://bugs.kde.org/show_bug.cgi?id=393912 --- Comment #14 from whoopsdecade --- (In reply to Thomas Surrel from comment #4) > Oops, I meant to provide more information with the attached patch. I will > try to get that upstream but in the meantime you can apply the patch to the > Desktop.qml file (you don't need to recompile anything). On ArchLinux you > can find it under > /usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/. > > Please confirm that fixes the issue for you as well. btw after applying this fix "Move to activity" (right click on window item on the bottom panel) stopped working. Don't know why. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 --- Comment #14 from whoopsdecade --- Does Dolphin keep track of "rows" of items? It should scroll the rows and make sure full rows get scrolled. As it is some lose visibility between scrolls. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #8 from whoopsdecade --- In reply to Christoph Feck from comment #7) > Is this massif output created with Qt 5.11? Infocenter says Qt is 5.9.4. I'm on Fedora 27. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 whoopsdecade changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #6 from whoopsdecade --- Created attachment 112931 --> https://bugs.kde.org/attachment.cgi?id=112931=edit massif output 2 Added a new log. This one was generated a coupe of hours after the first one I posted but I forgot to attach it here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #5 from whoopsdecade <jcdop...@gmail.com> --- (In reply to David Edmundson from comment #2) > In any case I can't do anything with a screenshot of a sysetm monitor. > > It's probably 368838. Please retest with Qt5.11. If you still have an issue > please upload a log from massif. I added a massif output. I restarted my computer since I first reported the problem. The plasmashell process has been increasing its memory consumption steadily as expected and it's now claiming 647k of memory, if I don't restart the computer it's clear it will go over 1gb of ram soon. Let me know if you would need any more information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #4 from whoopsdecade <jcdop...@gmail.com> --- Created attachment 112730 --> https://bugs.kde.org/attachment.cgi?id=112730=edit massif output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 --- Comment #3 from whoopsdecade <jcdop...@gmail.com> --- (In reply to Rex Dieter from comment #1) > Do you use slideshow wallpaper? No, I do not. (In reply to David Edmundson from comment #2) > It's probably 368838. Please retest with Qt5.11. If you still have an issue > please upload a log from massif. I don't think it's 368838 since I don't use the slideshow addon. Where can I read up on how to get a massif log? Been out of the country so I haven't been able to follow up on this as I should I apologise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] New: Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 Bug ID: 393929 Summary: Plasmashell gobbles all my memory leak Product: plasmashell Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jcdop...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112455 --> https://bugs.kde.org/attachment.cgi?id=112455=edit System monitor Plasmashell keeps on consuming more and more of my RAM and it never lets go of any of it (see attachment). Right now I'm on Fedora 27 and this happens on every session, very predictable. I usually do not turn off my laptop, I just suspend it (My uptime right now is 11 days). I had the same issue happen on a different laptop before I upgraded to the one I currently have (I've only been using Fedora and KDE for the last two months, longtime ubuntu user before). I use no widgets other than whatever comes by default with Fedora. People say that Plasmashell should only need around 400MB, mine has gone past the 1gb mark before so something must not be right. A screenshot it's probably not enough to report this kind of issue, just let me know what do I need to get and I will get it and attach it to the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393912] New: The Activities switcher steal the focus after I switch using meta+tab and after that it does not autohide
https://bugs.kde.org/show_bug.cgi?id=393912 Bug ID: 393912 Summary: The Activities switcher steal the focus after I switch using meta+tab and after that it does not autohide Product: plasmashell Version: 5.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Activity Switcher Assignee: ivan.cu...@kde.org Reporter: jcdop...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 The Activities switcher steal the focus after I switch using meta+tab and after that it does not autohide, I have to click on the activities switcher and then on the desktop for it to go away. This is very annoying to me because I actually want to do away with that animation entirely but I was getting used to it hiding right after I switched. Now I have to contend with the activity switcher actually getting in the way after I switch. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392363] Mouse wheel scroll is too fast
https://bugs.kde.org/show_bug.cgi?id=392363 --- Comment #2 from whoopsdecade <jcdop...@gmail.com> --- Created attachment 111662 --> https://bugs.kde.org/attachment.cgi?id=111662=edit after scrolling -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392363] Mouse wheel scroll is too fast
https://bugs.kde.org/show_bug.cgi?id=392363 --- Comment #1 from whoopsdecade <jcdop...@gmail.com> --- Created attachment 111661 --> https://bugs.kde.org/attachment.cgi?id=111661=edit before scrolling -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392363] New: Mouse wheel scroll is too fast
https://bugs.kde.org/show_bug.cgi?id=392363 Bug ID: 392363 Summary: Mouse wheel scroll is too fast Product: dolphin Version: 17.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: jcdop...@gmail.com Target Milestone: --- When scrolling using a USB wireless mouse' scrolling wheel Dolphin scrolls way too fast. The smallest scroll is enough to scroll all the items out of view sometimes. It feels like it's doiing "paged" scrolling with just a single, small move of the scrolling wheel. Not sure if this is normal behavior or not (using KDE seriously for the first time in years). But even if it is 'paged' scrolling by design it's not doing it correctly because sometimes some items that fall between the current "page" and the next are never shown in either the current or next page, like they just fall through the crack. Difficult to reproduce but it happens. I posted two screens here one before scrolling and the other one after scrolling (didn't seem to be able to attach more than one screenshot to the bug): https://imgur.com/a/ogWre -- You are receiving this mail because: You are watching all bug changes.
