Re: Akonadi won't start

2022-04-19 Thread Paul Brown
On Tuesday, 19 April 2022 18:25:58 CEST Mike Diehl wrote:
> Hi all,
> 
> I've been using kde on this machine for several months, now.  But suddenly,
> akonadi won't start:
> 
> 
> =
> mdiehl@mikeworkstation:~$ akonadictl start
> 
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> mdiehl@mikeworkstation:~$ org.kde.pim.akonadiserver: Starting up the
> Akonadi Server... org.kde.pim.akonadiserver: database server stopped
> unexpectedly
> org.kde.pim.akonadiserver: Database process exited unexpectedly during
> initial connection! org.kde.pim.akonadiserver: executable:
> "/usr/sbin/mysqld-akonadi"
> org.kde.pim.akonadiserver: arguments:
> ("--defaults-file=/home/mdiehl/.local/share/akonadi/mysql.conf",
> "--datadir=/home/mdiehl/.local/share/akonadi/db_data/",
> "--socket=/run/user/1000/akonadi/mysql.socket",
> "--pid-file=/run/user/1000/akonadi/mysql.pid") org.kde.pim.akonadiserver:
> stdout: ""
> org.kde.pim.akonadiserver: stderr: "mysqld-akonadi: [ERROR] Failed to open
> required defaults file:
> /home/mdiehl/.local/share/akonadi/mysql.conf\nmysqld-akonadi: [ERROR] Fatal
> error in defaults handling. Program aborted!\n" org.kde.pim.akonadiserver:
> exit code: 1
> org.kde.pim.akonadiserver: process error: "Unknown error"
> mysqladmin: connect to server at 'localhost' failed
> error: 'Can't connect to local MySQL server through socket
> '/run/user/1000/akonadi/mysql.socket' (2)' Check that mysqld is running and
> that the socket: '/run/user/1000/akonadi/mysql.socket' exists!
> org.kde.pim.akonadiserver: Failed to remove runtime connection config file
> org.kde.pim.akonadiserver: Shutting down AkonadiServer...
> org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
> normally...
> =
> 
> Any ideas would be most appreciated.
> 
> Mike.

Hey Mike,

Try moving your akonadi directory out of the way: 

mv .local/share/akonadi/ .local/share/akonadi_old

And then try starting akonadi again.

Akonadi will rebuild the databases and you won't loose any emails or 
calendars, although you may have to tweak stuff in you email profiles and  
folders, as, when rebuilding, you may discover that Kmail is now saving sent 
message in... oh... the drafts folder or the trashbin... it can be anywhere.

Another thing that may be affected are your local email filters, and, if you 
have more than one identity, the identity associated with each folder.

... Yeah, my setup is a bit clunky.

Cheers

Paul
-- 
Promotion & Communication

www: http://kde.org
Mastodon: https://mastodon.technology/@kde
Facebook: https://www.facebook.com/kde/
Twitter: https://twitter.com/kdecommunity
LinkedIn: https://www.linkedin.com/company/kde




Re: Akonadi won't start

2022-04-19 Thread Paul Brown
On Tuesday, 19 April 2022 20:50:28 CEST Mike Diehl wrote:
> On Tuesday, April 19, 2022 2:37:43 PM EDT Paul Brown wrote:
> > On Tuesday, 19 April 2022 18:25:58 CEST Mike Diehl wrote:
> > > Hi all,
> > > 
> > > I've been using kde on this machine for several months, now.  But
> > > suddenly,
> > > akonadi won't start:
> > > 
> > > 
> > > =
> > > mdiehl@mikeworkstation:~$ akonadictl start
> > > 
> > > Connecting to deprecated signal
> > > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> > > mdiehl@mikeworkstation:~$ org.kde.pim.akonadiserver: Starting up the
> > > Akonadi Server... org.kde.pim.akonadiserver: database server stopped
> > > unexpectedly
> > > org.kde.pim.akonadiserver: Database process exited unexpectedly during
> > > initial connection! org.kde.pim.akonadiserver: executable:
> > > "/usr/sbin/mysqld-akonadi"
> > > org.kde.pim.akonadiserver: arguments:
> > > ("--defaults-file=/home/mdiehl/.local/share/akonadi/mysql.conf",
> > > "--datadir=/home/mdiehl/.local/share/akonadi/db_data/",
> > > "--socket=/run/user/1000/akonadi/mysql.socket",
> > > "--pid-file=/run/user/1000/akonadi/mysql.pid")
> > > org.kde.pim.akonadiserver:
> > > stdout: ""
> > > org.kde.pim.akonadiserver: stderr: "mysqld-akonadi: [ERROR] Failed to
> > > open
> > > required defaults file:
> > > /home/mdiehl/.local/share/akonadi/mysql.conf\nmysqld-akonadi: [ERROR]
> > > Fatal
> > > error in defaults handling. Program aborted!\n"
> > > org.kde.pim.akonadiserver:
> > > exit code: 1
> > > org.kde.pim.akonadiserver: process error: "Unknown error"
> > > mysqladmin: connect to server at 'localhost' failed
> > > error: 'Can't connect to local MySQL server through socket
> > > '/run/user/1000/akonadi/mysql.socket' (2)' Check that mysqld is running
> > > and
> > > that the socket: '/run/user/1000/akonadi/mysql.socket' exists!
> > > org.kde.pim.akonadiserver: Failed to remove runtime connection config
> > > file
> > > org.kde.pim.akonadiserver: Shutting down AkonadiServer...
> > > org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
> > > normally...
> > > =
> > > 
> > > Any ideas would be most appreciated.
> > > 
> > > Mike.
> > 
> > Hey Mike,
> > 
> > Try moving your akonadi directory out of the way:
> > 
> > mv .local/share/akonadi/ .local/share/akonadi_old
> > 
> > And then try starting akonadi again.
> > 
> > Akonadi will rebuild the databases and you won't loose any emails or
> > calendars, although you may have to tweak stuff in you email profiles and
> > folders, as, when rebuilding, you may discover that Kmail is now saving
> > sent message in... oh... the drafts folder or the trashbin... it can be
> > anywhere.
> > 
> > Another thing that may be affected are your local email filters, and, if
> > you have more than one identity, the identity associated with each
> > folder.
> > 
> > ... Yeah, my setup is a bit clunky.
> > 
> > Cheers
> > 
> > Paul
> 
> Hi Paul,
> 
> Thanks for getting back to me so quickly.
> 
> Well, I tried what you suggested:
> 
> 
> mdiehl@mikeworkstation:~/.local/share$ mv akonadi akonadi.orig
> 
> mdiehl@mikeworkstation:~/.local/share$ akonadictl start
> 
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> mdiehl@mikeworkstation:~/.local/share$ org.kde.pim.akonadiserver: Starting
> up the Akonadi Server... mysqld-akonadi: [ERROR] Failed to open required
> defaults file: /home/mdiehl/.local/share/ mysqld-akonadi: [ERROR] Fatal
> error in defaults handling. Program aborted! org.kde.pim.akonadiserver:
> database server stopped unexpectedly
> org.kde.pim.akonadiserver: Database process exited unexpectedly during
> initial connection! org.kde.pim.akonadiserver: executable:
> "/usr/sbin/mysqld-akonadi"
> org.kde.pim.akonadiserver: arguments:
> ("--defaults-file=/home/mdiehl/.local/share/akonadi/mysql.conf",
> "--datadir=/home/mdiehl/.local/share/akonadi/db_data/",
> "--socket=/run/user/1000/akonadi/mysql.socket",
> "--pid-file=/run/user/1000/akonadi/mysql.pid") org.kde.pim.akonadiserver:
> stdout: ""
> org.kde.pim.akonadiserver: stderr: "mysqld-akonadi: [ERROR] Failed to open
> required defaults file:
> /home/mdiehl/.local/share/akonadi/mysql.conf\nmysqld-akonadi: [ERROR] Fatal
> error in defaults handling. Program aborted!\n" org.kde.pim.akonadiserver:
> exit code: 1
> org.kde.pim.akonadiserver: process error: "Unknown error"
> mysqladmin: connect to server at 'localhost' failed
> error: 'Can't connect to local MySQL server through socket
> '/run/user/1000/akonadi/mysql.socket' (2)' Check that mysqld is running and
> that the socket: '/run/user/1000/akonadi/mysql.socket' exists!
> org.kde.pim.akonadiserver: Failed to remove runtime connection config file
> org.kde.pim.akonadiserver: Shutting down AkonadiServer...
> org.kde.pim.akonadic

Re: Akonadi won't start

2022-04-19 Thread René J . V . Bertin
On Tuesday April 19 2022 14:50:28 Mike Diehl wrote:
>On Tuesday, April 19, 2022 2:37:43 PM EDT Paul Brown wrote:
>> On Tuesday, 19 April 2022 18:25:58 CEST Mike Diehl wrote:
>> > Hi all,
>> > 
>> > I've been using kde on this machine for several months, now.  But
>> > suddenly,
>> > akonadi won't start:


Hi,

You may get more insider information if you ask on ; the 
KDE PIM devs are there too.

R.


Re: Resized kontact/calendar pane. Now can't get it back

2022-04-19 Thread Duncan
Mike Diehl posted on Fri, 01 Apr 2022 10:43:02 -0400 as excerpted:

> On Thursday, March 10, 2022 5:30:58 PM EDT Frank Steinmetzger wrote:
>> Am Mon, Feb 28, 2022 at 05:11:03PM -0500 schrieb Mike Diehl:
>> > Hi all,
>> > 
>> > I was using kontact's calendar module and managed to make the date
>> > navigator and calendar manager disappear by resizing the panel.  How
>> > can I reset the screen layout?
>> 
>> There should be a vertical grip handle right next to the Kontact icon
>> sidebar. Actually, there are two on my machine. One for the iconbar
>> itself and one for those panels.
> 
> I was able to get back on my wife's machine and confirm that there are
> no handles to grab.  I can find the resizing area, but when I drag it
> out in either direction, nothing happens.
> 
> So, I need to find where the layout is stored and "reset" it.  Any
> ideas?

[Manually reset to standard nested quote/reply order.]

With the caveat below forcing a general answer which I never-the-less hope 
you find useful, kde configuration files are normally reasonably named and 
found in $XDG_CONFIG_HOME (~/.config/ by default if that var isn't set).  
Look for a kontact subdir if it exists, and if you don't find it there, 
kontactrc or other kontact* or possibly kalendar* or similar.

With fresh backups just in case, these should be text-editable.

The files should be normal *.ini format files for the most part, plain 
text with [] enclosed section titles and setting=value lines.

(Unfortunately, a few "state=" values are apparently base64-encoded binary 
or some such -- toolbar state being the thing I remember finding stored 
this way. But that's reasonably easy to reconfigure if deleting the rather 
opaque line whole is required, certainly easier than having to redo an 
entire heavily customized configuration from scratch.)

Caveat: I've never needed the full kontact suite and have never run it.  
After a decade on kmail without a lost mail that I recall, I started 
losing emails when they jumped the akonadi shark, and migrated away when I 
realized they were needlessly complexifying simple text-based email into 
easily corrupted binary database crap.  Since then, having broken my 
trust, anything kdepim or akonadi related is not allowed anywhere even 
close to my systems.  Of course YMMV and you may have never had such 
problems and with luck never will, but that's why, not seeing anything 
more specific posted yet, I'm posting the rather general answer based on 
kde norms, hoping it's still helpful.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman