[korganizer] [Bug 395675] Timezone Does not sync correctly via caldav

2018-08-10 Thread Donovan Hoare
https://bugs.kde.org/show_bug.cgi?id=395675

--- Comment #3 from Donovan Hoare  ---
Thanks, so can you lead me to where i can download the source and do a fix. I'm
a SELF-taught C++ Coder, so I have no idea, but maybe i can fix this and send
the patch.

But i have never did a fix and push, can you send me a how to to that. maybe
ill become a maintainer.

Please help

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

[kmail2] [Bug 397169] kmail does not sort mails after moving them to another directory

2018-08-10 Thread Francesco Turco
https://bugs.kde.org/show_bug.cgi?id=397169

Francesco Turco  changed:

   What|Removed |Added

 CC||ftu...@fastmail.fm

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

[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.

2018-08-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388068

wengah...@bn-paf.de changed:

   What|Removed |Added

 CC||wengah...@bn-paf.de

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

[kmail2] [Bug 397349] New: PgUp/PgDown doesn't work in message preview

2018-08-10 Thread Karsten Künne
https://bugs.kde.org/show_bug.cgi?id=397349

Bug ID: 397349
   Summary: PgUp/PgDown doesn't work in message preview
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: kue...@rentec.com
  Target Milestone: ---

In kmail-17.12.3 (Opensuse Leap 15.0) the PgUp/PgDown keys are broken in the
message preview. They only scroll the message one page and no more. If I scroll
down further with the arrow key or mouse and then hit PgDown it actually goes
UP to more or less one page down from the top. This is new in this version,
version 17.04.2 (Opensuse 42.3) was working correctly.

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

[kmail2] [Bug 383279] Kmail unnecessarily prompts for passwords

2018-08-10 Thread Karsten Künne
https://bugs.kde.org/show_bug.cgi?id=383279

--- Comment #5 from Karsten Künne  ---
It got better in kmail-17.12.3 (Leap 15.0) but it still occasionally prompts
for password despite GSSAPI authentication. I think I got the prompt on startup
and sometimes if I click "Check Mail" or so.

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

[kleopatra] [Bug 397341] New: PGP keys: Changing expiration date doesn't change expiration date of all subkeys

2018-08-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=397341

Bug ID: 397341
   Summary: PGP keys: Changing expiration date doesn't change
expiration date of all subkeys
   Product: kleopatra
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: spiolli...@googlemail.com
CC: kdepim-bugs@kde.org, m...@kde.org
  Target Milestone: ---

When changing the expiration date of a PGP key only the subkeys for certifying
and signing are changed, while the subkey for encryption remains unchanged.

How to reproduce:
1. Change the expiration date of a key (either using right-click -> "Change
Expiry Date" or right-click -> "Details" -> pen symbol next to "Expires")
2. look at expiration dates of subkeys (right-click -> "Details" -> "More
details")

Expected results: all subkeys have been set to expire at the new expiration
date

Actual result: Only the subkey with the usage "Certify, Sign" has been set to
the new expiration date, while the subkey with the usage "Encrypt" remains
unchanged

kleopatra version 18.04.3

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

[kontact] [Bug 397335] Kontact crashes randomly when closing

2018-08-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=397335

--- Comment #1 from wengah...@bn-paf.de ---
same behaviour when using kmail:

this are the errors i get when starting and closing kmail from the
command-line:

---
1 : "Uncaught ReferenceError: qt is not defined"
1 : "Uncaught ReferenceError: qt is not defined"
stringToMailbox: Invalid address
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
sonnet.plugins.hspell: HSpellDict::HSpellDict: Init failed
sonnet.core: Missing trigrams for languages: QSet("en_GB", "en_CA", "de_CH",
"en_AU", "de_AT")
*** KMail got signal 11 (Exiting)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmail path = /usr/bin pid = 23731
KCrash: Arguments: /usr/bin/kmail 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0

[1]+  Angehalten  kmail
---

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

[kontact] [Bug 397335] New: Kontact crashes randomly when closing

2018-08-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=397335

Bug ID: 397335
   Summary: Kontact crashes randomly when closing
   Product: kontact
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: wengah...@bn-paf.de
  Target Milestone: ---

Application: kontact (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.47.0
Operating System: Linux 4.15.0-30-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

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

Kontact crahses randomly when closing it with the close window close button.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6824c00080 (LWP 19288))]

Thread 6 (Thread 0x7f66921e8700 (LWP 21446)):
#0  0x7f6820e81ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f66921e77e0, expected=0, futex_word=0x7f67d40045f0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f6820e81ed9 in __pthread_cond_wait_common (abstime=0x7f66921e7880,
mutex=0x7f67d40045a0, cond=0x7f67d40045c8) at pthread_cond_wait.c:533
#2  0x7f6820e81ed9 in __pthread_cond_timedwait (cond=0x7f67d40045c8,
mutex=0x7f67d40045a0, abstime=0x7f66921e7880) at pthread_cond_wait.c:667
#3  0x7f681215f652 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f6812135799 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f6812135cfb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f681212e5eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f6820e7b6db in start_thread (arg=0x7f66921e8700) at
pthread_create.c:463
#8  0x7f68213b888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f66d9f5a700 (LWP 19327)):
#0  0x7f6820e819f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5603c659d8e0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f6820e819f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5603c659d890, cond=0x5603c659d8b8) at pthread_cond_wait.c:502
#2  0x7f6820e819f3 in __pthread_cond_wait (cond=0x5603c659d8b8,
mutex=0x5603c659d890) at pthread_cond_wait.c:655
#3  0x7f6821cdb59b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6821cd3c0b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f66daf4880c in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so
#6  0x7f6821cda16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6820e7b6db in start_thread (arg=0x7f66d9f5a700) at
pthread_create.c:463
#8  0x7f68213b888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f67a4ff9700 (LWP 19319)):
#0  0x7f6820e819f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f680bf4dfb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f6820e819f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f680bf4df68, cond=0x7f680bf4df90) at pthread_cond_wait.c:502
#2  0x7f6820e819f3 in __pthread_cond_wait (cond=0x7f680bf4df90,
mutex=0x7f680bf4df68) at pthread_cond_wait.c:655
#3  0x7f680bc575f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f680bc57639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f6820e7b6db in start_thread (arg=0x7f67a4ff9700) at
pthread_create.c:463
#6  0x7f68213b888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f67de7fc700 (LWP 19300)):
#0  0x7f6820e819f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f67de7fb738) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f6820e819f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f67de7fb6e8, cond=0x7f67de7fb710) at pthread_cond_wait.c:502
#2  0x7f6820e819f3 in __pthread_cond_wait (cond=0x7f67de7fb710,
mutex=0x7f67de7fb6e8) at pthread_cond_wait.c:655
#3  0x7f6812126999 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f68121269c7 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f68121014db in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f68120fdda8 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f681211a77b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f68121324d6 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f681212e5eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f6820e7b6db in start_thread (arg=0x7f67de7fc700) at
pthread_create.c:463
#11 

[Akonadi] [Bug 397330] akonactl fsck crashes

2018-08-10 Thread Richard Bos
https://bugs.kde.org/show_bug.cgi?id=397330

--- Comment #1 from Richard Bos  ---
In thread 6 I see:

#9  0x7f100f57706f in qt_message_print (message=..., context=...,
msgType=QtFatalMsg) at global/qlogging.cpp:1656
#10 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=...,
msg=msg@entry=0x7f100f8401f0 "ASSERT: \"%s\" in file %s, line %d",
ap=ap@entry=0x7f0fff7fd298) at global/qlogging.cpp:281
#11 0x7f100f578869 in QMessageLogger::fatal
(this=this@entry=0x7f0fff7fd370, msg=msg@entry=0x7f100f8401f0 "ASSERT: \"%s\"
in file %s, line %d") at global/qlogging.cpp:793

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

[Akonadi] [Bug 396980] akonadi_imap_resource segfaults [due to ImapQuotaAttribute in libakonadi-singlefileresource.so]

2018-08-10 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=396980

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||pim-runtime/c9254f3497e0cd3
   ||7039333c17085b064e3b323a2

--- Comment #6 from Daniel Vrátil  ---
Git commit c9254f3497e0cd37039333c17085b064e3b323a2 by Daniel Vrátil, on behalf
of Grzegorz Kowal.
Committed on 10/08/2018 at 09:20.
Pushed by dvratil into branch 'Applications/18.08'.

Fix array access bounds in IMAP resource

Summary:
ImapQuotaAttribute::serialized() processes IMAP roots assigning corresponding
QUOTA and USAGE attributes to each root. It uses three dictionaries: mRoots,
mLimits, and mUsages assuming that these dictionaries always have the same
number of  elements. In a case when mRoots contains more elements than other
two dictionaries, this causes referencing to non-existent elements in mLimits
and mUsages and segfaults.

Fix this by using mLimits.size() and mUsages.size() in corresponding loops.

Reviewers: #kde_pim, dvratil

Reviewed By: #kde_pim, dvratil

Subscribers: mlaurent, cfeck, kde-pim

Tags: #kde_pim

Differential Revision: https://phabricator.kde.org/D14554

M  +2-2resources/shared/singlefileresource/imapquotaattribute.cpp

https://commits.kde.org/kdepim-runtime/c9254f3497e0cd37039333c17085b064e3b323a2

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

[Akonadi] [Bug 392947] Configuration crash after parallel installation of openLeap42.2 to older version

2018-08-10 Thread Richard Bos
https://bugs.kde.org/show_bug.cgi?id=392947

Richard Bos  changed:

   What|Removed |Added

 CC||richard@xs4all.nl
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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

[Akonadi] [Bug 397330] New: akonactl fsck crashes

2018-08-10 Thread Richard Bos
https://bugs.kde.org/show_bug.cgi?id=397330

Bug ID: 397330
   Summary: akonactl fsck crashes
   Product: Akonadi
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: richard@xs4all.nl
  Target Milestone: ---

Application: akonadiserver (5.7.3)

Qt Version: 5.9.4
Frameworks Version: 5.45.0
Operating System: Linux 4.12.14-lp150.12.10-default x86_64
Distribution (Platform): openSUSE RPMs

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

Executed the command:
# akonadictl --verbose fsck

I recently migrated from an older openSUSE version to openSUSE Leap 15.
After the migration, the above command finished successfully.
Now with kmail and akonadi sometime in use (1,5 weeks) the command does not
finish succesfully.

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1010fa98c0 (LWP 4904))]

Thread 48 (Thread 0x7f0f68ff1700 (LWP 11476)):
#0  0x7f100b7b96a9 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f100b7ba03b in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f100b7ba21c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f100f7b0c0b in QEventDispatcherGlib::processEvents
(this=0x7f0fa000f5b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f68ff0d10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f100f5884da in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f100f58d0ce in QThreadPrivate::start (arg=0x7f0f8406f200) at
thread/qthread_unix.cpp:368
#7  0x7f100da70559 in start_thread () from /lib64/libpthread.so.0
#8  0x7f100ec7582f in clone () from /lib64/libc.so.6

Thread 47 (Thread 0x7f0f69ff3700 (LWP 11151)):
#0  0x7f100b7ff759 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f100b7b9b34 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f100b7ba0b0 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f100b7ba21c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f100f7b0c0b in QEventDispatcherGlib::processEvents
(this=0x7f0f8c029bf0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f69ff2d10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f100f5884da in QThread::exec (this=) at
thread/qthread.cpp:515
#7  0x7f100f58d0ce in QThreadPrivate::start (arg=0x5620b7ac24d0) at
thread/qthread_unix.cpp:368
#8  0x7f100da70559 in start_thread () from /lib64/libpthread.so.0
#9  0x7f100ec7582f in clone () from /lib64/libc.so.6

Thread 46 (Thread 0x7f0f6a7f4700 (LWP 11149)):
#0  0x7f100ec6b08b in poll () from /lib64/libc.so.6
#1  0x7f100b7ba109 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f100b7ba21c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f100f7b0c0b in QEventDispatcherGlib::processEvents
(this=0x7f0f80029b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f6a7f3d10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f100f5884da in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f100f58d0ce in QThreadPrivate::start (arg=0x7f0f84015f20) at
thread/qthread_unix.cpp:368
#7  0x7f100da70559 in start_thread () from /lib64/libpthread.so.0
#8  0x7f100ec7582f in clone () from /lib64/libc.so.6

Thread 45 (Thread 0x7f0f6700 (LWP 11147)):
#0  0x7f100b7ff339 in g_private_get () from /usr/lib64/libglib-2.0.so.0
#1  0x7f100b7e1ce0 in g_thread_self () from /usr/lib64/libglib-2.0.so.0
#2  0x7f100b7ba20d in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f100f7b0c0b in QEventDispatcherGlib::processEvents
(this=0x7f0f84056ae0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f6fffed10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f100f5884da in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f100f58d0ce in QThreadPrivate::start (arg=0x7f0f90020ab0) at
thread/qthread_unix.cpp:368
#7  0x7f100da70559 in start_thread () from /lib64/libpthread.so.0
#8  0x7f100ec7582f in clone () from /lib64/libc.so.6

Thread 44 (Thread 0x7f0f6aff5700 (LWP 6292)):
#0  0x7f100b7ff774 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f100b7b9aa8 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f100b7ba0b0 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  

[kmail2] [Bug 279115] Standard Mailing list doesn't thread properly

2018-08-10 Thread Jan
https://bugs.kde.org/show_bug.cgi?id=279115

Jan  changed:

   What|Removed |Added

 CC||medhe...@web.de

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