date:20161123

[kmail2] [Bug 372866] New: KMail crashes on "normal" usage (scrolling/clicking on messages)

2016-11-23 Thread bugzilla_noreply

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

Bug ID: 372866
   Summary: KMail crashes on "normal" usage (scrolling/clicking on
messages)
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@jneureuther.de
  Target Milestone: ---

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.8-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

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

I scrolled around my messages and single-clicked onto one of them. Then KMail
crashes (sometimes instant, sometimes after a short period).
The behaviour is reproducible on any message. I did not do any configuration
changes. This bug appeared after the last KMail update on my system.

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 0x7f9f7054e940 (LWP 21414))]

Thread 43 (Thread 0x7f9dd57f8700 (LWP 21518)):
#0  0x7f9f85a76460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9f8863be23 in JSC::GCThread::waitForNextPhase() () at
/lib64/libQt5WebKit.so.5
#2  0x7f9f8863beb0 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#3  0x7f9f88942151 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#4  0x7f9f85a706ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f9f952f3f6f in clone () at /lib64/libc.so.6

Thread 42 (Thread 0x7f9dd5ff9700 (LWP 21517)):
#0  0x7f9f85a76460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9f8863be23 in JSC::GCThread::waitForNextPhase() () at
/lib64/libQt5WebKit.so.5
#2  0x7f9f8863beb0 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#3  0x7f9f88942151 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#4  0x7f9f85a706ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f9f952f3f6f in clone () at /lib64/libc.so.6

Thread 41 (Thread 0x7f9dd67fa700 (LWP 21516)):
#0  0x7f9f85a76460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9f8863be23 in JSC::GCThread::waitForNextPhase() () at
/lib64/libQt5WebKit.so.5
#2  0x7f9f8863beb0 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#3  0x7f9f88942151 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#4  0x7f9f85a706ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f9f952f3f6f in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7f9dd6ffb700 (LWP 21515)):
#0  0x7f9f85a76460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9f8863be23 in JSC::GCThread::waitForNextPhase() () at
/lib64/libQt5WebKit.so.5
#2  0x7f9f8863beb0 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#3  0x7f9f88942151 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#4  0x7f9f85a706ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f9f952f3f6f in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7f9dd77fc700 (LWP 21514)):
#0  0x7f9f85a76460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9f8863be23 in JSC::GCThread::waitForNextPhase() () at
/lib64/libQt5WebKit.so.5
#2  0x7f9f8863beb0 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#3  0x7f9f88942151 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#4  0x7f9f85a706ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f9f952f3f6f in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7f9dd7ffd700 (LWP 21513)):
#0  0x7f9f85a76460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9f8863be23 in JSC::GCThread::waitForNextPhase() () at
/lib64/libQt5WebKit.so.5
#2  0x7f9f8863beb0 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#3  0x7f9f88942151 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#4  0x7f9f85a706ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f9f952f3f6f in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7f9ea88a6700 (LWP 21512)):
#0  0x7f9f85a76460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9f8863afdc in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7f9f88942151 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7f9f85a706ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f9f952f3f6f in clone () at /lib64/libc.so.6

Thread 36 (Thread 0x7f9ea9738700 (LWP 21511)):
#0  0x7f9f85a76460 in

[kontact] [Bug 372856] New: Kontact crashes after being launched

2016-11-23 Thread Michał Walenciak

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

Bug ID: 372856
   Summary: Kontact crashes after being launched
   Product: kontact
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kice...@gmail.com
  Target Milestone: ---

Application: kontact (5.3.3 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.10-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

As soon as i open Kontact it crashes.

Console output:
$ kontact 
[1123/215524:ERROR:browser_main_loop.cc(217)] Running without the SUID sandbox!
See
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md
for more information on developing with the sandbox on.
 void AdblockManager::reloadConfig() false   
AdBlock::AdblockManager(0x1033df0)
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
org.kde.akonadi.ETM: GEN true false false
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: 
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
QSocketNotifier: Invalid socket 84 and type 'Read', disabling...
QSocketNotifier: Invalid socket 107 and type 'Read', disabling...
KCrash: Application 'kontact' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

The crash can be reproduced every time.

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

Thread 30 (Thread 0x7fa669459700 (LWP 18156)):
#0  0x7fa7a1e5a740 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fa7a1e5cc2b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fa7a1e5d6ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fa7a1e5d89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fa7a8b2972b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fa7a8ad323a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fa7a88f60f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fa7a88fad78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa7a3e11454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa7a7ff97df in clone () at /usr/lib/libc.so.6

Thread 29 (Thread 0x7fa669c5a700 (LWP 18145)):
#0  0x7fa7a1e5c7fe in g_main_context_release () at
/usr/lib/libglib-2.0.so.0
#1  0x7fa7a1e5d73a in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa7a1e5d89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa7a8b2972b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa7a8ad323a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa7a88f60f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa7a88fad78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fa7a3e11454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fa7a7ff97df in clone () at /usr/lib/libc.so.6

Thread 28 (Thread 0x7fa685177700 (LWP 18139)):
#0  0x7fa7a1ea2db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fa7a1e5cc95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fa7a1e5d6ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fa7a1e5d89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fa7a8b2972b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fa7a8ad323a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fa7a88f60f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fa7a88fad78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa7a3e11454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa7a7ff97df in clone () at /usr/lib/libc.so.6

Thread 27 (Thread 0x7fa685978700 (LWP 18137)):
#0  0x7fa7a1ea2dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fa7a1e5d114 in g_main_context_check () at

[kmail2] [Bug 372850] New: KMail crashes on startup

2016-11-23 Thread Peter Grobarcik

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

Bug ID: 372850
   Summary: KMail crashes on startup
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: coder.peter.grobar...@gmail.com
  Target Milestone: ---

Application: kmail (5.3.3 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.29.0
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
I just booted up after an update. The update crpled kdepim. None action taken
yet.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe1805cfa00 (LWP 6210))]

Thread 3 (Thread 0x7fe17575f700 (LWP 6213)):
#0  0x7fe1b0a6d81e in timerSourcePrepareHelper (timeout=0x7fe17575e9f4,
src=) at kernel/qeventdispatcher_glib.cpp:133
#1  timerSourcePrepare (source=, timeout=0x7fe17575e9f4) at
kernel/qeventdispatcher_glib.cpp:165
#2  0x7fe1a4eba92d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe1a4ebb2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe1a4ebb4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fe1b0a6e23b in QEventDispatcherGlib::processEvents
(this=0x7fe1680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fe1b0a18cea in QEventLoop::exec (this=this@entry=0x7fe17575ebc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#7  0x7fe1b083dfb4 in QThread::exec (this=) at
thread/qthread.cpp:507
#8  0x7fe1b0842b98 in QThreadPrivate::start (arg=0x29a2ad0) at
thread/qthread_unix.cpp:344
#9  0x7fe1a6a0070a in start_thread (arg=0x7fe17575f700) at
pthread_create.c:333
#10 0x7fe1aff3982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fe176970700 (LWP 6212)):
#0  0x7fe1aff2db5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe1a4ebb39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe1a4ebb4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe1b0a6e23b in QEventDispatcherGlib::processEvents
(this=0x7fe178c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fe1b0a18cea in QEventLoop::exec (this=this@entry=0x7fe17696fb90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7fe1b083dfb4 in QThread::exec (this=this@entry=0x7fe1b2b66d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7fe1b2af27a5 in QDBusConnectionManager::run (this=0x7fe1b2b66d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:196
#7  0x7fe1b0842b98 in QThreadPrivate::start (arg=0x7fe1b2b66d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
#8  0x7fe1a6a0070a in start_thread (arg=0x7fe176970700) at
pthread_create.c:333
#9  0x7fe1aff3982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fe1805cfa00 (LWP 6210)):
[KCrash Handler]
#6  0x7fe1afe68428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fe1afe6a02a in __GI_abort () at abort.c:89
#8  0x7fe1afeaa7ea in __libc_message (do_abort=2,
fmt=fmt@entry=0x7fe1affc32e0 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7fe1afeb481e in malloc_printerr (ar_ptr=0x7fe1b01f6b20 ,
ptr=0x29d7ce0, str=0x7fe1affc0142 "malloc(): memory corruption",
action=) at malloc.c:5004
#10 _int_malloc (av=av@entry=0x7fe1b01f6b20 ,
bytes=bytes@entry=1162) at malloc.c:3472
#11 0x7fe1afeb65d4 in __GI___libc_malloc (bytes=bytes@entry=1162) at
malloc.c:2911
#12 0x7fe1b0843e32 in QArrayData::allocate (objectSize=objectSize@entry=2,
alignment=alignment@entry=8, capacity=capacity@entry=569,
options=options@entry=...) at tools/qarraydata.cpp:114
#13 0x7fe1b08cdbe8 in QTypedArrayData::allocate
(options=..., capacity=569) at
../../include/QtCore/../../src/corelib/tools/qarraydata.h:222
#14 QString::fromLatin1_helper (str=str@entry=0x7fe1b0ae44e0 
"ZzzzArabCyrlDsrtGuruHansHantLatnMongTfngArmnBengCherDevaEthiGeorGrekGujrHebrJpanKhmrKndaKoreLaooMlymMymrOryaTamlTeluThaaThaiTibtSinhSyrcYiiiVaiiAvstBaliBamuBatkBopoBrahBugiBuhdCansCariCakmChamCoptCprt"...,
size=size@entry=568) at tools/qstring.cpp:4654
#15 0x7fe1b08a4bf1 in QString::fromLatin1 (str=,
size=568) at ../../include/QtCore/../../src/corelib/tools/qstring.h:538
#16 qt_splitLocaleName (name=..., lang=..., script=..., cntry=...) at
tools/qlocale.cpp:434
#17 0x7fe1b08eaab3 in QSystemLocale::query (this=,
type=, in=...) at

[kaddressbook] [Bug 340316] Custom field titles and field types not saved with vCard

2016-11-23 Thread Thomas Hejze

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

--- Comment #3 from Thomas Hejze  ---
(In reply to Denis Kurz from comment #2)
> This bug has only been reported for versions before 4.14, which have been
> unsupported for at least two years now. Can anyone tell if this bug still
> present?
> 
> If noone confirms this bug for a Framework-based version of kaddressbook
> (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets
> closed in about three months.

Confirmed for kdepim 4.14.10, the official version of OpenSuSE leap 42.1.

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

[kmail2] [Bug 372840] New: Shortcuts does not work well with kmail 5.3.90 beta1

2016-11-23 Thread luisfe

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

Bug ID: 372840
   Summary: Shortcuts does not work well with kmail 5.3.90 beta1
   Product: kmail2
   Version: 5.3.44 pre (QtWebEngine)
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: lui...@lftabera.es
  Target Milestone: ---

Configuration:

kmail 5.3.90 beta1
frameworks 5.28
Plasma/5.8
Applications/16.12 beta
Qt 5.7.0

Shortcuts do not work well, I have detected two errors:

I have mapped:
Select All Messages: Ctrl+A
Select All Text: Ctrl+Shift+A

However, in a folder both Ctrl+A and Ctrl+Shift+A do the same action, select
all the text of current message. This happen either if Kmail is run as
standalone or as a part of kontact.

Also in the shortcut configuration, there were two Delete options with the same
name, one mapped to Del and the other to Shift+Del. Shift+Del does nothing.

I remapped Shift+Del to "Delete Message" and the second "delete" option has
disappeared from the list of shortcuts. 

If I click a message, in the message list it appears with a light blue
background and black font. Del moves the message to trash and Shift+Del does
nothing.

If I ckick again on the same selected message, in the message list it appears
with a darker blue background and the font changes to white. In this case Del
moves the message to trash and Shift+Del deletes the message.

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

[Akonadi] [Bug 372835] New: Korganizer and Digital Clock/Calendar widget keep forgetting of selected Caldav resources

2016-11-23 Thread Martin Ottmar

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

Bug ID: 372835
   Summary: Korganizer and Digital Clock/Calendar widget keep
forgetting of selected Caldav resources
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: mirovsk...@gmail.com
  Target Milestone: ---

Our company CalDav calendar resource contains two calendars called "Personal
Callendar" and "Staff".
I'm not using the personal calendar, so I have it permanently disabled.
But, when I enable the "Staff" calendar, by checking a certain CheckBox in
Korganizer calendar viewer, or in the panel->Digital Clock Settings->PIM Events
Plugin, akonadi (usually) forgets this setting after next plasma session login.
Setting this resource as default in the korganizer doesn't have any effect.

This behaviour has been confirmed on (archlinux) machine of my colleague.
This behaviour (in korganizer) is there since KDE-3.5 or before.
This behaviour is new in KF5 for the new style Digital Clock/Calendar plasma
widget.

Best regards.

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

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

2016-11-23 Thread Rokas Kupstys

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

Bug ID: 372824
   Summary: PIM Events Plugin crashes plasmashell
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rok...@zoho.com
  Target Milestone: ---

Created attachment 102405
  --> https://bugs.kde.org/attachment.cgi?id=102405=edit
plasmashell crashlog

Akonadi version is 5.3.3 as reported by "akonadictl --version".

On every startup plasmashell crashes and restarts. System tray displays crash
notification. Crash log is attached.

PIM Events plugin is enabled so i can see events in calendar. I have added
nextcloud to akonadi to fetch calendar data from. Everything works as expected
- calendar events and contact birthdays are displayed in calendar widget.

Enabled PIM Events Plugin options:
enabled - Birthdays & Anniversaries
enabled - nextcloud callendar & contacts > default (callendar)
disabled - nextcloud callendar & contacts > Contact birthdays
enabled - Search > Declined Invitations
enabled - Search > Open Invitations

When PIM Events Plugin in calendar settings is disabled plasmashell no longer
crashes on startup. When PIM Events Plugin is enabled once again it crashes
plasmashell once, after plasmashell restarts everything works as expected.

P.S. I do realize crashlog is of limited use. I am sorry about that, but
archlinux package maintainers are hostile to debug information in packages
therefore i am simply unable to provide more useful crash log.

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

[Akonadi] [Bug 262396] xml dump does not work because of non existent timezone

2016-11-23 Thread bugzilla_noreply

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

jacob.bec...@uni-konstanz.de changed:

   What|Removed |Added

 CC||jacob.becker@uni-konstanz.d
   ||e

--- Comment #2 from jacob.bec...@uni-konstanz.de ---
I can confirm this isue is still present with OpenSUSU 42.2 
akonadiconsole 0.99
KDE Framework 5.26.0
akonadi 5.3.2

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

[kmail2] [Bug 372866] New: KMail crashes on "normal" usage (scrolling/clicking on messages)

[kontact] [Bug 372856] New: Kontact crashes after being launched

[kmail2] [Bug 372850] New: KMail crashes on startup

[kaddressbook] [Bug 340316] Custom field titles and field types not saved with vCard

[kmail2] [Bug 372840] New: Shortcuts does not work well with kmail 5.3.90 beta1

[Akonadi] [Bug 372835] New: Korganizer and Digital Clock/Calendar widget keep forgetting of selected Caldav resources

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

[Akonadi] [Bug 262396] xml dump does not work because of non existent timezone

8 matches

Site Navigation

Mail list logo

Footer information