| 1 |
On 29 July 2017 at 12:19, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> |
| 5 |
> On 29 July 2017 at 12:03, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 6 |
> |
| 7 |
>> |
| 8 |
>> Don't use kmail |
| 9 |
>> |
| 10 |
>> Seriously, why are putting up with the pain that POS is causing you? |
| 11 |
>> You've been posting about serious kmail and akonadi issues for about 4 |
| 12 |
>> years now if memory serves, and it has never gotten better. It probably |
| 13 |
>> never will :-) |
| 14 |
>> |
| 15 |
>> It must be well more than 4 years. What can I say, you are right, I must |
| 16 |
> be glutton for punishment. LOL! |
| 17 |
> |
| 18 |
> TBH, it has been serving me fine for quite a few years now, although the |
| 19 |
> migration to akonadi was a painful affair by all accounts. This was |
| 20 |
> originally caused by me using POP3 and a tonne of filters. I moved to |
| 21 |
> IMAP4 and few filters and it all worked relatively painlessly since. |
| 22 |
> |
| 23 |
> This however must be a postgresql related error, as it worked fine before |
| 24 |
> I removed version 9.5. Any idea what this "Invalid database object during |
| 25 |
> initial database connection" might be and how to recover from it? |
| 26 |
> |
| 27 |
|
| 28 |
Hmm, even more symlinks have been broken, This time I spotted |
| 29 |
/usr/bin/psql pointing to a non-existent ../lib64/postgresql-9.5/bin/psql. |
| 30 |
I came across it when I tried to connect to the database manually and |
| 31 |
couldn't run psql, but could run psql96. I'm still not sure if I did |
| 32 |
something wrong this time during the upgrade and migration and what it |
| 33 |
might have been, of if something else is amiss and merits a bug report. |
| 34 |
|
| 35 |
akonadi is still uncooperative. :-( |
| 36 |
|
| 37 |
It must be related to whatever it runs to start postgres. |
| 38 |
-- |
| 39 |
Regards, |
| 40 |
Mick |
Archives