[Akonadi] [Bug 267864] migration of akonadi_mixedmaildir_resource fails

[Frits Spieker via KDE Bugzilla]

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

--- Comment #4 from Frits Spieker  ---
AFAIK it works fine now. I have quite some local mail folders and they all show
up just fine.

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

[Akonadi] [Bug 246195] Cannot create Google Contacts akonadi resource [strlen, strdup,extract_and_check_multi, ..., gcal_get_contacts]

[Frits Spieker via KDE Bugzilla]

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

--- Comment #51 from Frits Spieker  ---
No longer present. Works fine now.

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

[kmail2] [Bug 310897] Reading mbox files is extremely slow and often fails to show message body

[Frits Spieker via KDE Bugzilla]

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

--- Comment #4 from Frits Spieker  ---
As far as I know the bug is no longer there.

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

[kontact] [Bug 369118] New: Multiple selection of "find in message" causes crash

[Frits Spieker via KDE Bugzilla]

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

Bug ID: 369118
   Summary: Multiple selection of "find in message" causes crash
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: s.pa...@spiekerbros.com

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: I was searching for a specific
message so selected "find in message". The "search box" appeared at the bottom
of the screen (so far so good). When I clicked "search in message" again, the
application crashed. Tried again, but have not yet been able to reproduce.

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

Thread 41 (Thread 0x7fbd177fe700 (LWP 3258)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbda9ffb353 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa331971 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7fbd17fff700 (LWP 3257)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbda9ffb353 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa331971 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7fbd1cdf4700 (LWP 3256)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbda9ffb353 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa331971 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7fbd1d5f5700 (LWP 3255)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbda9ffb353 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa331971 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7fbd1ddf6700 (LWP 3254)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbda9ffb353 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa331971 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 36 (Thread 0x7fbd1e5f7700 (LWP 3253)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbda9ffb353 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa331971 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7fbd1edf8700 (LWP 3252)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbda9ffa201 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa331971 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 34 (Thread 0x7fbd77fff700 (LWP 3251)):
#0  0x7fbebfc4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbdaa300c4b in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fbdaa300c89 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fbebfc45454 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbec3da03ff in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7fbd6e6ee700 (LWP 3214)):
#0  0x7fbec3dacc1f in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7fbec3d976e2 in poll () at /lib64/libc.so.6
#2  0x7fbebeff5016 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fbebeff512c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fbec48d6aab in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fbd640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fbec487e6fa in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fbd6e6edc80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fbec46a43c3 in QThread::exec() (this=) at
thread/qthread.cpp:500
#7  0x7fbec46a92e8 in QThreadPrivate::start(void*) (arg=0x15e3da0) at
thread/

[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.

[Frits Spieker via KDE Bugzilla]

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

--- Comment #5 from Frits Spieker  ---
Not to be blunt, but deleting all imap accounts, dropping and recreating the
akonadi database and recreating of all imap accounts is not what I would call
resolved. It is a messy workaround and a very messy one at that. What about
users that also still have pop3 email boxes? What about the less technical
inclined? 
It's a messy workaround which hides a messy bug which is in need of a proper
fix.

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

[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.

[Frits Spieker via KDE Bugzilla]

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

Frits Spieker  changed:

   What|Removed |Added

 CC||s.pa...@spiekerbros.com

--- Comment #1 from Frits Spieker  ---
I am "glad" I am not the only one. Have exactly the same error.

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