return kde desktop to default.

jo...@wexfordpress.com

unread,

Mar 15, 2013, 12:35:16 PM3/15/13

to

I managed to mess up my KDE desktop on my home file so that I want to
start
over with the original configuration. Deleteing the ~.kde file didn't
do it. Any suggestions? Slackware 14

John Culleton

Aragorn

unread,

Mar 15, 2013, 2:11:44 PM3/15/13

to

On Friday 15 March 2013 17:35, jo...@wexfordpress.com conveyed the
following to comp.windows.x.kde...

> I managed to mess up my KDE desktop on my home file so that I want to
> start over with the original configuration. Deleteing the ~.kde file
> didn't do it. Any suggestions? Slackware 14

Try renaming the ~/.kde or ~/.kde4 _directory_ to something like
~/.kde.old and do the same for the _file_ ~/.kderc.

Do this while not logged into KDE. Then try logging in again. That
should reset the configuration to the defaults.

--
= Aragorn =

http://www.linuxcounter.net - registrant #223157

jo...@wexfordpress.com

unread,

Mar 15, 2013, 2:54:03 PM3/15/13

to

On Mar 15, 2:11 pm, Aragorn <stry...@telenet.be.invalid> wrote:
> On Friday 15 March 2013 17:35, j...@wexfordpress.com conveyed the

That should work but doesn't
I'll try wiping out everytning in th .config file. Stay tuned!

John C.

jo...@wexfordpress.com

unread,

Mar 15, 2013, 3:08:31 PM3/15/13

to

On Mar 15, 2:54 pm, "j...@wexfordpress.com" <j...@wexfordpress.com>
wrote:

> On Mar 15, 2:11 pm, Aragorn <stry...@telenet.be.invalid> wrote:
>
>
>
> > On Friday 15 March 2013 17:35, j...@wexfordpress.com conveyed the
> > following to comp.windows.x.kde...
>
> > > I managed to mess up my KDE desktop on my home file so that I want to
> > > start over with the original configuration. Deleteing the ~.kde file
> > > didn't do it. Any suggestions? Slackware 14
>
> > Try renaming the ~/.kde or ~/.kde4 _directory_ to something like
> > ~/.kde.old and do the same for the _file_ ~/.kderc.
>
> > Do this while not logged into KDE. Then try logging in again. That
> > should reset the configuration to the defaults.
>
> > --
> > = Aragorn =
>

> > http://www.linuxcounter.net-registrant #223157

>
> That should work but doesn't
> I'll try wiping out everytning in th .config file. Stay tuned!
>
> John C.

That didn't help eiither.

John C.

alexd

unread,

Mar 15, 2013, 3:50:48 PM3/15/13

to

jo...@wexfordpress.com (for it is he) wrote:

> I'll try wiping out everytning in th .config file. Stay tuned!

strace -eopen <kdeapp> will list every file that <kdeapp> tries to open when
it loads [not just limited to KDE programs here, of course]. With any luck,
it will include the configs it's trying to read. Example:

strace -eopen kate

lists, amongst many other lines,

open("/home/alex/.kde/share/config/katerc.lock", O_WRONLY|O_CREAT|O_EXCL,
0644) = 11
open("/home/alex/.kde/share/config/katerc", O_RDONLY|O_CLOEXEC) = 12
open("/home/alex/.kde/share/config/katercE19485.new", O_RDWR|O_CREAT|O_EXCL|
O_CLOEXEC, 0600) = 12
open("/home/alex/.kde/share/config/katercE19485.new", O_RDWR|O_CREAT|
O_CLOEXEC, 0666) = 13
open("/home/alex/.kde/share/config/katerc.lock", O_WRONLY|O_CREAT|O_EXCL,
0644) = 11
open("/home/alex/.kde/share/config/katerc", O_RDONLY|O_CLOEXEC) = 12
open("/home/alex/.kde/share/config/katercV19485.new", O_RDWR|O_CREAT|O_EXCL|
O_CLOEXEC, 0600) = 12
open("/home/alex/.kde/share/config/katercV19485.new", O_RDWR|O_CREAT|
O_CLOEXEC, 0666) = 13

so I can be pretty sure that ~/.kde is where it's getting its config from.

--
<http://ale.cx/> (AIM:troffasky) (UnSoEs...@ale.cx)
19:48:08 up 11:44, 2 users, load average: 0.74, 0.80, 0.72
Qua illic est reprehendit, illic est a vindicatum

Aragorn

unread,

Mar 15, 2013, 5:22:55 PM3/15/13

to

On Friday 15 March 2013 19:54, jo...@wexfordpress.com conveyed the

following to comp.windows.x.kde...

> On Mar 15, 2:11 pm, Aragorn <stry...@telenet.be.invalid> wrote:
>
>> On Friday 15 March 2013 17:35, j...@wexfordpress.com conveyed the
>> following to comp.windows.x.kde...
>>
>> > I managed to mess up my KDE desktop on my home file so that I want
>> > to start over with the original configuration. Deleteing the ~.kde
>> > file didn't do it. Any suggestions? Slackware 14
>>
>> Try renaming the ~/.kde or ~/.kde4 _directory_ to something like
>> ~/.kde.old and do the same for the _file_ ~/.kderc.
>>
>> Do this while not logged into KDE. Then try logging in again. That
>> should reset the configuration to the defaults.
>

> That should work but doesn't
> I'll try wiping out everytning in th .config file. Stay tuned!

You may also want to check /tmp, /var/tmp and ~/tmp for any directories
containing both the name of your user account and the word "cache" in
their name, and delete those.

Best is to do this while KDE has not been started yet.

jo...@wexfordpress.com

unread,

Mar 16, 2013, 10:00:42 AM3/16/13

to

On Mar 15, 5:22 pm, Aragorn <stry...@telenet.be.invalid> wrote:
> On Friday 15 March 2013 19:54, j...@wexfordpress.com conveyed the

> following to comp.windows.x.kde...
>
>
>
>
>
>
>
>
>
> > On Mar 15, 2:11 pm, Aragorn <stry...@telenet.be.invalid> wrote:
>
> >> On Friday 15 March 2013 17:35, j...@wexfordpress.com conveyed the
> >> following to comp.windows.x.kde...
>
> >> > I managed to mess up my KDE desktop on my home file so that I want
> >> > to start over with the original configuration. Deleteing the ~.kde
> >> > file didn't do it. Any suggestions? Slackware 14
>
> >> Try renaming the ~/.kde or ~/.kde4 _directory_ to something like
> >> ~/.kde.old and do the same for the _file_ ~/.kderc.
>
> >> Do this while not logged into KDE. Then try logging in again. That
> >> should reset the configuration to the defaults.
>
> > That should work but doesn't
> > I'll try wiping out everytning in th .config file. Stay tuned!
>
> You may also want to check /tmp, /var/tmp and ~/tmp for any directories
> containing both the name of your user account and the word "cache" in
> their name, and delete those.
>
> Best is to do this while KDE has not been started yet.
>
> --
> = Aragorn =
>
> http://www.linuxcounter.net- registrant #223157

Rebooted cleared out all three and it still found the old setup.

I'll fiddle some more.

John C.

J.O. Aho

unread,

Mar 16, 2013, 10:38:38 AM3/16/13

to

On 15/03/13 20:50, alexd wrote:
> jo...@wexfordpress.com (for it is he) wrote:
>
>
>> I'll try wiping out everytning in th .config file. Stay tuned!
>
> strace -eopen <kdeapp> will list every file that <kdeapp> tries to open when
> it loads [not just limited to KDE programs here, of course]. With any luck,
> it will include the configs it's trying to read. Example:
>
> strace -eopen kate
>
> lists, amongst many other lines,
>
> open("/home/alex/.kde/share/config/katerc.lock", O_WRONLY|O_CREAT|O_EXCL,
> 0644) = 11
>

> so I can be pretty sure that ~/.kde is where it's getting its config from.

If you do "mv ~alex/.kde ~alex/.kde_bup" as root while alex ain't logged
into a KDE desktop, the next time you start KDE, a new ~alex/.kde will
be created and next time you run kate new config files for it will be
created in ~alex/.kde/share/config/

There can of course be that you have default settings for applications
and removing the config for those applications will not make a
difference how they look or behave and of course this will not affect
gtk or qt only applications as those will not save their configs in
~alex/.kde.

--

//Aho

Yo$$1960

unread,

Mar 17, 2013, 7:40:40 AM3/17/13

to

On Sat, 16 Mar 2013 07:00:42 -0700, jo...@wexfordpress.com wrote:

> Rebooted cleared out all three and it still found the old setup.

At the risk of stating the obvious, and repeating stuff that's gone
before, you need to do all the moving/deleting of directories and files
whilst the user is *not* logged in. If that user account is active, the
config files simply get rewritten.

It's not clear that you've been doing it that way, so thought it worth
mentioning.

--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
Stained glass windows keep the cold outside
Religion - Public Image Ltd

jo...@wexfordpress.com

unread,

Mar 18, 2013, 9:28:15 AM3/18/13

to

On Mar 17, 7:40 am, Yo$$1960 <yoss1...@yahoo.co.uk> wrote:

Thanks. To be certain I have rebooted and with no kdm active deleted
the files required. It still doesn't work. For my next trick I will
copy my important files to another user directory, change ownership
and work from that one.

John C.

Bit Twister

unread,

Mar 18, 2013, 11:46:12 AM3/18/13

to

On Mon, 18 Mar 2013 06:28:15 -0700 (PDT), jo...@wexfordpress.com wrote:
>
> Thanks. To be certain I have rebooted and with no kdm active deleted
> the files required. It still doesn't work. For my next trick I will
> copy my important files to another user directory, change ownership

do grep those files for the old user's login.

Anytime my desktop became hosed, a rename of the .kde? to .kde?_bkup
and log out/in resolved that problem.

I do not have to worry about /var/tmp because I made kde use my
directory for everything by setting the following variables:
KDEHOME=/home/bittwister/.kde4
KDEVARTMP=/home/bittwister/tmp
KDETMP=/home/bittwister/tmp

I have that setup for system wide users via /etc/profile.d/xx_local.sh
which has the following snippet of commands:

export TMP=$HOME/tmp
export TMPDIR=$TMP

if [ -e $HOME/.kde4 ] ; then
export KDEHOME=$HOME/.kde4
fi

export KDETMP=$TMP
export KDEVARTMP=$TMPDIR
export KDE_NO_IPV6=true