LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-06-2011, 05:30 PM   #1
alexcg
LQ Newbie
 
Registered: Mar 2010
Location: St. Petersburg, Russia
Distribution: Slackware, Debian
Posts: 13

Rep: Reputation: 2
Question Akonadi server won't start...


Basically, the problem is that the Akonadi server won't start correctly on KDE startup.

I know this question has been asked million times, but I've not found the 100%-working solution for this problem yet. It seems like many Slackware users just remove the akonadi package, but it doesn't look like a good solution for me.

Unfortunately, I don't have the access to my Slackware box right now, so I'm writing this by memory.

Here is what I've tried to do so far:

1) Make the mysql daemon executable:
Code:
# chmod +x /etc/rc.d/rc.mysqld
2) Edit the /usr/bin/startkde file and add the /usr/share/akonadi directory to the XDG_DATA_DIRS environment variable.
3) Add the line "user=alexander" to the file /home/alexander/.local/share/akonadi/mysql.conf.
4) Reboot the computer.

After doing those steps the Akonadi server still shows a window with errors on startup.

As far as I remember the ~/.xsession-errors file contains an error like "Can't connect to local MySQL server through socket /home/alexander/<some path that I forget, sorry>/mysql.socket. I've tried searching this error as well, but again, no luck.

What am I doing wrong?

P.S. I'm running Slackware64 13.1 and KDE 4.4.5 from the Alien BOB's ktown repository.
 
Old 03-06-2011, 08:46 PM   #2
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 15,877
Blog Entries: 27

Rep: Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668
My guess is that your socket for mysql is not in the place that akonadi is looking. I think the standard location is /var/mysql/mysql.sock.

I think because I don't have a standard mysql installation to search. In a XAMPP installation, which is self-contained, the socket file is

/opt/lampp/var/mysql/mysql.sock.

I have no idea where the relevant akonadi config file would be.

[EDITORIAL MODE ON]

I loathe akonadi. Don't get me started.

[EDITORIAL MODE OFF]
 
1 members found this post helpful.
Old 03-06-2011, 11:29 PM   #3
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: LinuxMint 17.3 Rosa 64 bit
Posts: 589

Rep: Reputation: 49
Hello:

For what it is worth, that annoying Akonadi situation only happens when I login in as 'root'. It does not happen when I login as 'rob'.

Also, when I login as 'root' the Akonadi error msg happens twice!

The errors are about the 'Akonadi server' & the 'Akonadi control' and both refer to 'D-Bus'.

Last edited by Robert.Thompson; 03-06-2011 at 11:30 PM. Reason: typo's
 
Old 03-06-2011, 11:41 PM   #4
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 15,877
Blog Entries: 27

Rep: Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668Reputation: 4668
Maybe this thread will help:

http://www.linuxquestions.org/questi...konadi-795342/

It seems that akonadi is not allowed functionality for root as a security measure.
 
1 members found this post helpful.
Old 03-07-2011, 12:11 AM   #5
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: LinuxMint 17.3 Rosa 64 bit
Posts: 589

Rep: Reputation: 49
Quote:
Originally Posted by frankbell View Post
Maybe this thread will help:

http://www.linuxquestions.org/questi...konadi-795342/

It seems that akonadi is not allowed functionality for root as a security measure.
Does this mean that, if you log in as 'root', you should not use any windows manager and just use the command line?

If not, which windows manager is safe to use?

Thanks,
 
Old 03-07-2011, 12:37 AM   #6
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,589

Rep: Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959Reputation: 1959
Well, the general idea is that you shouldn't be logged in as root very often, if at all. Some distributions do not give root a login shell, so that you cannot log in as root. In those distributions, you have to use sudo to perform any superuser actions.

I'll login as my normal non-root self and "su -" in a window if I need to do something as root. Some people make the extra effort to use a visibly different terminal window to remind them that they are logged in as root and thus can do really bad things to their system. YMMV.
 
1 members found this post helpful.
Old 03-07-2011, 11:23 AM   #7
alexcg
LQ Newbie
 
Registered: Mar 2010
Location: St. Petersburg, Russia
Distribution: Slackware, Debian
Posts: 13

Original Poster
Rep: Reputation: 2
First of all, thank you all for your replies.

Quote:
Originally Posted by Robert.Thompson
For what it is worth, that annoying Akonadi situation only happens when I login in as 'root'. It does not happen when I login as 'rob'.
What have you done to get rid of that annoying Akonadi situation when you login as 'rob'?
By the way, which version of KDE are you running?

Quote:
Originally Posted by frankbell
My guess is that your socket for mysql is not in the place that akonadi is looking. I think the standard location is /var/mysql/mysql.sock.
Well, after reading this, I've solved the problem concerned with MySQL.

It looks like the Akonadi server starts without any problem on startup, but after KDE shutdown I get the following errors:
1) The /home/alexander/.local/share/akonadi/akonadiserver.error file contains a line
Code:
D-Bus session bus went down - quitting
2) The /home/alexander/.local/share/akonadi/akonadi_control.error file contains the same error.

My guess is that the D-Bus shutdown occurs earlier than the Akonadi shutdown does. It obviously generates an error, because Akonadi depends on D-Bus.

Is there any way to fix this (i.e. change the order of "shutdowning")?

By the way, is there any problem with Akonadi on slackware-current/slackware64-current?

Last edited by alexcg; 03-07-2011 at 11:34 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Akonadi GlennsPref Mandriva 7 03-04-2011 05:56 AM
i need to start akonadi as soon as i startx. basheer Slackware 3 08-10-2010 05:30 PM
getting rid of akonadi spoovy Slackware 15 08-05-2010 06:30 PM
Akonadi x42bn6 Linux - Newbie 5 12-11-2009 07:07 AM
akonadi won't start : libmysql.c error serafean Gentoo 2 07-18-2009 07:18 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:23 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration