[Akonadi] [Bug 374676] New: The Akonadi personal information management service is not operational

[Phillip Kruger]

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

Bug ID: 374676
   Summary: The Akonadi personal information management service is
not operational
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-bugs@kde.org
  Reporter: phillip.kru...@gmail.com
  Target Milestone: ---

Application: akonadiconsole (0.99)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.13-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
My Mail client (Kontact) reported "The Akonadi personal information management
service is not operational", so I try and open akonadi console, but then I get
this error. If I try and open akonadi on cmd line I get this:
cnf-lookup: error while loading shared libraries: libboost_system.so.1.60.0:
cannot open shared object file: No such file or directory

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Console (akonadiconsole), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f810f10af80 (LWP 11926))]

Thread 22 (Thread 0x7f8082ffd700 (LWP 11953)):
#0  0x7f810162c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f80fdf20639 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f80fdf20c39 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f80fdf20df0 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f80fdf1d78c in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f8101626454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f81089927df in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f80837fe700 (LWP 11952)):
#0  0x7f810898948d in poll () at /usr/lib/libc.so.6
#1  0x7f80e0960121 in  () at /usr/lib/libpulse.so.0
#2  0x7f80e09518f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#3  0x7f80e0951f8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f80e0952040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f80e0960069 in  () at /usr/lib/libpulse.so.0
#6  0x7f80df147ed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7f8101626454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f81089927df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f8083fff700 (LWP 11951)):
#0  0x7f810162c4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f80fdf14ac2 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f80fdf15375 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f80fdef6401 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f80fdf08604 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f80fdef2595 in  () at /usr/lib/libQt5WebEngineCore.so.5
#6  0x7f80fdf2141a in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7f80fdf1d78c in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7f8101626454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f81089927df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f80b0ff9700 (LWP 11950)):
#0  0x7f810162ef1c in __lll_lock_wait () at /usr/lib/libpthread.so.0
#1  0x7f8101628bb6 in pthread_mutex_lock () at /usr/lib/libpthread.so.0
#2  0x7f810f011255 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#3  0x7f81089c8a7d in do_dlopen () at /usr/lib/libc.so.6
#4  0x7f810f00d3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#5  0x7f81089c8b0f in dlerror_run () at /usr/lib/libc.so.6
#6  0x7f81089c8b82 in __libc_dlopen_mode () at /usr/lib/libc.so.6
#7  0x7f810899f8c5 in init () at /usr/lib/libc.so.6
#8  0x7f810162d6f9 in __pthread_once_slow () at /usr/lib/libpthread.so.0
#9  0x7f810899f9e4 in backtrace () at /usr/lib/libc.so.6
#10 0x7f80fded53be in  () at /usr/lib/libQt5WebEngineCore.so.5
#11 0x7f80fdeeca6e in  () at /usr/lib/libQt5WebEngineCore.so.5
#12 0x7f80fdeedc9c in  () at /usr/lib/libQt5WebEngineCore.so.5
#13 0x7f80fdee8711 in  () at /usr/lib/libQt5WebEngineCore.so.5
#14 0x7f80fdb7b8a0 in  () at /usr/lib/libQt5WebEngineCore.so.5
#15 0x7f80fdb7bf3e in  () at /usr/lib/libQt5WebEngineCore.so.5
#16 0x7f80fdb7c709 in  () at /usr/lib/libQt5WebEngineCore.so.5
#17 0x7f80fdb7c041 in  () at /usr/lib/libQt5WebEngineCore.so.5
#18 0x7f80fdb7ee38 in  () at /usr/lib/libQt5WebEngineCore.so.5
#19 0x7f80fdecc96e in  () at /usr/lib/libQt5WebEngineCore.so.5
#20 0x7f80fdeccafe in  () at /usr/lib/libQt5WebEngineCore.so.5
#21 0x7f80f1112a12 in event_base_loop () at /usr/lib/libevent-2.0.so.5
#22 0x7f80fdecbe8a in  () at /usr/lib/libQt5WebEngineCore.so.5
#23 0x7f80fdf08604 in  () at /usr/lib/libQt5WebEngineCore.so.5
#24 0x7f80fdef2595 in  () at /usr/lib/libQt5WebEngineCore.so.5
#25 0x7f80fdf2141a in  () at 

[kmail2] [Bug 368963] Freeze on send confirmation after spell check dialog.

[bugzilla_noreply]

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

k...@douglasmcmillan.com changed:

   What|Removed |Added

 CC||k...@douglasmcmillan.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 372973] missing Help handbook

[Nick Levinson]

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

--- Comment #6 from Nick Levinson  ---
GUI/CLI followup (especially @Burkhard Lueck): Apparently, KHelpCenter is
available but only through a command line interface
(https://forums.opensuse.org/showthread.php/391430-Khelpcenter-for-OpenSuSE-where-do-I-find-it?p=1848523#post1848523)
or the KDE Plasma Workspace (one graphical user interface), not the Gnome or
IceWM desktop environment GUIs. I asked about the CLI preference at a forum
(https://forums.opensuse.org/showthread.php/521603-why-need-CLI-console-to-use-GUI-KMail-Help?p=2803654#post2803654)
before I knew it worked in KDE's DE but no one replied. Why isn't KHelpCenter
working in whatever GUI desktop environment we happen to be using? Are you
getting it in any GUI other than KDE? If not, then this may need an enhancement
request somewhere, probably first within KDE to make KHelpCenter compatible
with a competitor's GUI. An alternative would be a message that, instead of
saying essentially that we can't use the help, would say to switch DEs.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 320529] maildir resource not working

[bugzilla_noreply]

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

kram...@web.de changed:

   What|Removed |Added

 CC||kram...@web.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly

[bugzilla_noreply]

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

--- Comment #10 from kram...@web.de ---
Created attachment 103245
  --> https://bugs.kde.org/attachment.cgi?id=103245=edit
akonadi_davgroupware_resource 16.12.0-1 crashlog with debug symbols

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly

[bugzilla_noreply]

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

kram...@web.de changed:

   What|Removed |Added

 CC||kram...@web.de

--- Comment #9 from kram...@web.de ---
Same here on Arch Linux with kdepim-runtime/kde-applications-meta 16.12-1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 374667] New: Crash opening akregator from kontact

[bugzilla_noreply]

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

Bug ID: 374667
   Summary: Crash opening akregator from kontact
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rjwgn...@yahoo.com
  Target Milestone: ---

Application: kontact (5.3.3 (QtWebEngine))

Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.8.15-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
New upgrade to Fedora 24. When I start kontact (kontact-16.08.3-2.fc24.x86_64,
akregator-16.08.3-2.fc24.x86_64), then switching to my feeds, I am told that
"Akregator did not close correctly. Would you like to restore the previous
session?".  Selecting either "Restore Session" or "Do Not Restore Session"
causes this crash. I have not tried "Ask me later".

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2027f49940 (LWP 4062))]

Thread 41 (Thread 0x7f1ee3857700 (LWP 4213)):
#0  0x7f2038859f79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f203c9c2c22 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f203c9d1581 in base::PosixDynamicThreadPool::WaitForTask() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f203c9d1aad in base::(anonymous
namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5
#4  0x7f203c9cac2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f20388545ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f20400d80ed in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7f1ee4058700 (LWP 4212)):
#0  0x7f2038859f79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f203c9c2c22 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f203c9d1581 in base::PosixDynamicThreadPool::WaitForTask() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f203c9d1aad in base::(anonymous
namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5
#4  0x7f203c9cac2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f20388545ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f20400d80ed in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7f1ee726d700 (LWP 4207)):
#0  0x7f2038859f79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f203c9c2c22 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f203c9d1581 in base::PosixDynamicThreadPool::WaitForTask() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f203c9d1aad in base::(anonymous
namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5
#4  0x7f203c9cac2d in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f20388545ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f20400d80ed in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7f1ee8dea700 (LWP 4124)):
#0  0x7f20400cc56d in poll () at /lib64/libc.so.6
#1  0x7f2036b9fa06 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f2036b9fb1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f2040ed275b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f2040e8181a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f2040ce0353 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f2040ce49ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f20388545ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f20400d80ed in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7f1ee95eb700 (LWP 4122)):
#0  0x7f2036be3a24 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f2036b9f599 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#2  0x7f2036b9fa70 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f2036b9fb1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f2040ed275b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f2040e8181a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f2040ce0353 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f2040ce49ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f20388545ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f20400d80ed in clone () at 

[Akonadi] [Bug 372712] Protocol::HelloResponse not correctly parsed, the object is just a Command with type set

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

Summary|akonadi_imap_resource   |Protocol::HelloResponse not
   |crashed while I had KMail   |correctly parsed, the
   |open in background  |object is just a Command
   ||with type set

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.

[Akonadi] [Bug 373242] Crash in akonadi_indexing_agent unknown cause processing emails received

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 372712 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 372712] akonadi_imap_resource crashed while I had KMail open in background

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||shawn.st...@rogers.com

--- Comment #4 from Daniel Vrátil  ---
*** Bug 373242 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.

[Akonadi] [Bug 372712] akonadi_imap_resource crashed while I had KMail open in background

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||dvra...@kde.org
  Component|IMAP resource   |libakonadi
   Assignee|chrig...@fastmail.fm|kdepim-bugs@kde.org

--- Comment #3 from Daniel Vrátil  ---
Moving to libakonadi, this is a generic problem in Protocol (?), looks like the
the command is not actually a HelloResponse, despite having the type set to
Hello. Possibly the Response bit is not set when sent from the server?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

[Akonadi] [Bug 373143] KDE Crashed when I configuring Digital Clock

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 368832 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 372914] Digital clock setting crash

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 368832 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||peter.fink...@inode.at

--- Comment #11 from Daniel Vrátil  ---
*** Bug 373989 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373989] Kmail 5.4 / akonadi agents hogging cpu cores

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 373443 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 368161] Plasma (plasmashell), signal: Segmentation fault

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||dvra...@kde.org

--- Comment #4 from Daniel Vrátil  ---
This should be fixed since kdepim-addons-5.3.3 (KDE Applications 16.08.3).

*** This bug has been marked as a duplicate of bug 368832 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373111] Crash During Start Up After Login

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||dvra...@kde.org

--- Comment #9 from Daniel Vrátil  ---
This has been fixed in KDE Applications 16.12 release.

*** This bug has been marked as a duplicate of bug 372824 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 372824] PIM Events Plugin crashes plasmashell

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||bj.kdede...@bkaj.org

--- Comment #2 from Daniel Vrátil  ---
*** Bug 373111 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Daniel Vrátil]

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

--- Comment #10 from Daniel Vrátil  ---
*** Bug 373442 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373442] Migration Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 373443 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Daniel Vrátil]

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

--- Comment #9 from Daniel Vrátil  ---
*** Bug 373441 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373441] Archive Mail Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||dvra...@kde.org

--- Comment #3 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 373443 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373444] Notes Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Daniel Vrátil  ---
Workaround: stop Akonadi and remove
~/.config/akonadi/agent_config_akonadi_notes_agent_X_changes.dat.

The problem is caused by the journal file being corrupted. The latest
stable/master has a fix that prevents getting stuck on corrupted files and also
fixes the bug that caused the corruption in the first place.

*** This bug has been marked as a duplicate of bug 373443 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Daniel Vrátil]

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

--- Comment #8 from Daniel Vrátil  ---
*** Bug 373444 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 374636] akonadi does not start after restore

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
> log_akonadiserver: stderr: "170106 15:35:40 [Note] /usr/sbin/mysqld (mysqld 
> 10.0.28-MariaDB) starting as process 9072 ...\n"
> log_akonadiserver: exit code: 1

Looks like mysqld dies on start up. Maybe the database is corrupted? Can happen
if you did the backup while MySQL was running and possibly changing and not
fully flushing all the data files.


> docb@T520:~> /usr/sbin/mysqld 
> --defaults-file=/home/docb/.local/share/akonadi/mysql.conf 
> --datadir=/home/docb/.local/share/akonadi/db_data/ 
> --socket=/tmp/akonadi-docb.uL1G8Q/mysql.socket
>   
> 
> 170106 15:41:07 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB) starting as 
> process 9147 ...

Does the mysqld process return immediately, or does it keep running? If it
returns, then it mean it still crashed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 374086] random crash after deleting a message

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
Looks like a search update in a search collection not known to KMail.

Can you reproduce? Would be helpful to know which Collection it is (at least
get the collectionId value) that we get an assert for.

If it's not a mail search collection, then we could try to debug why KMail got
a notification for a non-mail collection. If it's a mail search collection,
then we can debug why ETM does not know about it.

In the worst case, we can simply handle the situation gracefully and return
from ETMPrivate::monitoredItemLinked() early instead of asserting.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)

[Christophe Giboudeaux]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

   Assignee|kdepim-bugs@kde.org |k...@davidedmundson.co.uk

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 374514] Crash on akonadictl stop

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
This crash hopefully should be fixed in upcoming 5.4.1 release (KDE
Applications 16.12.1). Lets retest once it's released.


The transaction deadlocks are a known problem. We have some handling for that,
but it does not work 100%.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 374653] New: System tray icon empty when there are unread feeds

[Matthijs]

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

Bug ID: 374653
   Summary: System tray icon empty when there are unread feeds
   Product: akregator
   Version: 5.4.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mtijink.b...@gmail.com
  Target Milestone: ---

When there are unread feeds, the akregator icon is "empty": it is still there,
takes space, and can be clicked, but does not show any icon, just empty space.

The icon appears again when all feeds are read. This used to work in previous
versions of akregator.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 374644] New: Crashes while changing settings

[Eric]

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

Bug ID: 374644
   Summary: Crashes while changing settings
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: eric.v...@msg4.us
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Changing defalt send-email folder adress
- Custom settings of the application:
many accounts, many identity and aliases, many-many filters, and all main
Kontact/Akonady folders are simlinked to a (safe) different partition on a
different hard drive

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9229da87c0 (LWP 14135))]

Thread 27 (Thread 0x7f90ec9b3700 (LWP 14214)):
#0  0x7ffeee977b26 in clock_gettime ()
#1  0x7f92269fbc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f92273a97d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f92275293b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9227529945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f922752ab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f921f5474ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f921f547d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f921f547f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f922752ad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f92274d1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f92272f361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f92272f832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f916d93b700 (LWP 14213)):
#0  0x7f921fd6903f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f921401b86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f921401b899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f916e491700 (LWP 14210)):
#0  0x7f92269e6bfd in poll () at /lib64/libc.so.6
#1  0x7f921f547e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f921f547f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f922752ad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f92274d1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f92272f361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f92272f832f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f916f7fe700 (LWP 14175)):
#0  0x7ffeee977b26 in clock_gettime ()
#1  0x7f92269fbc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f92273a97d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f92275293b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9227529945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f922752ab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f921f5474ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f921f547d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f921f547f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f922752ad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f92274d1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f92272f361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f92272f832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f916700 (LWP 14173)):
#0  0x7ffeee977b26 in clock_gettime ()
#1  0x7f92269fbc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f92273a97d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f92275293b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9227529945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f922752ab5e in  () at /usr/lib64/libQt5Core.so.5
#6  

[kontact] [Bug 374643] New: Crashes while changing defalut settings

[Eric]

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

Bug ID: 374643
   Summary: Crashes while changing defalut settings
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: eric.v...@msg4.us
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Changing the "sent email" box address for one of my accounts
- Custom settings of the application:
Many accounts, many identity, many-many filters

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f648bcc97c0 (LWP 13967))]

Thread 27 (Thread 0x7f634e836700 (LWP 14102)):
#0  0x7ffec0afbb26 in clock_gettime ()
#1  0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f64892ca7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f648944bb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f64814684ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f6481468d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f6481468f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f648944bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f64893f2d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f648921932f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f648891002d in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f63cf7be700 (LWP 14101)):
#0  0x7f6481c8a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6475f3c86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f6475f3c899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f648891002d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f63d4dea700 (LWP 14081)):
#0  0x7ffec0afbb26 in clock_gettime ()
#1  0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f64892ca7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f648944bb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f64814684ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f6481468d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f6481468f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f648944bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f64893f2d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f648921932f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f648891002d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f63d55eb700 (LWP 14047)):
#0  0x7f6488903ccd in read () at /lib64/libc.so.6
#1  0x7f64814a9b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6481468999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6481468df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f6481468f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f648944bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f64893f2d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f648921932f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f648891002d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f63d5dec700 (LWP 14046)):
#0  0x7ffec0afbb26 in clock_gettime ()
#1  0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f64892ca7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  

[kontact] [Bug 374642] New: Crashes while changing account settings

[Eric]

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

Bug ID: 374642
   Summary: Crashes while changing account settings
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: eric.v...@msg4.us
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was changing the trashbox settings and the expiring settings for one of my
accounts
- Custom settings of the application:
many accounts, many identity, many-many filters

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fea0ae807c0 (LWP 2637))]

Thread 26 (Thread 0x7fe94d659700 (LWP 13897)):
#0  0x7fea00e4103f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe9f50f386b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fe9f50f3899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7fe94ce58700 (LWP 3502)):
#0  0x7ffcfe7e5b26 in clock_gettime ()
#1  0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fea084817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fea08602b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fea0061f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fea0061fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fea0061ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fea08602d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fea085a9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fea083d032f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7fe94fde8700 (LWP 2705)):
#0  0x7ffcfe7e5b26 in clock_gettime ()
#1  0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fea084817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fea08602b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fea0061f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fea0061fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fea0061ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fea08602d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fea085a9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fea083d032f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7fe9505e9700 (LWP 2678)):
#0  0x7fea07abaccd in read () at /lib64/libc.so.6
#1  0x7fea00660b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fea0061f999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fea0061fdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fea0061ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fea08602d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fea085a9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fea083d032f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7fe950dea700 (LWP 2676)):
#0  0x7ffcfe7e5b26 in clock_gettime ()
#1  0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fea084817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5

[Akonadi] [Bug 374636] New: akonadi does not start after restore

[Axel Braun]

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

Bug ID: 374636
   Summary: akonadi does not start after restore
   Product: Akonadi
   Version: 5.3.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

I had a HD failure, did a new installation of Leap 42.2 and restored the /home
tree from a backup.
Akonadi does now refuse to start:
docb@T520:~> akonadiconsole
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
 void AdblockManager::reloadConfig() false   
AdBlock::AdblockManager(0x2ab1db0)
log_akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid
name"
log_akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid
name"
org.kde.akonadi.ETM: GEN true true true
org.kde.akonadi.ETM: collection: QVector()
QSqlQuery::prepare: database not open
QSqlDatabasePrivate::removeDatabase: connection 'qt_sql_default_connection' is
still in use, all queries will cease to work.
log_akonadiserver: Database process exited unexpectedly during initial
connection!
log_akonadiserver: executable: "/usr/sbin/mysqld"
log_akonadiserver: arguments:
("--defaults-file=/home/docb/.local/share/akonadi/mysql.conf",
"--datadir=/home/docb/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-docb.uL1G8Q/mysql.socket")
log_akonadiserver: stdout: ""
log_akonadiserver: stderr: "170106 15:35:40 [Note] /usr/sbin/mysqld (mysqld
10.0.28-MariaDB) starting as process 9072 ...\n"
log_akonadiserver: exit code: 1
log_akonadiserver: process error: "Unknown error"
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/tmp/akonadi-docb.uL1G8Q/mysql.socket' (2 "No such file or directory")'
Check that mysqld is running and that the socket:
'/tmp/akonadi-docb.uL1G8Q/mysql.socket' exists!
log_akonadiserver: Failed to remove Unix socket
log_akonadiserver: Failed to remove runtime connection config file
log_akonadicontrol: Application 'akonadiserver' exited normally...
log_akonadicore: "Unbekannter Fehler."
log_akonadicore: Job error:  "Unbekannter Fehler." for collection: QVector() 

when I try to start mysql manually:
docb@T520:~> /usr/sbin/mysqld
--defaults-file=/home/docb/.local/share/akonadi/mysql.conf
--datadir=/home/docb/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-docb.uL1G8Q/mysql.socket  
170106 15:41:07 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB) starting as
process 9147 ...

-> seems to work.
Now lets try again:

docb@T520:~> akonadictl start
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
docb@T520:~> log_akonadiserver: Database process exited unexpectedly during
initial connection!
log_akonadiserver: executable: "/usr/sbin/mysqld"
log_akonadiserver: arguments:
("--defaults-file=/home/docb/.local/share/akonadi/mysql.conf",
"--datadir=/home/docb/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-docb.uL1G8Q/mysql.socket")
log_akonadiserver: stdout: ""
log_akonadiserver: stderr: "170106 15:41:26 [Note] /usr/sbin/mysqld (mysqld
10.0.28-MariaDB) starting as process 9174 ...\n"
log_akonadiserver: exit code: 1
log_akonadiserver: process error: "Unknown error"
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/tmp/akonadi-docb.uL1G8Q/mysql.socket' (2 "No such file or directory")'
Check that mysqld is running and that the socket:
'/tmp/akonadi-docb.uL1G8Q/mysql.socket' exists!
log_akonadiserver: Failed to remove Unix socket
log_akonadiserver: Failed to remove runtime connection config file
log_akonadicontrol: Application 'akonadiserver' exited normally...

Does not start!
Any idea? Need to access my mails!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)

[bugzilla_noreply]

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

bjoe...@arcor.de changed:

   What|Removed |Added

 CC||bjoe...@arcor.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 131106] copy link address not available from right-click menu when viewing article

[Daniel Morris]

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

Daniel Morris  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Daniel Morris  ---
no longer relevant

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 368113] invalid signature when using vcard

[bugzilla_noreply]

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

tprotopope...@gmail.com changed:

   What|Removed |Added

 CC||tprotopope...@gmail.com

--- Comment #1 from tprotopope...@gmail.com ---
I have something similar, so may be related, however, I am using openPGP
instead.

Setting the option of adding 'own vcard' to an identity makes a signature for
an email come up with 'not enough information to check signature validity'.

To reproduce:

1. Create an identity, with a signing key etc.
2. In the 'advanced' tab for configuring the identity select 'add own vcard'
and fill in the card if needed.
3. Send a signed email with that identity, which will have the vcard
automatically attached.
4. In the sent mail folder, or in inbox, the email displays 'not enough
information to check signature validity', even though it is signed with my own
key.

Without automatically attaching a vcard per step 2, but adding one manually
through 'new message -> attach -> attach -> attach vcards... -> select vcard
from addressbooks', the signature is recognised as valid. Attaching a file also
works fine.

Reproducilbe: always.

Kmail 5.4.0
Framework 5.29.0
Plasma 5.8.4
Qt 5.7.1
gpg (GnuPG) 2.1.16
libgcrypt 1.7.3

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373441] Archive Mail Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Gunter Ohrner]

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

--- Comment #2 from Gunter Ohrner  ---
Related to bug 373443, appears to be fixed on master and branch head.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373444] Notes Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Gunter Ohrner]

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

--- Comment #2 from Gunter Ohrner  ---
Related to bug 373443, appears to be fixed on master and branch head.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373442] Migration Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Gunter Ohrner]

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

--- Comment #3 from Gunter Ohrner  ---
Related to bug 373443, appears to be fixed on master and branch head.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Gunter Ohrner]

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

--- Comment #7 from Gunter Ohrner  ---
@Laurent: Sorry for the late reply. As kMail did not work for me any more with
this bug, I had to switch to Thunderbird for the meantime - and I did not
notice that I had not subscribed to the IMAP folder where my KDE Bugzilla
notifications end up, so I missed your question... :-(

(I configured kMail to show all folders regardless of subscription state.)

So that I've now seen your question (and tons of others) is an indication that
it's working for me again since yesterdays update. :)

Interestingly, KDE PIM Runtime which contains the mail agent was not changed
during this update, but Akonadi was upgraded to
4:16.12.0+p16.04+git20170104.0343-0 (KDE Neon package).

So if this fix was contained therein, it helps. If it wasn't, the issue was
caused by something else.

-- 
You are receiving this mail because:
You are the assignee for the bug.