Version: (using KDE 4.2.0) Compiler: gcc (Debian 4.3.3-4) 4.3.3 OS: Linux Installed from: Debian testing/unstable Packages Tested on Kile SVN, Kate, and any application that requires lock files and editing contexts. .kde4/share/apps/RecentDocuments gets populated with .lock files resulting in plasma shutting down, the entire dock being useless and kded4 being locked up. This becomes a recursive state which never resolves itself. If one minimizes their konsole [terminal] instance(s) they become useless. Killing X and restarting it via the KDM login is useless as there now are zombie processes that don't get killed and restarted, leaving one to a broken login desktop environment. Ultimate workaround [not really a workaround as it is forces one to move to gtk+ editors and more while in KDE4.2] is to sudo reboot. There is something fundamentally wrong in the FileDialog class that is not allowing for these locks to clean up and release objects.
Since you don't have a Debian Experimental, you might want to add this into your Platform options. This has been an issue since Debian Experimental has built KDE4 packages. Each revision has become more and more stable, but this is a show stopper.
What is the status of this bug in recent KDE versions (4.6.5 or 4.7)? Please add a comment. I have never heard of this issue before. Does Kate still create those .lock files?
Let me read up on the bug and verify if it still displays itself against Debian 4.6.5. Sincerely, Marc J. Driftmeyer On 07/28/2011 09:55 AM, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=185869 > > > Christoph Feck<christoph@maxiom.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |christoph@maxiom.de > > > > > --- Comment #2 from Christoph Feck<christoph maxiom de> 2011-07-28 16:55:11 --- > What is the status of this bug in recent KDE versions (4.6.5 or 4.7)? Please > add a comment. > > I have never heard of this issue before. Does Kate still create those .lock > files? >
Does this still happen?
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!