[Akonadi] [Bug 353304] New: Akonadi crashes while indexing IMAP resource

2015-09-28 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=353304

Bug ID: 353304
   Summary: Akonadi crashes while indexing IMAP resource
   Product: Akonadi
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: k...@kaishome.de
CC: kdepim-bugs@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.88.0)

Qt Version: 5.5.0
Operating System: Linux 4.2.0-gentoo-r1 x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed:

Everytime I booted the system, akonadi more or less reliably crashes.

Maybe related is this excerpt from the journal:

Sep 29 07:36:22 jupiter akonadi_maildir_resource[1576]: akonadiagentbase_log:
Item does not provide part "RFC822"
Sep 29 07:36:22 jupiter akonadi_maildir_resource[1576]: akonadiagentbase_log:
Item does not provide part "RFC822"
Sep 29 07:36:22 jupiter akonadi_invitations_agent[1552]: Failed to open
external payload: "/home/kakra/.local/share/akonadi/file_db_data/" "file to
open is a directory"
Sep 29 07:36:22 jupiter akonadi_invitations_agent[1552]: Failed to open
external payload: "/home/kakra/.local/share/akonadi/file_db_data/" "file to
open is a directory"

Sidenote:

Unfortunatly there also seems to be a bug in Dr. Konqi which does not really
let me report a crash as duplicate or possibly related report. The buttons are
non-functional (or missing in case of "this is a duplicate").

The crash can be reproduced sometimes.

-- Backtrace:
Application: Akonadi-Ressource (akonadi_imap_resource), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f16e9d8e880 (LWP 1541))]

Thread 4 (Thread 0x7f16e9277700 (LWP 1559)):
#0  0x00396c0df47d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x003bc9e0aa02 in poll (__timeout=-1, __nfds=1, __fds=0x7f16e9276c40)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x136cfc0, cond=cond@entry=0x136d000,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11-r1/work/libxcb-1.11/src/xcb_conn.c:459
#3  0x003bc9e0c4cf in xcb_wait_for_event (c=0x136cfc0) at
/var/tmp/portage/x11-libs/libxcb-1.11-r1/work/libxcb-1.11/src/xcb_in.c:623
#4  0x7f16e98dd989 in QXcbEventReader::run (this=0x137ad40) at
qxcbconnection.cpp:1197
#5  0x00386389f5c3 in QThreadPrivate::start (arg=0x137ad40) at
thread/qthread_unix.cpp:331
#6  0x00396c808224 in start_thread (arg=0x7f16e9277700) at
pthread_create.c:310
#7  0x00396c0e80cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f16e33d7700 (LWP 1764)):
#0  0x00396c0df47d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x0034d3a48bc4 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f16dc003020, timeout=-1, context=0x7f16dc000990) at
/var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7f16dc000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c:3803
#3  0x0034d3a48cdc in g_main_context_iteration (context=0x7f16dc000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c:3869
#4  0x003863a8873b in QEventDispatcherGlib::processEvents
(this=0x7f16dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x003863a3d29b in QEventLoop::exec (this=this@entry=0x7f16e33d6d50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x00386389aeba in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x00386389f5c3 in QThreadPrivate::start (arg=0x14b7430) at
thread/qthread_unix.cpp:331
#8  0x00396c808224 in start_thread (arg=0x7f16e33d7700) at
pthread_create.c:310
#9  0x00396c0e80cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f16e23d5700 (LWP 1807)):
#0  0x00386387ce70 in g_main_context_iteration@plt () from
/usr/lib64/libQt5Core.so.5
#1  0x003863a8873b in QEventDispatcherGlib::processEvents
(this=0x7f16d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#2  0x003863a3d29b in QEventLoop::exec (this=this@entry=0x7f16e23d4d50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#3  0x00386389aeba in QThread::exec (this=) at
thread/qthread.cpp:503
#4  0x00386389f5c3 in QThreadPrivate::start (arg=0x14b7dc0) at
thread/qthread_unix.cpp:331
#5  0x00396c808224 in start_thread (arg=0x7f16e23d5700) at
pthread_create.c:310
#6  0x00396c0e80cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f16e9d8e880 (LWP 1541)):
[KCrash Handler]
#6  0x00396c034ee7 in __GI_raise 

[kmail2] [Bug 277007] KMail2 full search of emails does not work

2015-09-28 Thread Andrew Gaydenko
https://bugs.kde.org/show_bug.cgi?id=277007

Andrew Gaydenko  changed:

   What|Removed |Added

 CC|a...@gaydenko.com  |

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 353288] New: pgp signed emails crash kmail

2015-09-28 Thread Bongani Hlope
https://bugs.kde.org/show_bug.cgi?id=353288

Bug ID: 353288
   Summary: pgp signed emails crash kmail
   Product: kmail2
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bhl...@mweb.co.za

Application: kmail (4.81 beta1)

Qt Version: 5.5.0
Operating System: Linux 4.1.8-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:

Selecting a PGP signed email on the kde mailing list on Mageia release 6
(Cauldron)

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f07c78d0840 (LWP 6669))]

Thread 9 (Thread 0x7f07c35e3700 (LWP 6670)):
#0  0x7f07e4c27fed in poll () at /lib64/libc.so.6
#1  0x7f07d9142ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f07d9144697 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f07c55a2c69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f07e552714f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#6  0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f07c156e700 (LWP 6681)):
#0  0x7f07e5748906 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#1  0x7f07e5749bce in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#2  0x7f07db28c80d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#3  0x7f07db28d113 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f07db28d2ec in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f07e574a7ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f07e56f467a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f07e55222ec in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f07e552714f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#10 0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f07c0cd2700 (LWP 6682)):
#0  0x7f07dbaafc3f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f07d72d7e00 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5WebKit.so.5
#2  0x7f07d72d7e29 in  () at /lib64/libQt5WebKit.so.5
#3  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#4  0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f07b90e7700 (LWP 6683)):
#0  0x7f07dbaafc3f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f07bb9eb97a in radeon_drm_cs_emit_ioctl () at
/usr/lib64/dri/r600_dri.so
#2  0x7f07bb9eb1a7 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so
#3  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#4  0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f0773ffd700 (LWP 6690)):
#0  0x7f07dbaafc3f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f07d6fdac5d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7f07d7307f01 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#4  0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f07737fc700 (LWP 6691)):
#0  0x7f07dbaafc3f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f07d6fdbc73 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7f07d7307f01 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#4  0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f0772ffb700 (LWP 6692)):
#0  0x7f07dbaafc3f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f07d6fdbc73 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7f07d7307f01 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#4  0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f07727fa700 (LWP 6693)):
#0  0x7f07dbaafc3f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f07d6fdbc73 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7f07d7307f01 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7f07dbaaa65d in start_thread () at /lib64/libpthread.so.0
#4  0x7f07e4c33e5d in clone () at /lib64/libc.so.6

Thread 1 

[kmail2] [Bug 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."

2015-09-28 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=246027

David Faure  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 277007] KMail2 full search of emails does not work

2015-09-28 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=277007

Robert Scott  changed:

   What|Removed |Added

 CC||b...@humanleg.org.uk

--- Comment #38 from Robert Scott  ---
I'm having the same problem with 4.14.1 under debian jessie. Immediately
returning no search results no matter what I type.

Part of me wants to say this is the last straw with kmail2, but I've said it
before too much already. I think the only reason I've been staying with it is
because of the convenience of kde's kioslaves. It makes me sad because kmail1
was one of my *favourite* applications.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 351850] Random crash when having a gmail account setup in kmail

2015-09-28 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=351850

Allen Winter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kdep
   ||imlibs/e99682c321aafa0918cf
   ||929cba888036dd9ecfd5
 Resolution|--- |FIXED

--- Comment #3 from Allen Winter  ---
Git commit e99682c321aafa0918cf929cba888036dd9ecfd5 by Allen Winter.
Committed on 28/09/2015 at 14:31.
Pushed by winterz into branch 'KDE/4.14'.

Check response content size before accessing it in search job
MERGE: not needed. this is a back port

M  +2-2kimap/searchjob.cpp

http://commits.kde.org/kdepimlibs/e99682c321aafa0918cf929cba888036dd9ecfd5

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 348817] New Mail notify message appears when no messages retrieved

2015-09-28 Thread Ian
https://bugs.kde.org/show_bug.cgi?id=348817

--- Comment #3 from Ian  ---
Does not happen when i'm using kontact, only when kmail is stand-alone.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs