On Mon, 4 Jun 2012 16:01:24 Roger Oberholtzer wrote:
On Mon, 2012-06-04 at 11:36 +0800, George Olson wrote:
Another test you might do is create a completely new user, and see if the desktop crashes when that one logs in.
I mentioned in the original question that a newly created user worked fine. As that is the case, I guess they could delete the current .kde4 directory and the various caches in the current user and let them be recreated. That would be pretty much what they would get with a new user anyway. But that is a last ditch effort.
Roger, It sounds to me like a corruption or incompatibility in one of the desktop configuration files under .kde4/share/config. When I have had issues like this in the past, I have usually ended up backing up and deleting all the plasma- related config files. Unfortunately, this then requires recreating all of the user settings (which I know you're trying to avoid). These are only text files, so it may be possible (if you had access to the desktop) to narrow it down to a specific file or even section of a file but that is not likely to be something solved quickly.
I think they are trying to preserve their KDE config. The problem has occurred in a measurement vehicle out on some highway system. The measurement crew are not trained in user recovery. Explaining how to configure KDE over the mobile is possible, but not something they want to do if it can be avoided.
I feel your pain. What KDE needs is a default user template that can be customised and saved and used as the basis for new users (I think 'doze can do this to a certain extent).
We have on our to-do list making a script that configures a user's KDE setup. This seems to be a rather poorly documented part of KDE, and so we still must do this by hand on every install. Generally we can live with that. But here is an example of when such customization would best be scripted. The types of things we change are those that effect our use of the system. Like disabling screen savers, power saving features, system update nagging.
None of this should be too difficult to do - it just takes time (which in this case you may not have). If you do come up with a suitable framework I'm sure there would be others interested in it. Regards, Rodney. -- ========================================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ========================================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org