![]() I didn't test your patch and not sure if it'd actually work, but it looks like it might work.Īs for issue with changing directory, does folder view store positions configuration for different directory somewhere? It doesn't look that way to me. I think in my patch it's a bit more obvious where data is buffered. > It still needs a fixup as it still has that same issue with handling a > as a buffer before we we set as folder model's proxy. > - same principle but uses the source model > Also I think we can do everything inside plasma-desktop, which skips the > If you change dir (such as from configure) we'll get a new completed event. > There's a potential issue with that patch. (In reply to David Edmundson from comment #25) Hope we can find the real cause of the problem. # To alleviate 'messed-up desktop icons' bug (KDE Bugtracking System – Bug 354802)Ĭp -appletsrc.saved -appletsrcĪ very ugly temporary fix - but it works for me. I use this small script to make the restoration and restart: What I have done to alleviate my situation is to make a copy of the afore-mentioned file prior to switching off my computer, and then use it to restore the file, and restart the plasma shell when I notice that the desktop is messed up after login. I presume that some kde program wants to check this file for plausibility or correctness, and then messes it up. The apparent reason for the mixed-up desktop is that the file ~/.config/-appletsrc is modified directly after I log into my computer. I suspect many kde devs never switch-off their machines, hence they would never see the bug. The bug is especially annoying if you switch-off your computer on a nightly basis (like I do). I have just migrated to 18.04 from 14.04. Only that it then appeared every month or so, but now, with kubuntu 18.04, practically every day. It's also not limited to reboots, though reboots trigger this more frequently - it can also happen on a normal logout (not followed by a reboot). The graphics card driver / manufacturer does not make a difference - it's hitting systems with Intel, Nvidia and AMD graphics equally. Interestingly, I have not seen this happening in VirtualBox VMs - just in case someone is trying it in there. I have yet to migrate most machines to openSUSE Leap 15.0, so I do not have any data on it (yet). Upgrading from openSUSE Leap 42.2 (Plasma Framework 5.27.0, Plasma Desktop/Workspace 5.8.3) to openSUSE Leap 42.3 (Plasma Framework 5.32.0, Plasma Desktop/Workspace 5.8.7) reduced the likelihood of triggering this bug by at least 50%, but it's still there. Machines with spinning drives are affected much more frequently. However, what I have learned so far: A lot less likely to happen if the Desktop configuration data (i.e. I have not found a reliable way to reproduce it. xsession-errors from 2 sessions without bug and 1 with bugĪ have been observing this bug on multiple machines for a few years now. config/-appletsrc after reboot with icons rearrangedįiles and screenshot before and after bug Original placement with corruption fixed manually Misplaced bottom panel and usage monitors ISO.ĭuring install to hard disk it asks at the end to the install Grub Boot Loader, if installed correctly it will boot up Debian after 30 seconds automatically.unless a key is pressed to bypass.ĭebian have extensive guides on their website.Before: 4 clean rows of icons. ISO you can burn to DVD Media, even Windows 10 can burn an. It is recommended to use Etcher to write the x86 Debian with RPD. Would somebody please detail what I need to do so upon reboot, I boot into Desktop and avoid visiting GRUB again? Perhaps Mikerr? The GRUB config criteria from the previous session was not retained and of course how to do so was a fondly-held well-kept secret! I Googled to see how to save the GRUB parameters but was unsuccessful at obtaining an understandable solution. I was again thrown into bloody GRUB prompt mode, and all previous commands had to be repeated. Later I booted up again, but not into RPI Desktop. At a Desktop session's end, I logged out and shut down. Miraculously, I finally managed to discover how to identify and enter the needed GRUB parameters (root, vmlinuz, etc.) then upon GRUB's boot command, RPi Desktop actually started up! Halleluja! I noticed PiServer was on the desktop menu so I would FINALLY be able to do ethernet boots on my Pi 3s, the true goal of this protracted endeavor. However when I booted up, I was not in Desktop but was thrown into a GRUB prompt without a clue what to do next. ![]() In a previous thread I was advised to install Rpi Desktop on my x86 pc, which I (after much travail) I finally succeeded doing, thanks to UNetbootin. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |