Mailinglist Archive: opensuse (1018 mails)
| < Previous | Next > |
Re: [opensuse] plasma desktop crashes
- From: Roger Oberholtzer <roger@xxxxxx>
- Date: Mon, 04 Jun 2012 08:31:24 +0200
- Message-id: <1338791484.28675.17.camel@acme.pacific>
On Mon, 2012-06-04 at 11:36 +0800, George Olson wrote:
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.
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.
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.
Yours sincerely,
Roger Oberholtzer
OPQ Systems / Ramböll RST
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
roger.oberholtzer@xxxxxxxxxx
________________________________________
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
www.rambollrst.se
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
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.
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.
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.
Yours sincerely,
Roger Oberholtzer
OPQ Systems / Ramböll RST
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
roger.oberholtzer@xxxxxxxxxx
________________________________________
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
www.rambollrst.se
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
| < Previous | Next > |