[Akonadi] [Bug 355426] New: KF5 based KDEPIM/Akonadi 15.08.03 - tags are duplicated on each tag editing

[Till Schäfer via KDE Bugzilla]

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

Bug ID: 355426
   Summary: KF5 based KDEPIM/Akonadi 15.08.03 - tags are
duplicated on each tag editing
   Product: Akonadi
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: till2.schae...@uni-dortmund.de

After migration to Plasma 5 and Allplications 15.08 from KDE4 i see my tags in
kdepim multiple times, i.e. the same tag name is listed more than once.
Deleting the duplicate tags does not help, as the tags duplicate with each time
i add the tag a calendar entry or task. 

Reproducible: Always

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

[Zsiráf via KDE Bugzilla]

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

--- Comment #34 from Zsiráf  ---
(In reply to Yasin Zähringer from comment #33)
> start the akonadi console, select the browser tab and find the affected
> inbox. Right click on it and select folder properties. Now you find a tab
> called ACL and where probably all check boxes are deselected.
All boxes was selected (except link and unlink) but delete or move doesn't
work.

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

[kontact] [Bug 355439] New: kontact crashed after updating an event

[Dj YB via KDE Bugzilla]

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

Bug ID: 355439
   Summary: kontact crashed after updating an event
   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: yehi...@mail.ru

Application: kontact (4.14.9)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.5-201.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

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

I have updated an event time, pressing return to save the program has crashed

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

Thread 4 (Thread 0x7fa2d12ae700 (LWP 3204)):
#0  0x003cbc80c540 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x00396f38af61 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQtWebKit.so.4
#2  0x00396f6896d6 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQtWebKit.so.4
#3  0x003968eaa754 in  () at /lib64/libGL.so.1
#4  0x003cbc807555 in start_thread () at /lib64/libpthread.so.0
#5  0x003cbbd02b9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fa2c11a3700 (LWP 4330)):
#0  0x003cbbcf2fad in read () at /lib64/libc.so.6
#1  0x003968ea973c in  () at /lib64/libGL.so.1
#2  0x003966601bf7 in  () at /lib64/tls/libnvidia-tls.so.304.128
#3  0x003cbdc8db00 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#4  0x003cbdc498b4 in g_main_context_check () at /lib64/libglib-2.0.so.0
#5  0x003cbdc49d60 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#6  0x003cbdc49ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#7  0x003ccf3ba4ee in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#8  0x003ccf388791 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#9  0x003ccf388b05 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#10 0x003ccf278289 in QThread::exec() () at /lib64/libQtCore.so.4
#11 0x003ccf27aaac in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#12 0x003968eaa754 in  () at /lib64/libGL.so.1
#13 0x003cbc807555 in start_thread () at /lib64/libpthread.so.0
#14 0x003cbbd02b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fa2bbfff700 (LWP 6088)):
#0  0x003cbbcf72fd in poll () at /lib64/libc.so.6
#1  0x003cbdc49dbc in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x003cbdc49ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x003ccf3ba4ee in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x003ccf388791 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x003ccf388b05 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x003ccf278289 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x003ccf368863 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#8  0x003ccf27aaac in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x003968eaa754 in  () at /lib64/libGL.so.1
#10 0x003cbc807555 in start_thread () at /lib64/libpthread.so.0
#11 0x003cbbd02b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa31ba02900 (LWP 3178)):
[KCrash Handler]
#6  0x in  ()
#7  0x0033ee041000 in QApplication::x11ProcessEvent(_XEvent*) () at
/lib64/libQtGui.so.4
#8  0x0033ee06a489 in x11EventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQtGui.so.4
#9  0x003cbdc49a8a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#10 0x003cbdc49e20 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#11 0x003cbdc49ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#12 0x003ccf3ba4ce in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#13 0x0033ee06a626 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#14 0x003ccf388791 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#15 0x003ccf388b05 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#16 0x003ccf38e6a9 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#17 0x00403787 in main ()

Possible duplicates by query: bug 347371, bug 343159.

Reported using DrKonqi

-- 
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 355441] New: DAV Resource 15.08.3: Broken state, The item was not deleted on the server.

[Till Schäfer via KDE Bugzilla]

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

Bug ID: 355441
   Summary: DAV Resource 15.08.3: Broken state, The item was not
deleted on the server.
   Product: Akonadi
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: till2.schae...@uni-dortmund.de

Whenever I delete a task in KOrganizer 15.08.3 the DAV Resource is broken
afterwards: 

The status message is:
There was a problem with the request. The item has not been deleted from the
server.
The file or folder the.domain.of.my.server does not exist. (0).

When I restart the resource in akonadiconsole a message box pops up with the
message "Could not delete ."

Otherwise the synchronization works as expected. I can create new entries and
modify them.

Reproducible: Always

-- 
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 354417] crash on boot

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||i...@f2s.com

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

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

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

[Cor Blom via KDE Bugzilla]

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

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

-- 
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 355445] Baloo indexer crash after akonadi restart

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||chrig...@fastmail.fm,
   ||dvra...@kde.org,
   ||m...@vhanda.in
  Component|general |Baloo Indexer
   Assignee|unassigned-b...@kde.org |kdepim-bugs@kde.org
Product|kde |Akonadi

-- 
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 352664] Crash when pressing the "write new mail" button

[Fuchs via KDE Bugzilla]

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

--- Comment #11 from Fuchs  ---
Hi, fixed for me in 15.8.3 indeed, thank you very much. 

FIXED: Resolved for me, but maybe let's wait for the archers, too (I'd be
surprised though to see it still happen just based on distro, but given they
already seem to have had a fix ...)

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