SUMMARY *** 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. idk 2. idk 3. idk OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: coffee linux (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Idk how this happen. i tried to figured it out how to fix it. even selecting lock in place doesnt fix it. it happens both on laptop and legion go. im using coffee linux and it is arch based. i dont remember if i had this issue on debian kde. but, i need help figuring it out on how to solve this issue. happens everytime on reboot. maybe another bug. can you help?
This happens to me too on Debian 12 + testing repository, so Plasma 5.27.9 and Frameworks 5.107 It's very annoying! Especially when you have many shortcuts, like I have, to folders (Home, Trash) tools, programs, games, etc.
(In reply to John from comment #1) > This happens to me too on Debian 12 + testing repository, so Plasma 5.27.9 > and Frameworks 5.107 > It's very annoying! > Especially when you have many shortcuts, like I have, to folders (Home, > Trash) tools, programs, games, etc. oh wow, so im not the only one then. must be a huge issue on kde then.
(In reply to John from comment #1) > This happens to me too on Debian 12 + testing repository, so Plasma 5.27.9 > and Frameworks 5.107 > It's very annoying! > Especially when you have many shortcuts, like I have, to folders (Home, > Trash) tools, programs, games, etc. any idea how to fix it?
Could any of the reporters check if this issue still exists on plasma 6? Thanks!
now i cant use desktop icons at all, lol.
hopefulyl someone has a fixed:)
(In reply to fanzhuyifan from comment #4) > Could any of the reporters check if this issue still exists on plasma 6? > Thanks! I don't think the requested information has been provided :(
(In reply to fanzhuyifan from comment #7) > (In reply to fanzhuyifan from comment #4) > > Could any of the reporters check if this issue still exists on plasma 6? > > Thanks! > > I don't think the requested information has been provided :( whats information is need?
If possible, could you check if this issue still exists on plasma 6? The least disruptive way to try that would be using a neon unstable live boot ISO, so that you don't need to modify the existing system. On arch it is also offered in the kde-unstable repo https://wiki.archlinux.org/title/Official_repositories#kde-unstable
(In reply to fanzhuyifan from comment #9) > If possible, could you check if this issue still exists on plasma 6? The > least disruptive way to try that would be using a neon unstable live boot > ISO, so that you don't need to modify the existing system. On arch it is > also offered in the kde-unstable repo > https://wiki.archlinux.org/title/Official_repositories#kde-unstable i see, coffee linux is using 5.27.10 so kde plasma 6 is now out?
(In reply to cggoody5 from comment #10) > (In reply to fanzhuyifan from comment #9) > > If possible, could you check if this issue still exists on plasma 6? The > > least disruptive way to try that would be using a neon unstable live boot > > ISO, so that you don't need to modify the existing system. On arch it is > > also offered in the kde-unstable repo > > https://wiki.archlinux.org/title/Official_repositories#kde-unstable > > i see, coffee linux is using 5.27.10 so kde plasma 6 is now out? Currently plasma 6 is in RC2, and the actual release will be sometime in February (https://community.kde.org/Schedules/Plasma_6) Since plasma 5 will no longer receive updates, and since plasma 6 had received many updates and fixes, it would really appreciated if you could check if this bug still exists in plasma 6 -- I personally did not reproduce this on my plasma 6 setup.
(In reply to fanzhuyifan from comment #11) > (In reply to cggoody5 from comment #10) > > (In reply to fanzhuyifan from comment #9) > > > If possible, could you check if this issue still exists on plasma 6? The > > > least disruptive way to try that would be using a neon unstable live boot > > > ISO, so that you don't need to modify the existing system. On arch it is > > > also offered in the kde-unstable repo > > > https://wiki.archlinux.org/title/Official_repositories#kde-unstable > > > > i see, coffee linux is using 5.27.10 so kde plasma 6 is now out? > > Currently plasma 6 is in RC2, and the actual release will be sometime in > February (https://community.kde.org/Schedules/Plasma_6) > Since plasma 5 will no longer receive updates, and since plasma 6 had > received many updates and fixes, it would really appreciated if you could > check if this bug still exists in plasma 6 -- I personally did not reproduce > this on my plasma 6 setup. ok cool. how would i install this plasma 6?
ok im trying to add the kde unstable line to pacman.conf line. how should it look? there has to be a spac e between the include line before general options right? i just rejoined arch of this yr. so im a bit rusty from debian, lol.
i got it figured it out.
got i got it installed. it seems to work if you lock in place.
where do you find the icon lock in place besides right clicking on the desktop>icons then lock in place. where do i find that in system settings? it changed the locations of where they at and such.
seems to be fixed now. so i think whatever happened is now fixed.
ok, also, many icons are missing in nemo file manager folder. is that part of kde as well? or no?
(In reply to cggoody5 from comment #18) > ok, also, many icons are missing in nemo file manager folder. > > is that part of kde as well? or no? Hi, nemo is not a KDE project.
(In reply to fanzhuyifan from comment #19) > (In reply to cggoody5 from comment #18) > > ok, also, many icons are missing in nemo file manager folder. > > > > is that part of kde as well? or no? > > Hi, nemo is not a KDE project. ok, thanks.