[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #6 from William --- This bug happens on all configs (row / clolumn) align fixed positions, doesnt matter. The icons change position and wanna be in a different state than the one saved in the appletrc "positions=" line. YES if u restart plasmashell and dont have the file in readOnly mode that line gets rewritten, but even if u put it in readOnly the icons shift and the config file shows different positions that those displayed on the desktop. There is only 1 screen at all times and no the scramble does not follow alphabethical order or reverse or anything like that... when in row alignment (with manual sorting) icons in a column: turn into some sort of staircase with only the upper left staying where it was AA B -> B C C Also there is no "[ScreenConnectors]" section in the ~/.config/plasmashellrc file. As i said on new user it is not reproducable immediatly, just when u start using that user after a while soemthing happens (mb plasma crashes or doesnt shutdown properly or smthing) and after that icon scrambles happen almost everytime plasmashell is restarted. I backed up the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file from fresh user where it did not happen, when it started happening i replaced it with the backup, that did NOT fix it either: the icons keep scrambling every restart. Mb its note worthy but the desktop in question always uses "large" label width for the icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #13 from William --- (In reply to Uwe Dippel from comment #12) > Are we now running into something else, or am I at the wrong report? Earlier > we were at 'scrambled at reboot' AFAIK. Now we are at Plasmashell Start? > I still experience the 'at reboot' st times. Like today, see attachment. > Everything in 'Desktop' plus my desktop icons are placed in a wrapped > fashion above the default desktop background (see attachment). > Then I have to 'Customize Layout', add the PlasmaConfigSaver and restore to > my last saved desktop layout (see attachment). > > Please, inform me if this is not the appropriate bug, and the 'RESOLVED > CLOSED' (LOL) original was reopened elsewhere, thanks. this is the correct bug report, i just named it "on plasmashell start" as that is precisly what is happening during reboot, relogin or via commands, the part in question is the plasmashell startup that messes things up. Mb u can run the command "kquitapp5 plasmashell && kstart5 plasmashell" and see if it happnes to u with that aswell. Anyways the old report was closed and u are right here, welcome to the a bug that is now 7 years old, twice marketed as fixed and still some process during startup does not respect icon positions and on top of all also tries overwrites a users config file that it shouldnt ever even attempt to write to. here is to another 6 years of noone bothering to fix the most important issue in KDE plasma and why windows users wont switch, quote "if it cant even remember my desktop icons i cant trust it to store anything, even if microsoft collects all my data at least it does know how to store stuff lol" try to install xfce or zorinOS if u dont want to scare them away. kde just doesnt prioritize this kind of stuff - every other company wouldve had complete featurefreeze and stopped all further coding till this is fixed but opensource u cant do that so every1 just does what he likes to do. even throwing money at this thing does nothing,... i guess i have to learn coding and fix it myself, even if that takes 3 years it probably is faster -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #29 from William --- do desktop dimensions also change during plasmashell startup? the MergeRequest https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2118 indeed sounds pormising but lets pls not close the bug until it is fixed for sure. This issue occured on all gpus all monitors (single or multi monitor) and all distributions (i tried quite a bit of KDE installs), it is 100% reproducable with the posted plasmashell restart commands (so not only during KDE startup, just plasmashell startup im still baffled how its hard to reproduce while it happens to me every KDE install ever within a week of using it, nothing special (no power user stuff or customizations). I know how to install latest KDE Neon unstable if it lands there i can check it if i have the time otherwise idk how to verify early if this MR would help -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 William changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #71 from William --- (In reply to Nate Graham from comment #70) > Please stop changing the status to VERIFIED despite not verifying the fix. > I'd like William to do that, since he's the one who reported this issue. Sry i didnt keep up with what was happening in this isssue and i only recently got the 5-27 update in manjaro stable. But i am happy to report now that it doesnt happen anymore for me. i removed my "read-only" workaround script and used the command "kquitapp5 plasmashell && kstart5 plasmashell" at least 50 times in a row, which previously would always result in some form of icon scramble, but this time it did not. Good job to whatever was done in the end that fixed it. 5.27 seems like a great release! PS: manjaro skipped the early point releases and went straight to plasma 5.27.3. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468453] New: Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 Bug ID: 468453 Summary: Installed and am trying to setup KDE connect. Classification: I don't know Product: kde Version: unspecified Platform: Microsoft Windows OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bwett...@gmail.com Target Milestone: --- Created attachment 158058 --> https://bugs.kde.org/attachment.cgi?id=158058&action=edit scrn shot of KDE connect SUMMARY See attached screen shot. As you see, KDE does not know my computer. I tried typing in my computer name but KDE will not let me type the letter B *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 --- Comment #1 from William --- I opened a command prompt and tried your troubleshooting commands. Check that the process is listening on the network: sudo netstat -tunelp | grep -i kdeconnect error: sudo is not a recognized command Are the ports open/blocked? netcat -z -v 1714-1764 error: cannot find file I opened the ports to no avail. Same results -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 William changed: What|Removed |Added CC||bwett...@gmail.com --- Comment #2 from William --- Created attachment 158059 --> https://bugs.kde.org/attachment.cgi?id=158059&action=edit scrn shot of KDE connect I rebooted both the computer and the phone with slightly better results...but serious problems still remain. See screen shot 2. As that shows, the phone and computer connected, but all the words are gibberish --words are missing letters. I also discovered that if I try to edit the computer name, then only about half the keys on my keyboard are detected. I want this to work so that I can send SMS messages from my Windows 10pro laptop. Is that possible. Currently, i do not see that function is available. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 --- Comment #3 from William --- Created attachment 158085 --> https://bugs.kde.org/attachment.cgi?id=158085&action=edit scrn shot of KDE connect After the initial install failed to connect, I rebooted both the computer and the phone with slightly better results...but serious problems still remain. The phone and computer connected, but all the words are gibberish --words are missing letters. I also discovered that if I try to edit the computer name, then KDE only detects about half the keys on my keyboard. I want this to work so that I can send SMS messages from my Windows 10pro laptop. Is that possible. Currently, i do not see that function is available. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 William changed: What|Removed |Added Attachment #158058|0 |1 is obsolete|| Attachment #158059|0 |1 is obsolete|| Attachment #158085|0 |1 is obsolete|| --- Comment #4 from William --- Created attachment 158088 --> https://bugs.kde.org/attachment.cgi?id=158088&action=edit scrn shot not relevant After the initial install failed to connect, I rebooted both the computer and the phone with slightly better results...but serious problems still remain. The phone and computer connected, but all the words are gibberish --words are missing letters. I also discovered that if I try to edit the computer name, then KDE only detects about half the keys on my keyboard. I want this to work so that I can send SMS messages from my Windows 10pro laptop. Is that possible. Currently, i do not see that function is available -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 William changed: What|Removed |Added Version|6.0.0 |6.1.0 --- Comment #7 from William --- bump: still a problem in plasma 6.1: breaking all dark color-schemes -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 482202] New: Elisa: Improve Tray Icon
https://bugs.kde.org/show_bug.cgi?id=482202 Bug ID: 482202 Summary: Elisa: Improve Tray Icon Classification: Applications Product: Elisa Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: wi11ia...@pm.me Target Milestone: --- Almost all apps that include a minimize to sys-tray option show up in the sys-tray always or include an option to do so. This way the app can be minimized to tray not just by pressing close but also by pressing on the sys-tray icon. (like telegram for example) To make the best music player on KDE even better pls add an option to always show tray icon and let user toggle the state by clicking it. STEPS TO REPRODUCE 1. Open Elisa Settings 2. Activate Sys-tray icon when window is closed OBSERVED RESULT sys-tray icon only shows when closed EXPECTED RESULT add another option below the sys-tray activation that activates the sys-tray icon always. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 482202] Elisa: Improve Tray Icon
https://bugs.kde.org/show_bug.cgi?id=482202 --- Comment #1 from William --- after reporting found this bug from 2021: https://bugs.kde.org/show_bug.cgi?id=434560 with a potential fix already, wondering why that was not applied. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 William changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from William --- bump: discover settings page is the only thing that seems to be affected. is the SwipeListItem not used anywhere else? And why cant discover set the normal default background overwritting whatever kirigami sets as the standard? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #6 from William --- because the current background color comes from out of nowhere and cannot be configured in kde color-scheme settings. thats bad, but if a fix in Kirigami takes more effort/ time why not do what was done in qt5 and use the normal background color that is used everywhere else and can be configured? the color looks out of place in any color scheme even breeze default and is nowhere to be found in the color-scheme file. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484279] New: background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 Bug ID: 484279 Summary: background color used in settings leads to bad contrast Classification: Applications Product: Discover Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: wi11ia...@pm.me CC: aleix...@kde.org Target Milestone: --- Created attachment 167624 --> https://bugs.kde.org/attachment.cgi?id=167624&action=edit picture of discover settings SUMMARY The Settings page in Discover uses a new background color for the row, which is generated from the color-schemes [Colors:Window] -> BackgroundNormal value, this however does not work properly for very dark themes, e.g. pure black window color leads to white text on almost white background. STEPS TO REPRODUCE 1. Use color-scheme Breeze-Dark 2. Change Window-background color to pure-black #00 3. Open Discover Settings OBSERVED RESULT Settings almost unreadable, background color is almost white. EXPECTED RESULT The colors from my color-scheme should not be "manipulated" and the background should just be black. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #1 from William --- Created attachment 167625 --> https://bugs.kde.org/attachment.cgi?id=167625&action=edit color-scheme -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #2 from William --- Added color-scheme (default breeze-dark with only one color changed to black). Why does a white-greyish color (#BEBEBE) when changing a color to black. It is impossible to change this color without also changing the window-background of lets say the calculator app, Maybe there should be an option to set this color specifically in the color-scheme (where #BEBEBE wich is 190,190,190 in dez) is never even present. Anyways somehow the behind-the-options stuff that generates this color is not working properly for dark colors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage
https://bugs.kde.org/show_bug.cgi?id=425271 William changed: What|Removed |Added CC||thegpugene...@gmail.com --- Comment #30 from William --- I am experiencing the same issue with Nextcloud and Firefox when I stop the compositor. The moment the compositor is stopped, Xorg process pins CPU at 100% and xembedsniproxy goes to approximately 65%, with the logs spamming the same message, xembedsniproxy: Container window visible, stack below. This locks up the system - htop updates once every 30 seconds at best, Firefox and Discord freeze completely, and any game running freezes as well. If a terminal is not already open and selected for me to rectify (by restarting the compositor), the system must be forcibly rebooted. I discovered this issue with Lutris - its disable compositor option froze my system. This isn't 100% reproducible for me, for example I just closed Nextcloud and Firefox and reopened them, and no error occurred. But it can start randomly - I have also experienced opening a link from Discord while in a game, and it opened Firefox - completely freezing the system. Manjaro, KDE Plasma 5.23.3, Frameworks 5.88.0, Qt Version 5.15.2, Kernel 5.13.19-2-MANJARO, NVIDIA 3080 GPU. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 445804] kiconthemes 5.88.0 inconsistent icon changes
https://bugs.kde.org/show_bug.cgi?id=445804 William changed: What|Removed |Added Status|RESOLVED|REOPENED CC||wi11ia...@pm.me Resolution|FIXED |--- --- Comment #8 from William --- Can this be related to the fact that in plasma 5.23 my icons do not respect the themes "inherits=hicolor, breeze" path anymore? for example the icon for Steam used to come from the hicolor theme (where steam installed it) before as it is the first in the inherits chain, now it comes from the breeze theme... (it even comes from breeze theme if it is completly removed from the inherits) Idk if this belongs here but shouldnt that be considered undesired behaviour? i want my inherits chain to work as before and not use breeze icons when they are available in hicolor... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] New: wrong app icons
https://bugs.kde.org/show_bug.cgi?id=446477 Bug ID: 446477 Summary: wrong app icons Product: frameworks-kiconthemes Version: 5.88.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: wi11ia...@pm.me CC: kdelibs-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Use icon theme that inherits nothing but hicolor in index.theme 2. test an app that has an icon in hicolor and breeze themes but not in your theme OBSERVED RESULT the app uses the "wrong" icon from the breeze theme even though ur inherits chain should check first (and only) in hicolor EXPECTED RESULT the app icon that is present in hicolor theme is used SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.2-2-Manjaro (64bit) [manjaro stable] KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION might be related to https://bugs.kde.org/show_bug.cgi?id=445804 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 445804] kiconthemes 5.88.0 inconsistent icon changes
https://bugs.kde.org/show_bug.cgi?id=445804 --- Comment #10 from William --- sry didnt mean to cause confusion: i created a new ticket here: https://bugs.kde.org/show_bug.cgi?id=446477 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] wrong app icons
https://bugs.kde.org/show_bug.cgi?id=446477 --- Comment #1 from William --- obviously the icon theme from step 1 is not breeze itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] wrong app icons
https://bugs.kde.org/show_bug.cgi?id=446477 --- Comment #2 from William --- sry i meant it might be related to this commit: https://github.com/KDE/kiconthemes/commit/de3a1abb1839136322f32f2782f9592280b2bbd3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] wrong app icons
https://bugs.kde.org/show_bug.cgi?id=446477 William changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from William --- (In reply to Nate Graham from comment #3) > Can you test with Frameworks 5.89 once it's released in a week? If that > fixes it, then it's the same issue as Bug 445804. I can test it right now on KDE Neon Unstable Edition with frameworks 5.89.0 and the bahaviour is still exactly the same. breeze icons show up for apps even though the breeze icon theme is nowhere in the inherits chain and the icon exists in hicolor theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 William changed: What|Removed |Added CC||wi11ia...@pm.me --- Comment #199 from William --- Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.24.5 KDE-Frameworks-Version: 5.93.0 Qt-Version: 5.15.3 Kernel-Version: 5.17.6-1-MANJARO (64-bit) Grafik-Plattform: X11 just hit the update on manjaro stable, this bug still occuring , left/right row or column alignment items locked or unlocked, after every logout/login they are scrambled, although it doesnt seem random but rather in same way everytime (for example row alignment causes them to be in a sort of staircase pattern next login that is same everytime) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #200 from William --- what i just dont understand is why the "plasma-org.kde.plasma.desktop-appletsrc" file in the user home gets overwritten at all. if it already exists it shouldnt be changed by a login like ever.. i tried locking the file in readOnly mode it still gets touched and items are scrambled so only workaround is to autostart a script that changes that file agian... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #201 from William --- still also happens but not always on running "pkill plasmashell && kstart5 plasmashell" just tested this too, every 2nd or 3rd time that command changes deskto item positions aswell..- pls remove any codepath that touches that file during plasmashell start! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 William changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #202 from William --- Ok this might be a slitghtly different issue but the desktop icons still get scrambled and if i run the command cp -v ~/.config/plasma-org.kde.plasma.desktop-appletsrc.bak ~/.config/plasma-org.kde.plasma.desktop-appletsrc followed by the usual plamsashell restart: kquitapp5 plasmashell && kstart5 plasmashell the desktop ends up in a weird state where the icons show up where they belong as long as the focus is on the terminal, but when clicking anywhere on teh desktop the icons show up scrambled and on different positions. PLS PLS someone fix this issue for good, this is the nr1 reason i have to install xfce desktops on new linux user pcs because this happening every reboot/login would just drive em away from linux again at this point i am willing to pay for this to get fixed for real. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #204 from William --- (In reply to Nate Graham from comment #203) > Please file a new bug report as the original cause of this one has been > fixed. There might be new causes, but those need new bug reports. what policy is that? the bug description and everything in it fits the issue i have exactly, THIS bug is not fixed, creating a new one with exact same description will just lead to it not being found and not gaining any credibility, so it can be ignored for 6years again? There was a commit that claimed to fix this and it didnt: THIS BUG IS NUMBER 1 REASON u cannot install KDE to new users who dont want windows11.- and the action is to just ignore it and put it on "CLOSED FIXED" ? I am here telling you and whoever claimed to fix this, i can pay you if this gets finally fixed for real! And to anyone coming here from google, and co: THIS BUG IS NOT FIXED,.. it is very much still happening and 100% reproduceable every single logout/login, you are not the only one and your install is not at fault. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] New: Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 Bug ID: 454345 Summary: Desktop Icons get scrambled on plasmashell startup Product: plasmashell Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: wi11ia...@pm.me CC: h...@kde.org Target Milestone: 1.0 SUMMARY *** Everything is already explained here: https://bugs.kde.org/show_bug.cgi?id=354802 except that the this has nothing to do with resolution changes, so 5.24.5 did not fix it. *** STEPS TO REPRODUCE 1. put icons on desktop 2. kquitapp5 plasmashell && kstart5 plasmashell OBSERVED RESULT icons switch position, seemingly random with some sort of order to it so the same layout of icons mostly results in teh same scamble EXPECTED RESULT icons stay where they were SOFTWARE/OS VERSIONS Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.24.5 KDE-Frameworks-Version: 5.93.0 Qt-Version: 5.15.3 Kernel-Version: 5.17.6-1-MANJARO (64-bit) Grafik-Plattform: X11 ADDITIONAL INFORMATION This has nothing to do with resolutions, multimonitors or variable refresh rates or what not. Happens on logout/login or reboot aswell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #213 from William --- i created new bug for those still expirencing the issue here: https://bugs.kde.org/show_bug.cgi?id=454345 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #1 from William --- Additional Observarions on my part after the dissapointment that it was still not fixed with 5.24.5: 1: you can put the file where the desktop icon positions are stored: "~/.config/plasma-org.kde.plasma.desktop-appletsrc" in readonly mode and icons still get scrambled, even though the file does not seem to be changed. 2: when executing the restart commands the desktop icons can stay in a different state then currently shown when u have focus on a window, clicking on the desktop shows icons on different positions then when a window is in focus, this stopps after a while and the "desktop-state" when no window is in focus takes over for good 3: i have not completly figured out when this starts happening as you can create a fresh user and it doesnt happen for it until some point when it happens once, then it seems to happen everytime u just restart the shell or login. Deleting the ~/.config file does not have any effect on it either having to recreate ur desktop. 4: happens with no activitys and on single desktops, plasma uses systemd-startup. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 William changed: What|Removed |Added CC||wi11ia...@pm.me --- Comment #46 from William --- not an expert here just wondering about there just being an easy fix perhaps: Since blur is not part of the themes or window-decorations and if a user customizes his desktop with any combination of themes, to achive blur he will also have to go into the effects to activate it. Now here is my thaught: Why not just make the blur corner radius configurable in the blur effect settings. yes then it is just manual but users configure the blur str aso anyways when they customize their desktop. All this automatic detection stuff is maybe just unneccessary. Just a thaught from a different perspective after reading about this issue alot: take it as you wish, not an expert here on the technical side, just dont underestimate the KDE powerusers that are affected by this. they know how to configure themes and alot of stuff why not this too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440235] CSD windows have huge black outline when compositing is disabled
https://bugs.kde.org/show_bug.cgi?id=440235 William changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|1 |0 CC||wi11ia...@pm.me Status|RESOLVED|REPORTED --- Comment #5 from William --- on X11 it is already possible to circumvent this bug with some special settings: first one has to enforce the titlebar on firefox via a Kwin WindowRule (do not enable the standard titlebar in firefox settings) second u have to use breeze window-decoration style and make a custom rule to "unforce" border and titlebar again. this way the shadow is drawn by kwin and the window still looks just as before with proper gtk CSD! a proper solution to this would be to automatically load in a gtk-css style (similar to the window-decorations overwrite that already syncs min/max/close buttons) that just disables ALL CSD shadows and margins and then add something to kwin that enforces the draw of shadows. if the shadows come from kwin even on uncomposited desktop firefox and all other gtk CSD apps would look normal, without shadow. i dont know however how far this is possible (in kwin). on my end for firefox and the couple other gtk csd apps that i use i have the workaround in place and a custom gtk-css style that removes all shadows+markins in my ~/.config/gtk-3.0/gtk.css so that any gtk theme wont have these ugly client side shadows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440235] CSD windows have huge black outline when compositing is disabled
https://bugs.kde.org/show_bug.cgi?id=440235 --- Comment #6 from William --- another plus to my proposed solution (and the workaround) is that CSD apps would always (no matter the gtk-theme) have the correct shadow set by the window decoration theme, (that is if this is possible to implement for other windwo decos than breeze) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 425367] New: Setting the indentation to "Normal" through the menu Tools->Indentation never sticks
https://bugs.kde.org/show_bug.cgi?id=425367 Bug ID: 425367 Summary: Setting the indentation to "Normal" through the menu Tools->Indentation never sticks Product: kate Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: tambewill...@gmail.com Target Milestone: --- SUMMARY When opening a C files, the indentation is set to "C Style", which I am not comfortable with; so I tend to always set the indentation to "Normal" through the menu Tools->Indentation, but it never sticks. As soon as I switch to a different document in the "Document Tree View", and switch back to the C file, the indentation get reset back to "C Style". SOFTWARE/OS VERSIONS Kate Part Version 5.68.0 KDE Frameworks 5.68.0 Qt 5.12.8 (built against 5.12.8) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475429] New: Discover Crash
https://bugs.kde.org/show_bug.cgi?id=475429 Bug ID: 475429 Summary: Discover Crash Classification: Applications Product: Discover Version: 5.27.8 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: willsa...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.8) Qt Version: 5.15.3 Frameworks Version: 5.104.0 Operating System: Linux 5.15.0-86-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Crash when launching home tab while loading app icons The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7efcff3a7ba4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #5 0x7efcff3a7c10 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #6 0x7efcff3a89f7 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x7efcff3b4fd5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #8 0x7efd3fea141e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7efd41770713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7efd3fe73e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7efd3fe76f27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7efd3fecda67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7efd3e5a4d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7efd3e5fa258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7efd3e5a23e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7efd3fecd0b8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7efd3fe7275b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7efd3fe7acf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x55fa22df1c63 in ?? () #20 0x7efd3f78fd90 in __libc_start_call_main (main=main@entry=0x55fa22df1340, argc=argc@entry=1, argv=argv@entry=0x7ffdb6276768) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7efd3f78fe40 in __libc_start_main_impl (main=0x55fa22df1340, argc=1, argv=0x7ffdb6276768, init=, fini=, rtld_fini=, stack_end=0x7ffdb6276758) at ../csu/libc-start.c:392 #22 0x55fa22df26a5 in ?? () [Inferior 1 (process 3887) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 William changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #32 from William --- still happening on manjaro stable 5.26.2 changes did affect the behavoir instead of: AA B -> B C C it now scrambles the icons in a different way: AA B -> B CC sry but this is not fixed.- something still wrong here. why is it so hard to remove any logik that touches that desktop-appletrc file during plasmashell startup? you should only ever need to read from it till startup is completly done and in case of items or icons not found in it just dont display them till the user moves them to a new spot... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #34 from William --- ok still happens with the old style scramble when doing the command: kquitapp5 plasmashell && kstart5 plasmashell seeing this in the log output if it helps: file:///usr/lib/qt/qml/org/kde/plasma/private/containmentlayoutmanager/BasicAppletContainer.qml:144: TypeError: Cannot read property 'width' of null org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion wish someone wouldve actually worked with me or anyone who has this issue and can reproduce it effortlessly. i wouldve been happy to test out any new development version of plasmashell. plasma is by far the best DE there is but issues like this make it impossible to recommend. can we use this ticket or do i have to open it again with the exact same description? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #37 from William --- the point was that nothing should ever write to said file ever unless triggerd by a user-action (aka creating a new icon or moving one) parallel or not it doesnt matter. Also systemd cannot be blamed for this all the major distros use it and they all manage to not f*** with user settings during startup process. plasma is the only one where this happens. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448228] New: Gradients on Vector layer Issues (video included)
https://bugs.kde.org/show_bug.cgi?id=448228 Bug ID: 448228 Summary: Gradients on Vector layer Issues (video included) Product: krita Version: 5.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: williamrma...@gmail.com Target Milestone: --- SUMMARY https://youtu.be/v51IGnlRvZ4 Multi color Gradients not working as expected. The above video shows examples *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 10 Pro - OS Build - 19042.1415 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] Breeze icon being shown despite current icon theme not having Breeze in its fallback chain
https://bugs.kde.org/show_bug.cgi?id=446477 --- Comment #6 from William --- i dont wanna exagerate here but isnt this kinda a big issue? people who use different icon-themes to not want to have apps icons falling back to breeze, apps like Steam bring their own icon and with this bug alive those icons will never be used in any case, beacuse there exists a steam icon in the breeze-icon theme. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491242] New: Intermittent Plasma Crash with Multi-Monitor Setup, Custom Keyboard Layout, and Specific Window Focus Sequence
https://bugs.kde.org/show_bug.cgi?id=491242 Bug ID: 491242 Summary: Intermittent Plasma Crash with Multi-Monitor Setup, Custom Keyboard Layout, and Specific Window Focus Sequence Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: williamcand...@gmail.com Target Milestone: --- Hi. When i am using a multi-monitor setup with 3 monitors with a custom keyboard layout and a specific sequence of window focus events, the plasma crashes occasionally and that results in the entire desktop environment restarting. Reaching out looking for a work around for it. Your advice or assistance will extremely be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491242] Intermittent Plasma Crash with Multi-Monitor Setup, Custom Keyboard Layout, and Specific Window Focus Sequence
https://bugs.kde.org/show_bug.cgi?id=491242 William changed: What|Removed |Added URL||https://www.regfield.co.za -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #39 from William --- bump: plasma 5.26.4, 2 month after the latest claum it would be fixed this is still happening alot on fresh kde installs, how can i get the devs that worked on https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1150 and https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2240 to take a look at this issue again? it is rly rly annoying and an absolute no-go. As was pointed out it has nothing to do with systemd or anything happening before plasmashell startup. it happens even when plasmashell is started manually. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 414456] ktorrent crashes after at most 1 minute
https://bugs.kde.org/show_bug.cgi?id=414456 William changed: What|Removed |Added CC||williamdsm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 414727] New: Konversation crashes without any user input
https://bugs.kde.org/show_bug.cgi?id=414727 Bug ID: 414727 Summary: Konversation crashes without any user input Product: konversation Version: 1.7.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: gtr...@gmail.com Target Milestone: --- SUMMARY I started Konversation, connected to a server, joined a couple of channels and minimized the window. While I was using another app (firefox, the last time), Konversation crashed. This has happened both on Windows 10 (1909) and openSUSE Leap 15.1, both times running the 1.7.5 version. The Windows version was downloaded from https://binary-factory.kde.org/. STEPS TO REPRODUCE 1. Open Konversation; 2. Connect to a server and join a channel; 3. Minimize Konversation; 4. Wait a few minutes (about 20 to 40 minutes(?) - it's not constant) until it crashes. OBSERVED RESULT Konversation crashes silently. The last time (in openSUSE), I ran it from the console to check if I got an error to display there, and it actually brought up the KDE crash reporter; The generated report is pasted under "Additional Information". EXPECTED RESULT Keep Konversation running. SOFTWARE/OS VERSIONS Windows: Windows 10 (1909, 64-bit) Linux/KDE Plasma: openSUSE Leap 15.1, KDE Plasma 5.12.8 (openSUSE) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 (Windows 10 - information taken from "About Konversation") KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 (built against 5.13.2) ADDITIONAL INFORMATION KDE generated crash report: Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8164a58900 (LWP 2520))] Thread 6 (Thread 0x7f8131ce6700 (LWP 2525)): #0 0x7f815b0938ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f813739c83b in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7f813739c547 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0 #4 0x7f815d6099ef in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f8132628700 (LWP 2524)): #0 0x7f815b0938ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f813739c83b in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7f813739c547 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0 #4 0x7f815d6099ef in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f8146be7700 (LWP 2523)): #0 0x7f815d5ff19b in poll () from /lib64/libc.so.6 #1 0x7f81578551a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f81578552bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f815e27c96b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f815e22190a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f815e03fdaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f815d6099ef in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8147fff700 (LWP 2522)): #0 0x7f8157854640 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f81578550db in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f81578552bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f815e27c96b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f815e22190a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f815e03fdaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f815e6fc9e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f815d6099ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f814f56c700 (LWP 2521)): #0 0x7f815d5ff19b in poll () from /lib64/libc.so.6 #1 0x7f8159416307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f8159417f3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f8152324939 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f815d6099ef in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8164a58900 (LWP 2520)): [KCrash Handler] #6 0x7f815e0bf6e3 in operator==(QString const&, QString const&) () from /usr/lib64/libQt5Core.so.5 #7 0x562f782d32d9 in ?? () #8 0x562f782e035c in ?? () #9 0x562f782e96fd in ?? () #10 0x562f78297b9b in ?? ()
[plasmashell] [Bug 396384] New: Plasma desktop crash on startup
https://bugs.kde.org/show_bug.cgi?id=396384 Bug ID: 396384 Summary: Plasma desktop crash on startup Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rndm.ba...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.3) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.4-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I had rebooted after updating to the latest Plasma versions from Pacman, the crash appeared upon logging into the desktop. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f85f6a93cc0 (LWP 710))] Thread 11 (Thread 0x7f850f817700 (LWP 893)): #0 0x7f85efb9dea9 in poll () at /usr/lib/libc.so.6 #1 0x7f85d529e865 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f854b2ea144 in () at /usr/lib/libnvidia-glcore.so.396.24.02 #3 0x7f854b20aa8e in () at /usr/lib/libnvidia-glcore.so.396.24.02 #4 0x7f85d5294c1e in () at /usr/lib/libGLX_nvidia.so.0 #5 0x7f85df3e9569 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #6 0x7f85f0a48e10 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #7 0x7f85f42a18e8 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f85f42a5658 in () at /usr/lib/libQt5Quick.so.5 #9 0x7f85f02b8b45 in () at /usr/lib/libQt5Core.so.5 #10 0x7f85ef457075 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f85efba853f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f852affe700 (LWP 874)): #0 0x7f85efb9dea9 in poll () at /usr/lib/libc.so.6 #1 0x7f85e96ec523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f85e96ec63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f85f04ba054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f85f046594c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f85f02aea99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f85f422423b in () at /usr/lib/libQt5Quick.so.5 #7 0x7f85f02b8b45 in () at /usr/lib/libQt5Core.so.5 #8 0x7f85ef457075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f85efba853f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f85317fd700 (LWP 869)): [KCrash Handler] #6 0x7f85efb511e1 in __memmove_sse2_unaligned_erms () at /usr/lib/libc.so.6 #7 0x7f854af11286 in () at /usr/lib/libnvidia-glcore.so.396.24.02 #8 0x7f854affa00f in () at /usr/lib/libnvidia-glcore.so.396.24.02 #9 0x7f854affa3a5 in () at /usr/lib/libnvidia-glcore.so.396.24.02 #10 0x7f854b01c3c4 in () at /usr/lib/libnvidia-glcore.so.396.24.02 #11 0x7f854afdc3b4 in () at /usr/lib/libnvidia-glcore.so.396.24.02 #12 0x7f85f0d658c0 in () at /usr/lib/libQt5Gui.so.5 #13 0x7f85f0d66909 in () at /usr/lib/libQt5Gui.so.5 #14 0x7f85f0d379fb in () at /usr/lib/libQt5Gui.so.5 #15 0x7f85f0d3809e in QOpenGLShaderProgram::link() () at /usr/lib/libQt5Gui.so.5 #16 0x7f85f4299596 in QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char const*, char const*) () at /usr/lib/libQt5Quick.so.5 #17 0x7f85f4266c96 in () at /usr/lib/libQt5Quick.so.5 #18 0x7f85f42676b1 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #19 0x7f85f42688b6 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #20 0x7f85f426e103 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #21 0x7f85f425e4ee in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #22 0x7f85f425e9bc in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #23 0x7f85f4299030 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #24 0x7f85f42fcdb5 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #25 0x7f85f42a18a0 in () at /usr/lib/libQt5Quick.so.5 #26 0x7f85f42a5658 in () at /usr/lib/libQt5Quick.so.5 #27 0x7f85f02b8b45 in () at /usr/lib/libQt5Core.so.5 #28 0x7f85ef457075 in start_thread () at /usr/lib/libpthread.so.0 #29 0x7f85efba853f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f85337ff700 (LWP 868)): #0 0x7f85ef45cffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f85f02b92fc in QWaitCondition::wait(QMutex*, unsig
[dolphin] [Bug 352052] Dolphin startup fails when having hiragana (japanese) text in klipper history
https://bugs.kde.org/show_bug.cgi?id=352052 --- Comment #12 from William --- Problem seems to have gone away. Thanks -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369541] application couldt not download packages as update my system
https://bugs.kde.org/show_bug.cgi?id=369541 William changed: What|Removed |Added CC||wmore...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369541] application couldt not download packages as update my system
https://bugs.kde.org/show_bug.cgi?id=369541 --- Comment #2 from William --- Failed to apply changes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379970] New: When manually adding digital camera on Windows 10, camera is not detected and photos cannot be imported
https://bugs.kde.org/show_bug.cgi?id=379970 Bug ID: 379970 Summary: When manually adding digital camera on Windows 10, camera is not detected and photos cannot be imported Product: digikam Version: 5.5.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: wpvk...@gmail.com Target Milestone: --- I am trying to import photos from digital camera on Windows 10. The feature does not work due to the fact that the camera is not detected by digiKam. I see it works with gPhoto2, which is a Linux application. Will it be possible to do this in MS Windows? If not, it would be better to only have this feature available when the OS is Linux based. Rather hide it in MS Windows than "creating futile hope". -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 376514] New: Encrpyption option not available
https://bugs.kde.org/show_bug.cgi?id=376514 Bug ID: 376514 Summary: Encrpyption option not available Product: kmymoney4 Version: 4.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: file Assignee: kmymoney-de...@kde.org Reporter: william.cummi...@myself.com Target Milestone: --- Option to encrypt file grayed out, even though files can be encrypted with GPG in the command line and KGPG Varsion 4.8.0.1 Fedora 25 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 376514] Encrpyption option not available
https://bugs.kde.org/show_bug.cgi?id=376514 --- Comment #2 from William --- Hi Jack, I'm using Fedora 25,and KmyMoney was downloaded from the Fedora 25 repo. The website of course states "If possible, it is always preferred to use a package specifically prepared for your distribution", it doesn't add "unless you want to use file encryption, in which case you'll need to dowload the source files and compile it youself". As a file released to the official repo, I'd expect it to work 'as is'. and I do have Gpgme installed. Hope this helps, William *Sent:* Wednesday, February 15, 2017 at 4:18 PM *From:* Jack *To:* william.cummi...@myself.com *Subject:* [kmymoney4] [Bug 376514] Encrpyption option not availablehttps://bugs.kde.org/show_bug.cgi?id=376514 Jack changed: What |Removed |Added CC| |ostroffjh@users.sourceforge | |.net --- Comment #1 from Jack --- You don't say which distribution you use, or whether you compiled yourself. I believe there is a command line switch at compile (cmake) time for this feature, This requires gpgme, not just gpg, so you might also be missing the necessary library, although I suspect that would cause an error rather than just silently not offer encryption. You can try "lss `which kmymoney` | grep gpg" to see if that is an issue. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 376514] Encrpyption option not available
https://bugs.kde.org/show_bug.cgi?id=376514 --- Comment #4 from William --- Thanks I've raised a bug with Fedora, I'll keep you updated william *Sent:* Thursday, February 16, 2017 at 5:10 PM *From:* Jack *To:* william.cummi...@myself.com *Subject:* [kmymoney4] [Bug 376514] Encrpyption option not availablehttps://bugs.kde.org/show_bug.cgi?id=376514 Jack changed: What |Removed |Added CC|ostroffjh@users.sourceforge | |.net | --- Comment #3 from Jack --- I suggest you file a bug with Fedora. If they intentionally left out encryption, I'd love to know why, and if it was unintentional, they need to know. It certainly does not seem to be a bug in KmyMoney itself. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386141] New: Export to Google Photos not responding
https://bugs.kde.org/show_bug.cgi?id=386141 Bug ID: 386141 Summary: Export to Google Photos not responding Product: digikam Version: 5.7.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: wpvk...@gmail.com Target Milestone: --- Hi, I am running digiKam 5.7.0 on Windows 10 and trying to Export to Google Photos. I select my photos, Select the Export > Google Photos option, but nothing happens. No window appears, or error message is shown. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 386141] Export to Google Photos not responding
https://bugs.kde.org/show_bug.cgi?id=386141 --- Comment #2 from William --- After turning off all plugins except the Google Services plugin, it worked. I will have to try with 5.8.0, although I am bit scared that using a non-released version will have a bad effect on my digikam database. Should I be concerned? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384934] New: Install failed on Windows 10
https://bugs.kde.org/show_bug.cgi?id=384934 Bug ID: 384934 Summary: Install failed on Windows 10 Product: digikam Version: 5.7.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: wpvk...@gmail.com Target Milestone: --- Created attachment 107937 --> https://bugs.kde.org/attachment.cgi?id=107937&action=edit DigiKam 5.7.0 Install Error Hi, I am installing Digikam 5.7.0 on a Windows 10 system, but the error in the attached image is encountered. Any suggestions? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 384400] New: Segmentation Fault on Bug Report
https://bugs.kde.org/show_bug.cgi?id=384400 Bug ID: 384400 Summary: Segmentation Fault on Bug Report Product: drkonqi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: wibl...@gmail.com Target Milestone: --- Created attachment 107707 --> https://bugs.kde.org/attachment.cgi?id=107707&action=edit Call Stack On use of drkonqi the app crashes on receiving a Segmentation Fault (11) signal. Before that signal I was filling a report for a crash. Please find attached the call stack. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 384400] Segmentation Fault on Bug Report
https://bugs.kde.org/show_bug.cgi?id=384400 William changed: What|Removed |Added CC||wibl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374961] New: Clipboard "Edit Contents" shortcut never works
https://bugs.kde.org/show_bug.cgi?id=374961 Bug ID: 374961 Summary: Clipboard "Edit Contents" shortcut never works Product: plasmashell Version: 5.8.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: lee...@gmail.com Target Milestone: 1.0 Been using every release of KDE since 2.x. Since the new clipboard in the systray was introduced, assigning a shortcut to "Edit Contents.." and then trying to trigger it fails silently. OTOH, assigning a shortcut to 'Open Klipper at mouse position' and using it works fine (funny how 'Klipper' is still mentioned, despite klipper being a separate program as far as I'm aware). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374961] Clipboard "Edit Contents" shortcut never works
https://bugs.kde.org/show_bug.cgi?id=374961 --- Comment #2 from William --- Wow, I literally waited YEARS hoping that every release would bring a fix, even removing the plasmoid en starting klipper.. then removing the plasmoid again with each apt-get upgrade. Many, many thanks. If I can drop a donation anywhere, let me know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493569] loss of icon position on the desktop
https://bugs.kde.org/show_bug.cgi?id=493569 William changed: What|Removed |Added CC||wi11ia...@pm.me --- Comment #5 from William --- this does not seem to be resolved - it is happening on single monitor, single dedicated amd-gpu fresh install of tumbleweed with plasma 6.2.0.- I suspect its still an issue where positions are read and saved at the same time as you can sometimes end up with "zombie" icons after a monitor power off/on that just show but are not clickable and follow other icons around if you drag them... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494353] New: Black Scren upon lock, monitor off/on with desktop icons scrambled
https://bugs.kde.org/show_bug.cgi?id=494353 Bug ID: 494353 Summary: Black Scren upon lock, monitor off/on with desktop icons scrambled Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wi11ia...@pm.me CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Fresh install OpenSuse Tumbleweed. Plasma 6.2 - X11 Session: When locking the session (Meta+L) the screen goes completly black with only a cursor. Upon turning monitor off and back on again the lock screen appears, when logging in icons on desktop are scrambled. Turning monitor off without locking and turning it back on results in same blackscreen. Plasmashell can be restarted then with opening a Konsole window via shortcut and running "killall plasmashell && kstart plasmashell" and desktop is back but icons are scrambled. STEPS TO REPRODUCE 1. login x11 session 2. lock session 3. turn monitor off - and back on again 4. log back in OBSERVED RESULT after lock session the screen is black, it comes back when monitor is restarted but after login the desktop icons are scrambled EXPECTED RESULT the lockscreen shows and remains after monitor off/on + the desktop icons remain in position. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.2 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #8 from William --- plasma 6.2: discover settings still not readable for any dark color-scheme -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494353] Black Scren upon lock, monitor off/on with desktop icons scrambled
https://bugs.kde.org/show_bug.cgi?id=494353 --- Comment #2 from William --- Created attachment 174579 --> https://bugs.kde.org/attachment.cgi?id=174579&action=edit kwin_x11 crash - added kwin crash dump: maybe related, maybe not but kwin_x11 crashes when monitor is turned off while no app is running. when at least one window is open the crash dialog does not come up when plasmashell shows up again display is connected via displayport to dedicated amd gpu, there is no second monitor shenanigans or any weird monitor setup, simple FHD (1920*1080) resolution and no other connection is used. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494353] Black Scren upon lock, monitor off/on with desktop icons scrambled
https://bugs.kde.org/show_bug.cgi?id=494353 --- Comment #1 from William --- Ok issue seems not not happen everytime. sometimes the lockscreen actually appears, when the blackscreen appears waiting does not resolve it though even after 10min the lockscreen wont appear. Same for the monitor off/on cycles - sometimes the desktop comes right back. sometimes plasmashell seems to be frozen entirely (nothing in panel or desktop can be clicked but window shortcuts still work) either way turing monitor off/on again couple of times seems to cause plasmashell to come back and work normaly again. Anyway lockscreen (and desktop icons) unusable in X11 session with auto monitor sleep -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494353] Monitor off/on scrambles desktop icons
https://bugs.kde.org/show_bug.cgi?id=494353 William changed: What|Removed |Added Summary|Black Scren upon lock, |Monitor off/on scrambles |monitor off/on with desktop |desktop icons |icons scrambled | --- Comment #4 from William --- I swear i try to search for existing bugs before i create new ones but i somehow missed this, probably cuz it was under theme component and didnt have "black" screen in it but its exactly what is happening on a fresh tumbleweed install when u change the theme to Breeze, wich is the only thing i did (always do this, to avoid distro themeing and rather use the KDE defaults) buit when changing back to the distro theme the blank/black screen does not appear. only with breeze theme: so that part is duplicate of this unresolved bug: https://bugs.kde.org/show_bug.cgi?id=483163 the desktop icon scramble sounds very much like this resolved bug: https://bugs.kde.org/show_bug.cgi?id=493569 which either is not resolved or triggered by a different issue, it happens everytime u cycle monitor power though just like described in that bug. Let me know if i should close this one as duplicate and reopen that one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494353] Monitor off/on scrambles desktop icons
https://bugs.kde.org/show_bug.cgi?id=494353 William changed: What|Removed |Added Component|general |Folder CC||h...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493569] loss of icon position on the desktop
https://bugs.kde.org/show_bug.cgi?id=493569 --- Comment #8 from William --- this happens 100% reliably every single time turing monitor off and back on. not with games or lockscreen though only monitor power cycles. doesnt matter if i select desktop or any icons on it - still they get scrambled. happens of fresh install (tumbleweed) when u just put a single icon onto the desktop. Also if u power cycle monitor enough u can create "zombie" icons that cant be clicked. things were not as bad before 6.2 - pls ensure desktop positions are not updated while previous state is "stored". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493569] loss of icon position on the desktop
https://bugs.kde.org/show_bug.cgi?id=493569 --- Comment #9 from William --- by playing around with the desktop folderview settings i made following revelation: the bug happens only when sort mode "left to right" is active (which is the default) and not when "top to bottom" is selected. This sounds weird but settings are confusing and icons are not sorted after anything (set to "manual") so why does a sort order have any impact when it should never apply.. "locking" the icons has also no effect other than that you cant fix them manually after they get scrambled all the other possible settings also dont affect it. tested on fresh install - simply switching the sort order fixes it - then you can sort your items manually once and they actually stay. Why not simply remove all the auto sorting stuff that noone uses anyway when it seems to mess with user preffered positions this much... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494353] Monitor off/on scrambles desktop icons
https://bugs.kde.org/show_bug.cgi?id=494353 --- Comment #7 from William --- Both bugs still happen on 6.2.1, but this can be closed as duplicate as its exactly the 2 bugs i linked and those include more info. 1st bug (missing lockscreen) is only happening on X11 and with compositor turned on and is fixed with choosing different theme (note opensuse theme seems to be 1:1 breeze with just a different default desktop wallpaper) 2nd bug (scrambled icons) is happening on both wayland and x11 - but not after chaning default sort order to "top to bottom" its a single monitor connected via displayPort directly to dedicated amd gpu in a desktop-pc (no other gpu). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494353] Monitor off/on scrambles desktop icons
https://bugs.kde.org/show_bug.cgi?id=494353 --- Comment #8 from William --- the kwin_x11 crash issue i thaught connected to bug 1 is fixed in 6.2.1 though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 498223] X11 session mouse curosor extremly laggy and delayed
https://bugs.kde.org/show_bug.cgi?id=498223 William changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- Ever confirmed|0 |1 --- Comment #2 from William --- then why does it only happen in plasma and stops as soon as kwin_x11 renders some other stuff? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 498223] New: X11 session mouse curosor extremly laggy and delayed
https://bugs.kde.org/show_bug.cgi?id=498223 Bug ID: 498223 Summary: X11 session mouse curosor extremly laggy and delayed Classification: Plasma Product: kwin Version: 6.2.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: wi11ia...@pm.me Target Milestone: --- Only in the X11 session the mouse cursor is extremely laggy and delayed (like dragging it on a rope). This however stops as soon as some effect is running that updates the forces the screen to be updated. e.g. when running glxgears at monitor refresh rate in background the cursor is normal. as soon as glx gear is stopped and only some static apps are running that do not update the screen every vblank the cursor becomes very slow. using the showFPS effect also forces the screen update and therefor fixes the cursor but as soon as its deactivated the cursor is slow again. Note: cursor is also slow when compositing is disabled (kwin_x11 suspend). only X11 is affected, in wayland the cursor behaves normaly. SOFTWARE/OS VERSIONS Linux Kernel: 6.12.6 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION single dedicated AMD gpu, displayport connection to single monitor that does not support "freesync" or other VRR. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #9 from William --- plasma 6.2.4 the issue is resolved and background color in settings is as expected -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 William changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 --- Comment #41 from William --- as i said happens on wayland and x11 both. scrambling is not alphabetical anymore and icons even end up outside the screen area (so you have to scroll to find them) happens 100% consistently on every monitor off/on cycle. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 William changed: What|Removed |Added Version|6.1.3 |6.3.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 William changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 --- Comment #37 from William --- This bug is not fixed in plasma 6.3.0 - still happens on single display - no scaling - wayland and x11 both - single dedicated amd gpu setup when montitor turns off u can hear unplug sound and when turned on again icons are scrambled again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500270] New: Desktop click and drag icon multi-select window does not select the right files
https://bugs.kde.org/show_bug.cgi?id=500270 Bug ID: 500270 Summary: Desktop click and drag icon multi-select window does not select the right files Classification: Plasma Product: plasmashell Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop icons & Folder View widget Assignee: plasma-b...@kde.org Reporter: wi11ia...@pm.me CC: h...@kde.org Target Milestone: 1.0 SUMMARY When clicki + dragging to select files on Desktop and only half selecting an icon the window does not include it in the end or only includes it and not the rest. STEPS TO REPRODUCE 1. place multiple icons on desktop folderview 2. click drag in a straight line up wards 2 ore more icons but only slightly select the last one (so it shows up as slected while still holding but isnt fully engulfed in the selection) 3. let go of click OBSERVED RESULT Nothing is selected - you cannot move the icons. EXPECTED RESULT All icons that are shown as highlighted during the selection process are part of the select afterwards. Note: when fully engulfing the icons it works as expected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse tumbleweed KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION worked in 6.2.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 William changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 --- Comment #39 from William --- Its def not fixewd on my end - dont make me create a new bug ticket for a 5th time with the exact same description as this. fresh install opensuse tumbleweed with plasma 6.3.0 - comepletly new user new desktop icons - still happens -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482875] When encountering a "zero screens connected" condition, desktop icons get re-arranged (first time in alphabetical order, then after that randomly)
https://bugs.kde.org/show_bug.cgi?id=482875 --- Comment #42 from William --- OK here is some further test results on plasma 6.3. The issue is definitly not as bad as it was in 6.2 and icons surive a reboot all the time. The issue seems to happen for me 100% when you touches the setting to change icon order (left-to-right | top-bottom) within the current session (just via right click on desktop -> symbols -> order) and then power cycle the monitor. The icons seem to survive some power cycles and expecially on a fresh plasma bootup where this setting was never changed. So can one of you that could reproduce this issue in 6.2 check if it is happening for you when you change that setting and after that toggle the monitor off/on a couple times? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504736] New: Clipboard setting to not include non-text in history does not work
https://bugs.kde.org/show_bug.cgi?id=504736 Bug ID: 504736 Summary: Clipboard setting to not include non-text in history does not work Classification: Plasma Product: plasmashell Version First master Reported In: Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard widget & pop-up Assignee: plasma-b...@kde.org Reporter: wi11ia...@pm.me CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY The plasma clipboard settings do not what they say they do. STEPS TO REPRODUCE 1. Adjust clipboard settings to not sync with select and not store non-text in history. 2. Explizitly copy file or folder. 3. Check clipboard history OBSERVED RESULT the file shows up in the clipboard history EXPECTED RESULT the file does not show up in the history SOFTWARE/OS VERSIONS Linux Kernel: openSUSE tumbleweed stable (Kernel 6.14) KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 ADDITIONAL INFORMATION both wayland and x11 seem to be affected by this -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504736] Clipboard setting to reject non-text from history unintuitively still includes files
https://bugs.kde.org/show_bug.cgi?id=504736 --- Comment #2 from William --- mmh seems like it. i just testen this on a fresh kubuntu stable that is sitll running plasma 5 and the behaviour is the same. At the very least the setting should be renamed to better describe what "non-text" and "text" selections include. ' And i guess the wanted behaviour of no files at all showing up in the history is a feature request then -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 507505] New: Download folder is not resolved correctly by default on Windows platform leading to receiving files not working OOB
https://bugs.kde.org/show_bug.cgi?id=507505
Bug ID: 507505
Summary: Download folder is not resolved correctly by default
on Windows platform leading to receiving files not
working OOB
Classification: Applications
Product: kdeconnect
Version First unspecified
Reported In:
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: windows-application
Assignee: piyushaggarwal...@gmail.com
Reporter: wmcdann...@gmail.com
Target Milestone: ---
What I was attempting to do when I noticed the problem:
Sending file(s) from an Android device (using KDE connect app) to a Windows
laptop.
What happened:
The Android phone claims the file was sent, but I have no idea where to find
the file on the Windows laptop. There's no notification or indication on the
Windows laptop that a file was received. I checked the settings for the "share
and receive" plugin on the windows machine and the "save files in:" path is set
to "/C:/Users/wmcdannell/Desktop" (notice the leading forward slash).
I then headed over to
https://invent.kde.org/network/kdeconnect-kde/-/blob/master/plugins/share/shareplugin.cpp?ref_type=heads
to check the code for anything obvious.
The following code might be where the leading forward slash comes from (works
great on Android and linux of course) but I'm not familiar with cpp or the
project so it could be coming from elsewhere.
plugins/share/shareplugin.cpp
Lines 57-63
~
QUrl SharePlugin::getFileDestination(const QString filename) const
{
const QUrl dir = destinationDir().adjusted(QUrl::StripTrailingSlash);
QUrl destination(dir);
destination.setPath(dir.path() + QStringLiteral("/") + filename,
QUrl::DecodedMode);
return destination;
}
~
Moreover, in the plugin settings for "share and receive", I can put anything I
want in the "save files in" path. Even if it is not a valid path, when I click
"apply" it gets saved 😲. When apply is clicked, a little input validation and
checking that the chosen folder is writable by the app would probably be a good
idea.
Additionally concerning, on the windows platform in particular, is the lack of
information given to the user when a file is received. Even after updating the
path to be a valid path, when I send a file from the Android device there is no
notification of any kind to let me know that a file was sent to the laptop. The
file just shows up in the destination folder. I'm perfectly ok with that being
a more technically inclined user but a regular user of windows might be
wondering: did it work? where did it go? how do i get there? The fact that the
desktop folder is the default destination is good but I think a system
notification or a notification from the app would be more user friendly.
Version of KDE connect installed:
kdeconnect-kde-release_25.04-4975-windows-cl-msvc2022-x86_64.exe (latest
download as of 2025-07-24).
Platform details:
Edition Windows 11 Home
Version 24H2
Installed on‎7/‎4/‎2025
OS build26100.4770
Experience Windows Feature Experience Pack 1000.26100.197.0
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 362881] Crash when applying transform
https://bugs.kde.org/show_bug.cgi?id=362881 William Kensinger changed: What|Removed |Added CC||will89...@gmail.com --- Comment #14 from William Kensinger --- I'm also experiencing this bug. Running Krita 3.0.94 directly from the appimage. Looking over synaptic, currently installed version of QT is QT4 "4:4.8.7+dfsg-5ubuntu2", which tells me that it's probably 4.8? Running Linux Mint's Cinnamon interface over an existing Ubuntu 16.04 LTS intallation. I hope this information is useful in fixing this bug, and let me know if there's anything else I can do to help! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450201] New: Desktop Application Launcher opens desktop file in text editor.
https://bugs.kde.org/show_bug.cgi?id=450201 Bug ID: 450201 Summary: Desktop Application Launcher opens desktop file in text editor. Product: plasmashell Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: haiwilli...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 146702 --> https://bugs.kde.org/attachment.cgi?id=146702&action=edit bug depiction SUMMARY Not sure If I'm reporting this in the correct place, but when using the application launcher that opens by clicking on the desktop opens the desktop file in the default text editor instead of opening the desired application. STEPS TO REPRODUCE 1. Enable application menu on desktop 2. Open any application OBSERVED RESULT Desktop file opens in default text editor. EXPECTED RESULT Application opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Have not tested on x11, bug experienced under wayland. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446497] Breeze GTK theme CSD (window decorations) incorrect under Wayland
https://bugs.kde.org/show_bug.cgi?id=446497 William F. changed: What|Removed |Added CC||haiwilli...@gmail.com --- Comment #5 from William F. --- I can reproduce this on 5.24 Tumbleweed under Wayland with both natively installed apps and flatpaks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450201] Desktop Application Launcher opens desktop file in text editor.
https://bugs.kde.org/show_bug.cgi?id=450201 --- Comment #1 from William F. --- Just tested on x11, same behaviour as wayland. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470195] New: Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything
https://bugs.kde.org/show_bug.cgi?id=470195 Bug ID: 470195 Summary: Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: wcool...@gmail.com Target Milestone: --- Created attachment 159219 --> https://bugs.kde.org/attachment.cgi?id=159219&action=edit Can't open anything through main K menu, Task Manager, or Desktop Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 5650U with Radeon Graphics Memory: 14.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20XF004SUS System Version: ThinkPad T14s Gen 2 ADDITIONAL INFORMATION I can't open *anything* in the K menu or from the task manager. I'm getting a "Resource error (fork failure): Cannot allocate memory" error for everything, see attachment. Also, none of my desktop icons are viewable. I have 16 gigs of memory total, and have been running Kubuntu for a year without any real problems. I don't know what update brought on this behavior? Running free -h shows I have 9.1Gi left, so I don't know what is going on. The only way I was able to even open Firefox to file this bug report was krunner. So far, I've been able to open most things through it, or typing into konsole once I opened that through krunner, but this is a huge inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468899] [Spectacle 23.04] Video Recording - Add configuration options and shortcuts to Spectacle settings page.
https://bugs.kde.org/show_bug.cgi?id=468899 William Herron changed: What|Removed |Added CC||wherro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #5 from William Coolman --- I don't think this is the same bug. My memory usage looks normal. On Wed, May 24, 2023 at 9:35 AM Paul Worrall wrote: > https://bugs.kde.org/show_bug.cgi?id=469445 > > Paul Worrall changed: > >What|Removed |Added > > > CC||wcool...@gmail.com > > --- Comment #4 from Paul Worrall --- > *** Bug 470195 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470195] Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything
https://bugs.kde.org/show_bug.cgi?id=470195 William Coolman changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #2 from William Coolman --- I don't appear to have a memory leak, so I don't think the suggested bug that this was listed as a clone is accurate. I'm reopening this ticket. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #6 from William Coolman --- (In reply to William Coolman from comment #5) > Created attachment 159362 [details] > attachment-3610397-0.html > > I don't think this is the same bug. My memory usage looks normal. > > On Wed, May 24, 2023 at 9:35 AM Paul Worrall > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=469445 > > > > Paul Worrall changed: > > > >What|Removed |Added > > > > > > CC||wcool...@gmail.com > > > > --- Comment #4 from Paul Worrall --- > > *** Bug 470195 has been marked as a duplicate of this bug. *** > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. Ok, removing the ScreenMapping entry made things work again. I'll close this ticket. Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 William Coolman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #7 from William Coolman --- Removing [ScreenMapping] entry from /home/[user]/.config/plasma-org.kde.plasma.desktop-appletsrc fixed the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #10 from William Coolman --- My mistake. I'll correct that. On Wed, May 31, 2023, 7:32 AM Federico Dossena wrote: > https://bugs.kde.org/show_bug.cgi?id=469445 > > --- Comment #9 from Federico Dossena --- > Why did you mark this as fixed? That's a workaround, not a solution. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shade/shutter feature
https://bugs.kde.org/show_bug.cgi?id=450582 William Kendrick changed: What|Removed |Added CC||n...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
