[Akonadi] [Bug 361322] Crash during cold boot

2016-04-02 Thread Christoph Feck via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361322

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |kdepim-bugs@kde.org
Product|kde |Akonadi
  Component|general |general

-- 
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 345992] Keyboard shortcut assigned to "archive mail" works once, unconfigures itself

2016-04-02 Thread Rewarp via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345992

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #4 from Rewarp  ---
Since this is a keyboard shortcut issue, I am adding my own custom shortcut
problem here as well.
 I have assigned the "Right" and "Left" key to Next and Previous message
respectively.

For some odd reason, The shortcut for "Focus on Next Message" is not the
default Alt+Right, but is Right. This conflicts with my custom key for "Next
Message".

After changing "Focus on Next Message" to the default Alt+Right, the Right key
works once to move to the next message, but on the second tap is suddenly
reassigned to "Focus on Next Message again"

Steps to reproduce:

1. Reassign shortcut for "Focus on Next Message" to default Alt+Right
2. Assign shortcut for "Next Message" to Right.
3. Press Right.

Expected:

The next email message should be selected.

Instead:

1. The next message is selected.
2. The custom shortcut fails and is reassigned to "Focus on Next Message".

-- 
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 351628] Akonadi DAV Resource does not sync all calendars on ownCloud any more

2016-04-02 Thread somnium via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351628

--- Comment #20 from somnium  ---
It seems that the problem has something to do with the new owncloud version
9.0.

The urls changed from: https://ADDRESS/remote.php/caldav/ and
https://ADDRESS/remote.php/carddav/ to https://ADDRESS/remote.php/dav/ (caldav
and carddav). I changed this manually in akonadiconsole and the calendars and
contacts appeared again.

I think, this is an easy fix in kontact/kdepim.

Cheers.

-- 
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 316153] can't move or delete messages in imap inbox

2016-04-02 Thread Richard via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=316153

Richard  changed:

   What|Removed |Added

 CC|richard.taub...@gmx.de  |

-- 
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


[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

2016-04-02 Thread naughtypine
https://bugs.kde.org/show_bug.cgi?id=350731

naughtyp...@openmailbox.org  changed:

   What|Removed |Added

 CC||naughtyp...@openmailbox.org

-- 
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 361319] New: akonadi_googlecalendar_resource crashed when it runs on background

2016-04-02 Thread Lukáš Karas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361319

Bug ID: 361319
   Summary: akonadi_googlecalendar_resource crashed when it runs
on background
   Product: Akonadi
   Version: GIT (master)
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@kde.org
  Reporter: lukas.ka...@centrum.cz
CC: kdepim-bugs@kde.org

I re-compile Akonadi from source some hours before this crash. My current head
is: bf2fddd8ecb9a8e3ec8d50d8371b651e1c1e3406

I found many bugs related with this assert in "createItemSyncInstanceIfMissing"
but it seems that none is related with this code path. Sorry if this report is
duplicate.

Application: akonadi_googlecalendar_resource (akonadi_googlecalendar_resource),
signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f70c61d8940 (LWP 3099))]

Thread 5 (Thread 0x7f70c40c8700 (LWP 3127)):
#0  0x7f70dcfaf5ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f70d4d0ec62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f70d4d108d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f70c5def4a9 in QXcbEventReader::run (this=0x920010) at
qxcbconnection.cpp:1253
#4  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x920010) at
thread/qthread_unix.cpp:331
#5  0x7f70d46e36fa in start_thread (arg=0x7f70c40c8700) at
pthread_create.c:333
#6  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f70c2b35700 (LWP 3160)):
#0  socketNotifierSourceCheck (source=0x7f70b4002e00) at
kernel/qeventdispatcher_glib.cpp:74
#1  0x7f70d41c1d61 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f70d41c22d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f70d41c243c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f70ddaf2a6b in QEventDispatcherGlib::processEvents
(this=0x7f70b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f70dda99d7a in QEventLoop::exec (this=this@entry=0x7f70c2b34c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f70dd8b6854 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x9a2790) at
thread/qthread_unix.cpp:331
#8  0x7f70d46e36fa in start_thread (arg=0x7f70c2b35700) at
pthread_create.c:333
#9  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f70c2334700 (LWP 3170)):
#0  0x7f70d4206a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f70d41c224e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f70d41c243c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f70ddaf2a6b in QEventDispatcherGlib::processEvents
(this=0x7f70b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f70dda99d7a in QEventLoop::exec (this=this@entry=0x7f70c2333c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f70dd8b6854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x99cbc0) at
thread/qthread_unix.cpp:331
#7  0x7f70d46e36fa in start_thread (arg=0x7f70c2334700) at
pthread_create.c:333
#8  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f70c1b33700 (LWP 3237)):
#0  0x7f70d41c1c7f in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f70d41c22d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f70d41c243c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f70ddaf2a6b in QEventDispatcherGlib::processEvents
(this=0x7f70ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f70dda99d7a in QEventLoop::exec (this=this@entry=0x7f70c1b32c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f70dd8b6854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x9a87d0) at
thread/qthread_unix.cpp:331
#7  0x7f70d46e36fa in start_thread (arg=0x7f70c1b33700) at
pthread_create.c:333
#8  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f70c61d8940 (LWP 3099)):
[KCrash Handler]
#6  0x7f70dcee9518 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f70dceeb0ea in __GI_abort () at abort.c:89
#8  0x7f70dd8a8fb1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=this@entry=0x7ffee00e0bd0,
msg=msg@entry=0x7f70ddb66028 "ASSERT failure in %s: \"%s\", file %s, line %d")
at glob

[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir

2016-04-02 Thread Lukáš Karas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353957

--- Comment #16 from Lukáš Karas  ---
Yes, it seems to be fixed already. You can close it. If it shows up again,
someone can reopen it...

-- 
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