[Akonadi] [Bug 392092] akonadi_control crash on first start

[Wolfgang Bauer]

https://bugs.kde.org/show_bug.cgi?id=392092

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||freekdekru...@kde.nl

--- Comment #25 from Wolfgang Bauer  ---
*** Bug 409584 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Daniel Vrátil]

https://bugs.kde.org/show_bug.cgi?id=392092

Daniel Vrátil  changed:

   What|Removed |Added

   Version Fixed In||19.04.3
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/ako
   ||nadi/c21bb5220a3ae835a5183a
   ||fd58c186ba21f6c93d

--- Comment #24 from Daniel Vrátil  ---
Git commit c21bb5220a3ae835a5183afd58c186ba21f6c93d by Daniel Vrátil.
Committed on 28/06/2019 at 15:13.
Pushed by dvratil into branch 'Applications/19.04'.

Fix race-condition on akonadi_control start

Summary:
Check that there are no other akonadi_control instances running as the
very first thing on startup. Previously this check would happen after
AkApplication initialization, which contains some potential race-
conditions, like rotating log files.

The situation when akonadi_control is launched multiple times can occur
on session startup, when multiple different components will attempt to
launch Akonadi if its not yet running.
FIXED-IN: 19.04.3

Reviewers: #kde_pim, vkrause

Reviewed By: #kde_pim, vkrause

Subscribers: kde-pim

Tags: #kde_pim

Differential Revision: https://phabricator.kde.org/D22092

M  +2-14   src/akonadicontrol/main.cpp
M  +3-4src/shared/akapplication.cpp
M  +43   -6src/shared/akapplication.h

https://commits.kde.org/akonadi/c21bb5220a3ae835a5183afd58c186ba21f6c93d

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Till Schäfer]

https://bugs.kde.org/show_bug.cgi?id=392092

Till Schäfer  changed:

   What|Removed |Added

 CC||till2.schaefer@uni-dortmund
   ||.de

--- Comment #23 from Till Schäfer  ---
I can confirm the crash on every start with akonadi_control 5.11.2:

Cannot remove old log file '%s': %s") at global/qlogging.cpp:887

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[tom]

https://bugs.kde.org/show_bug.cgi?id=392092

tom  changed:

   What|Removed |Added

 CC||vdx55...@bcaoo.com

--- Comment #22 from tom  ---
Same here with gentoo amd64, akonadi version 5.10.3
I was able to get a konsole output that tells the log file name when I start
kmail for the first time after reboot:

Cannot rename log file '/home/tom/.local/share/akonadi/akonadi_control.error'
to '/home/tom/.local/share/akonadi/akonadi_control.error.old': Cannot create
/home/tom/.local/share/akonadi/akonadi_control.error.old for output 
 KCrash: Application 'akonadi_control' crashing... 
 KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit 
 sock_file=/var/run/user/1000/kdeinit5__0 
 Nouveau openGL driver detected. Qt WebEngine will disable usage of the GPU. 
 Note: you can set the QT_WEBENGINE_DISABLE_NOUVEAU_WORKAROUND 
 environment variable before running this application, but this is 
 not recommended since this usually causes applications to crash as 
 Nouveau openGL drivers don't support multithreaded rendering 
 QDBusConnection: name 'org.kde.kwalletd5' had owner '' but we thought it was
':1.60'

Created an additional patch to get some more debug information:

--- a/src/shared/akdebug.cpp.a   2019-03-03 23:03:57.0 +0100 
 +++ b/src/shared/akdebug.cpp 2019-06-11 18:57:00.375941258 +0200 
 @@ -200,6 +200,8 @@ void akInit(const QString ) 
  const auto errorLogFile = DebugPrivate::errorLogFileName(name); 
  QFileInfo infoOld(errorLogFile + QLatin1String(".old")); 
  if (infoOld.exists()) { 
 +   qCritical("Old log file '%s' exists.
deleting...",qUtf8Printable(infoOld.fileName())); 
  QFile fileOld(infoOld.absoluteFilePath()); 
 +   qCritical("Old log file (complete) '%s' exists.
deleting...",qUtf8Printable(fileOld.fileName())); 
  const bool success = fileOld.remove(); 
  if (!success) { 
 @@ -207,6 +208,8 @@ void akInit(const QString ) 
  qUtf8Printable(fileOld.fileName()), 
  qUtf8Printable(fileOld.errorString())); 
  } 
 +} else { 
 +   qCritical("Old log file '%s' does not
exist",qUtf8Printable(infoOld.fileName())); 
  } 

  QFileInfo info(errorLogFile); 
 @@ -219,7 +222,11 @@ void akInit(const QString ) 
 qUtf8Printable(file.fileName()), 
 qUtf8Printable(oldName), 
 qUtf8Printable(file.errorString())); 
 +} else { 
 + qCritical("log file '%s' renamed",qUtf8Printable(file.fileName())); 
  } 
 +} else { 
 +   qCritical("no log file to rename."); 
  } 

  QtMessageHandler origHandler = qInstallMessageHandler(akMessageHandler);


which results in this output when akonadi crashes:

Old log file 'akonadi_control.error.old' exists. deleting... 
 Old log file (complete)
'/home/tom/.local/share/akonadi/akonadi_control.error.old' exists. deleting... 
 Cannot rename log file '/home/tom/.local/share/akonadi/akonadi_control.error'
to '/home/tom/.local/share/akonadi/akonadi_control.error.old': Cannot create
/home/tom/.local/share/akonadi/akonadi_control.error.old for output 
 KCrash: Application 'akonadi_control' crashing... 
 KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit 
 sock_file=/var/run/user/1000/kdeinit5__0 
 Nouveau openGL driver detected. Qt WebEngine will disable usage of the GPU. 
 Note: you can set the QT_WEBENGINE_DISABLE_NOUVEAU_WORKAROUND 
 environment variable before running this application, but this is 
 not recommended since this usually causes applications to crash as 
 Nouveau openGL drivers don't support multithreaded rendering 
 QDBusConnection: name 'org.kde.kwalletd5' had owner '' but we thought it was
':1.53'

the log files are in my home folder and there are no access restrictions for my
user for the folder or the files. I can rename or delete the files manually
without error messages.
It looks to me like the deletion of the .old file is not done even if
fileOld.remove() returns success, or if there is some kind of race condition
(this is all wild guess).

Also reported here:
https://forums.gentoo.org/viewtopic-t-1092660.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

Christoph Feck  changed:

   What|Removed |Added

 CC||p...@jaoplusnet.plus.com

--- Comment #21 from Christoph Feck  ---
*** Bug 407070 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #20 from Christoph Feck  ---
Martin, could you please add the Konsole output? It should show which files it
fails to rename, and why.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #19 from Christoph Feck  ---
*** Bug 406038 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=392092

maxime.haselba...@googlemail.com changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #18 from Martin Tlustos  ---
Still happening

Operating System: KDE neon 5.15
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.0
Kernel Version: 4.15.0-46-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 7,7 GiB

Crash info:
Application: akonadi_control (akonadi_control), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcc0ea82800 (LWP 11570))]

Thread 2 (Thread 0x7fcc03050700 (LWP 11572)):
#0  0x7fcc0c4f3bf9 in __GI___poll (fds=0x7fcc0304fcb8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fcc089d3747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fcc089d536a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fcc045cb32a in QXcbEventQueue::run (this=0x560046f45200) at
qxcbeventqueue.cpp:225
#4  0x7fcc0ce18bc2 in QThreadPrivate::start (arg=0x560046f45200) at
thread/qthread_unix.cpp:361
#5  0x7fcc0c1c76db in start_thread (arg=0x7fcc03050700) at
pthread_create.c:463
#6  0x7fcc0c50088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fcc0ea82800 (LWP 11570)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7fcc0c41f801 in __GI_abort () at abort.c:79
#8  0x7fcc0cdf4e7b in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1901
#9  QMessageLogger::fatal (this=this@entry=0x7ffe85788010,
msg=msg@entry=0x5600461de1a0 "Cannot rename log file '%s' to '%s': %s") at
global/qlogging.cpp:887
#10 0x5600461d2701 in akInit (appName=...) at ./src/shared/akdebug.cpp:218
#11 0x5600461d0762 in AkApplicationBase::init (this=0x7ffe857881b0) at
./src/shared/akapplication.cpp:62
#12 0x5600461b1138 in AkApplicationImpl::AkApplicationImpl
(loggingCategory=..., argv=0x7ffe85788318, argc=@0x7ffe8578812c: 1,
this=0x7ffe857881b0) at ./src/shared/akapplication.h:83
#13 main (argc=, argv=0x7ffe85788318) at
./src/akonadicontrol/main.cpp:55

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #17 from Christoph Feck  ---
*** Bug 404390 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

Christoph Feck  changed:

   What|Removed |Added

 CC||jerry.fl...@gmail.com

--- Comment #16 from Christoph Feck  ---
*** Bug 404414 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

Christoph Feck  changed:

   What|Removed |Added

 CC||mcd...@gmail.com

--- Comment #15 from Christoph Feck  ---
*** Bug 382833 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

Christoph Feck  changed:

   What|Removed |Added

 CC||maxime.haselbauer@googlemai
   ||l.com

--- Comment #14 from Christoph Feck  ---
*** Bug 402619 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Daniel Vrátil]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #13 from Daniel Vrátil  ---
Git commit 4bd807c28663556c7e84c841d45f2d31803755bb by Daniel Vrátil.
Committed on 05/07/2018 at 13:55.
Pushed by dvratil into branch 'Applications/18.04'.

akInit: improve error message when renaming old logfiles fails

Tell us which file caused the error and what the error was.

M  +9-3src/shared/akdebug.cpp

https://commits.kde.org/akonadi/4bd807c28663556c7e84c841d45f2d31803755bb

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[PK]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #12 from PK  ---
I installed a package called mariadb-server and it seems as if things are
better now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[PK]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #11 from PK  ---
After starting up kmail I get this grey screen. But I can access the settings.
When I start the account-wizzard from there after a while the akonadi self-test
starts. And again it says that "akonadi is not registered at dbus".

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[PK]

https://bugs.kde.org/show_bug.cgi?id=392092

PK  changed:

   What|Removed |Added

 CC||pieterkristen...@gmail.com

--- Comment #10 from PK  ---
I have the same experience. I think it started from the moment I installed
plasma 5.13 on my system. I'm using KDE Neon user build.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[BingMyBong]

https://bugs.kde.org/show_bug.cgi?id=392092

BingMyBong  changed:

   What|Removed |Added

 CC||bingmyb...@btinternet.com

--- Comment #9 from BingMyBong  ---
Happening on opensuse:tumbleweed:20180613 as well
Qt: 5.11.0 KDE Frameworks: 5.46.0 - KDE Plasma:  5.13.0 - kwin 5.13.0
kmail2 5.8.2 - akonadiserver 5.8.2 - Kernel:  4.16.12-3-default  - 

Application: akonadi_control (akonadi_control), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5d3dff6800 (LWP 9255))]

Thread 2 (Thread 0x7f5d310ee700 (LWP 9256)):
#0  0x7f5d3bb3c5d9 in poll () from /lib64/libc.so.6
#1  0x7f5d381ea377 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f5d381ebf8a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f5d340c8939 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f5d3c47993c in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f5d3b834554 in start_thread () from /lib64/libpthread.so.0
#6  0x7f5d3bb46fdf in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5d3dff6800 (LWP 9255)):
[KCrash Handler]
#6  0x7f5d3ba8424b in raise () from /lib64/libc.so.6
#7  0x7f5d3ba6d4f1 in abort () from /lib64/libc.so.6
#8  0x7f5d3c43a22b in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib64/libQt5Core.so.5
#9  0x562e57e1d93b in ?? ()
#10 0x562e57e40402 in ?? ()
#11 0x562e57e1daa8 in ?? ()
#12 0x7f5d3ba6f11b in __libc_start_main () from /lib64/libc.so.6
#13 0x562e57e1e1aa in _start ()

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Rex Dieter]

https://bugs.kde.org/show_bug.cgi?id=392092

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

--- Comment #8 from Rex Dieter  ---
Seeing another downstream user seemingly getting this semi-often,
https://bugzilla.redhat.com/show_bug.cgi?id=1448691

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #7 from Martin Tlustos  ---
more testing:
starting kmail from konsole will render the same error.
starting korganizer from konsole will crash akonadi_control, but with a
different error:
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kf5.kservice.services: KServiceTypeTrader: serviceType "KOrganizer/Part" not
found
akonadi.collectionattributetable   OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation  OK
akonadi.collectiontableOK
akonadi.flagtable  OK
akonadi.mimetypetable  OK
akonadi.parttable  OK
akonadi.parttypetable  OK
akonadi.pimitemflagrelationOK
akonadi.pimitemtable   OK
akonadi.pimitemtagrelation OK
akonadi.relationtable  OK
akonadi.relationtypetable  OK
akonadi.resourcetable  OK
akonadi.schemaversiontable OK
akonadi.tagattributetable  OK
akonadi.tagremoteidresourcerelationtable   OK
akonadi.tagtable   OK
akonadi.tagtypetable   OK
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
true
true
.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #6 from Martin Tlustos  ---
starting akonadi via akonadictl start does not produce any errors in konsole.
Starting kontact in konsole will produce the same "Cannot rename log file -
running on a readonly filesystem maybe?" error.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #5 from Martin Tlustos  ---
No connection to opening kwallet at first time after login either, I just
closed my wallet and let akonadi reopen it (with password etc.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #4 from Martin Tlustos  ---
It's all under my home folder, I have access to everything (although I redid
it, just to make sure...).
Again, the error is not reproduced if I stop kontact/akonadi and later restart
it. It just happens the first time after booting up the machine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #3 from Christophe Giboudeaux  ---
#9  QMessageLogger::fatal (this=this@entry=0x7fff8d48d930,
msg=msg@entry=0x437280 "Cannot rename log file - running on a readonly
filesystem maybe?") at global/qlogging.cpp:816

what kind of partition is that ? does your user have write access to
~/.config/akonadi* and ~/.local/share/akonadi ?

Any error in the dmesg output ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #2 from Martin Tlustos  ---
It now seems to happen every time. Crash information:

Application: akonadi_control (akonadi_control), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f5d3645a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f5d3645c02a in __GI_abort () at abort.c:89
#8  0x7f5d36e1f311 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1710
#9  QMessageLogger::fatal (this=this@entry=0x7fff8d48d930,
msg=msg@entry=0x437280 "Cannot rename log file - running on a readonly
filesystem maybe?") at global/qlogging.cpp:816
#10 0x0042d783 in akInit (appName=...) at
/workspace/build/src/shared/akdebug.cpp:215
#11 0x0042b792 in AkApplicationBase::init
(this=this@entry=0x7fff8d48dbf0) at
/workspace/build/src/shared/akapplication.cpp:61
#12 0x0040a0cb in AkApplicationImpl::AkApplicationImpl
(loggingCategory=..., argv=0x7fff8d48dd58, argc=@0x7fff8d48da5c: 1,
this=0x7fff8d48dbf0) at /workspace/build/src/shared/akapplication.h:83
#13 main (argc=1, argv=0x7fff8d48dd58) at
/workspace/build/src/akonadicontrol/main.cpp:55

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

Martin Tlustos  changed:

   What|Removed |Added

Version|unspecified |5.8.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=392092

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 392092] akonadi_control crash on first start

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=392092

--- Comment #1 from Martin Tlustos  ---
It seems that this crash occurs only if you start kontact right after computer
startup. If you start it after a while, the crash does not occur.

-- 
You are receiving this mail because:
You are watching all bug changes.