From kde-pim  Mon Jan 04 10:41:57 2010
From: Anne Wilson <annew () kde ! org>
Date: Mon, 04 Jan 2010 10:41:57 +0000
To: kde-pim
Subject: Re: [Kde-pim] unwanted akonadi startup - how to kill it?
Message-Id: <201001041042.05144.annew () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-pim&m=126260176820734
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1981362615=="

--===============1981362615==
Content-Type: multipart/signed;
  boundary="nextPart1821473.8b8JtLFpxr";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1821473.8b8JtLFpxr
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Sunday 03 January 2010 21:08:33 ComputerDruid wrote:
> On Sunday 03 January 2010 15:52:44 Anne Wilson wrote:
> > On Sunday 03 January 2010 19:09:44 Anne Wilson wrote:
> > > I have some old root mail in /var/spool/mail/root.  My intention was =
to
> > >
> > >  check in kwrite that there was only old messages, then delete it.
> > >  However, as soon as I clicked on it (in root dolphin) it attempted to
> > >  start up akonadi.  It's still whizzing back and forth, and I can't
> > > find a way to stop it.
> >
> > It was in fact trying to start a new KMail, and I did eventually manage
> > to kill it.
>=20
> Let me just mention that root dolphin probably isn't the greatest idea.
>=20
I know - and I have put my own warning signs in place so that I stay there =
for=20
the shortest time needed to do a specific job.

> That said, maybe the akonadi server startup should be cancelable? (With a
> warning that this might cripple some pim applications)
>=20
I'm confused about what is actually happening here.  Certainly this was an=
=20
additional akonadi server startup that was being attempted - stopping and r=
e-
starting the local one didn't affect it.  Sooner or later, though, someone =
is=20
going to accidentally start one as I did, so a way of cancelling it would b=
e a=20
benefit.

> Dolphin probably should have warning when being run as root also.
>=20
I use a different schema that is unmistakeable - with bright blue text for=
=20
everything.  It works perfectly for me, prompting me to close dolphin as so=
on=20
as I have found and done whatever I was searching for.  With failing memory=
 as=20
you get older, visual searching in a file manager is much easier than CLI=20
searching, particularly if I want to check whether a number of files are=20
applicable to the problem of the moment, rather than a single one.  Yes, I=
=20
know it's all possible on the CLI, but my solution is practicable for me.

Anne
=2D-=20
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org

--nextPart1821473.8b8JtLFpxr
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)

iEYEABECAAYFAktBxfwACgkQbMErw/n0TZr6TwCcDIChHQKe/lBPxJSS8akBmZwu
uM4An38vJdSMFF/qjZloRAp3NpaDUSOS
=PtRY
-----END PGP SIGNATURE-----

--nextPart1821473.8b8JtLFpxr--

--===============1981362615==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============1981362615==--