[Mageia-dev] Fwd: Re: M3 won't complete boot after update

Anne Wilson annew at kde.org
Thu Sep 27 12:05:29 CEST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 27/09/12 09:59, Anne Wilson wrote:
> On 26/09/12 23:20, AL13N wrote:
> 
>> this is normal behavior for gmail, it's why i stopped using it:
> 
>> it works like this, if you are on a mailing list, and it ends up
>>  at google, and you're using the gmail imap gateway, you will not
>>  be getting your own message, thus not knowing if it was there or
>>  not, and your threading will break. same thing with aliasses.
> 
>> i filed a bug but it is a "feature"
> 
> Agreed.  Sadly, I don't have much choice right now.
> 
> Borg2 is/was my IMAP server, and GMail was my emergency backup. 
> Since I can't access Borg2 from my laptop, that's no longer a 
> possibility. I can't even read the mail on Borg2 itself, as I can't
> get akonadi to start - manually starting it says that akonadiserver
> returned with exit code 255 (Unknown error) and "akonadiserver"
> crashed too often and will not be restarted.
> 
Ignore that - I realise now that I was in a root console when I tested
it.  In a user console it tells me that akonadi server is running.

> The result is that Borg2 is reported as being offline.
> 
So whatever it is, it appears it's not akonadi as such.

Anne
- -- 
Need KDE help? Try
http://userbase.kde.org or
http://forum.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBkJOcACgkQj93fyh4cnBdZnQCffqy22iQMiU9XVpIjCvM9eJdu
BPIAn3gMiWHQ+c4bVgl11nguTuSb4lWN
=yHiU
-----END PGP SIGNATURE-----


More information about the Mageia-dev mailing list