[Akonadi] [Bug 397634] Is it possible to define a port for akonadi mariadb database ?

2018-09-12 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=397634

--- Comment #2 from Christoph Feck  ---
Nick, did comment #1 help to resolve your issues?

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

[akregator] [Bug 398559] New: Akregator is crashing

2018-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=398559

Bug ID: 398559
   Summary: Akregator is crashing
   Product: akregator
   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: f.bren...@gmx.net
  Target Milestone: ---

Application: akregator (5.7.3)

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

-- Information about the crash:
every time i want to start akregator, it is crashing

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd7a1bb7b80 (LWP 9910))]

Thread 32 (Thread 0x7fd6c672e700 (LWP 9952)):
#0  0x7fd797c5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5616fa8a25f0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fd797c5d9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5616fa8a25a0, cond=0x5616fa8a25c8) at pthread_cond_wait.c:502
#2  0x7fd797c5d9f3 in __pthread_cond_wait (cond=0x5616fa8a25c8,
mutex=0x5616fa8a25a0) at pthread_cond_wait.c:655
#3  0x7fd768ba846b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7fd768ba8197 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7fd797c576db in start_thread (arg=0x7fd6c672e700) at
pthread_create.c:463
#6  0x7fd79d9c988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 31 (Thread 0x7fd6c6f2f700 (LWP 9951)):
#0  0x7fd797c5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5616fa7c4200) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fd797c5d9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5616fa7c41b0, cond=0x5616fa7c41d8) at pthread_cond_wait.c:502
#2  0x7fd797c5d9f3 in __pthread_cond_wait (cond=0x5616fa7c41d8,
mutex=0x5616fa7c41b0) at pthread_cond_wait.c:655
#3  0x7fd768ba846b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7fd768ba8197 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7fd797c576db in start_thread (arg=0x7fd6c6f2f700) at
pthread_create.c:463
#6  0x7fd79d9c988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30 (Thread 0x7fd6cc927700 (LWP 9949)):
#0  0x7fd797c5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fd78abc0fb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fd797c5d9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fd78abc0f68, cond=0x7fd78abc0f90) at pthread_cond_wait.c:502
#2  0x7fd797c5d9f3 in __pthread_cond_wait (cond=0x7fd78abc0f90,
mutex=0x7fd78abc0f68) at pthread_cond_wait.c:655
#3  0x7fd78a8ca5f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7fd78a8ca639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7fd797c576db in start_thread (arg=0x7fd6cc927700) at
pthread_create.c:463
#6  0x7fd79d9c988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7fd6cd3ff700 (LWP 9944)):
#0  0x7fd797c5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5616fa3d1ad8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fd797c5d9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5616fa3d1a88, cond=0x5616fa3d1ab0) at pthread_cond_wait.c:502
#2  0x7fd797c5d9f3 in __pthread_cond_wait (cond=0x5616fa3d1ab0,
mutex=0x5616fa3d1a88) at pthread_cond_wait.c:655
#3  0x7fd78e1c7c95 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fd78e1c8177 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fd78e1c8f11 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fd78e1c55eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fd797c576db in start_thread (arg=0x7fd6cd3ff700) at
pthread_create.c:463
#8  0x7fd79d9c988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7fd6ce35f700 (LWP 9943)):
#0  0x7fd797c5d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5616fa659450) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fd797c5d9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5616fa659400, cond=0x5616fa659428) at pthread_cond_wait.c:502
#2  0x7fd797c5d9f3 in __pthread_cond_wait (cond=0x5616fa659428,
mutex=0x5616fa659400) at pthread_cond_wait.c:655
#3  0x7fd79e0dd59b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd79e0d5c0b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd6cf35a80c in  () at

[kmail2] [Bug 398399] using + to move to next unread message keeps the current message also selected

2018-09-12 Thread Christian Kalkhoff
https://bugs.kde.org/show_bug.cgi?id=398399

Christian Kalkhoff  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #3 from Christian Kalkhoff  ---
I did some tests but wasn't able to reproduce in kontact/kmail 5.9.1 on
Archlinux. Not sure when 5.9.1 will be released to you by OpenSUSE but chances
are, that the bug got fixed in the meantime.

So if nobody else is able to reproduce, I would suggest you to wait for 5.9.1
and see if the problem persists. I will have my focus on the described
behaviour in my daily usage of kontact, but I cannot remember that something
alike happend to me in the past.

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

[kontact] [Bug 398558] New: Crash when changing between mail folders

2018-09-12 Thread Oliver
https://bugs.kde.org/show_bug.cgi?id=398558

Bug ID: 398558
   Summary: Crash when changing between mail folders
   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: der_b...@gmx.de
  Target Milestone: ---

Application: kontact (5.7.3)

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

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

I have an IMAP post box configured in Kontact. When I switch between Inbox,
Sent etc. Kontact randomly crashes. Sometimes it does, sometimes not.

I use Kontact Version 5.7.3 in Kubuntu 18.04.

-- 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 0x7f0cc78bc600 (LWP 15027))]

Thread 30 (Thread 0x7f0b63fff700 (LWP 15141)):
#0  0x7f0cc425abf9 in __GI___poll (fds=0x7f0b58001cb0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f0cbdf66439 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0cbdf6654c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0cc4dc090b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0cc4d659ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0cc4b8422a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0cc4b8916d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0cbffe66db in start_thread (arg=0x7f0b63fff700) at
pthread_create.c:463
#8  0x7f0cc426788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7f0b6d918700 (LWP 15091)):
#0  0x7f0cbdf66527 in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f0cc4dc090b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0cc4d659ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0cc4b8422a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0cc4b8916d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0cbffe66db in start_thread (arg=0x7f0b6d918700) at
pthread_create.c:463
#6  0x7f0cc426788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7f0b6e119700 (LWP 15090)):
#0  0x7f0cbffec9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x56304523e7ec) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f0cbffec9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x56304523e798, cond=0x56304523e7c0) at pthread_cond_wait.c:502
#2  0x7f0cbffec9f3 in __pthread_cond_wait (cond=0x56304523e7c0,
mutex=0x56304523e798) at pthread_cond_wait.c:655
#3  0x7f0cb4fdfc95 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f0cb4fe0177 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f0cb4fe0f11 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f0cb4fdd5eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f0cbffe66db in start_thread (arg=0x7f0b6e119700) at
pthread_create.c:463
#8  0x7f0cc426788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f0b7944d700 (LWP 15071)):
#0  0x7f0cbffec9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5630456c4100) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f0cbffec9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5630456c40b0, cond=0x5630456c40d8) at pthread_cond_wait.c:502
#2  0x7f0cbffec9f3 in __pthread_cond_wait (cond=0x5630456c40d8,
mutex=0x5630456c40b0) at pthread_cond_wait.c:655
#3  0x7f0cc4b8a59b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0cc4b82c0b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0b7a43b80c in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so
#6  0x7f0cc4b8916d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0cbffe66db in start_thread (arg=0x7f0b7944d700) at
pthread_create.c:463
#8  0x7f0cc426788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f0b7b143700 (LWP 15069)):
#0  0x7f0cbffee035 in __GI___pthread_getspecific (key=7) at
pthread_getspecific.c:31
#1  0x7f0cbdf8e2f0 in g_thread_self () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0cbdf6653d in g_main_context_iteration () at

[kontact] [Bug 398557] New: Kontact crashes when starting

2018-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=398557

Bug ID: 398557
   Summary: Kontact crashes when starting
   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: f.bren...@gmx.net
  Target Milestone: ---

Application: kontact (5.7.3)

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

-- Information about the crash:
every time i'm starting Kontact it just crashes without any error or something

The crash can be reproduced every time.

-- 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 0x7f640ef8bb80 (LWP 8960))]

Thread 34 (Thread 0x7f629f00f700 (LWP 9011)):
#0  0x7f64076259f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55fef532) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f64076259f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55fef531ffb0, cond=0x55fef531ffd8) at pthread_cond_wait.c:502
#2  0x7f64076259f3 in __pthread_cond_wait (cond=0x55fef531ffd8,
mutex=0x55fef531ffb0) at pthread_cond_wait.c:655
#3  0x7f640c23559b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f640c22dc0b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f62a40f280c in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so
#6  0x7f640c23416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f640761f6db in start_thread (arg=0x7f629f00f700) at
pthread_create.c:463
#8  0x7f640b90988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 33 (Thread 0x7f62a4dcf700 (LWP 9009)):
#0  0x7f64055b9cf4 in g_mutex_unlock () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6405573988 in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f640557436b in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f640557454c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f640c46b90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f640c4109ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f640c22f22a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f640c23416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f640761f6db in start_thread (arg=0x7f62a4dcf700) at
pthread_create.c:463
#9  0x7f640b90988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 32 (Thread 0x7f62b5686700 (LWP 9001)):
#0  0x7f640b8fcbf9 in __GI___poll (fds=0x7f62ac027070, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f6405574439 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f640557454c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f640c46b90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f640c4109ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f640c22f22a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f640c23416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f640761f6db in start_thread (arg=0x7f62b5686700) at
pthread_create.c:463
#8  0x7f640b90988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 31 (Thread 0x7f62b5e87700 (LWP 9000)):
#0  0x7f64055b9cd9 in g_mutex_lock () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f64055739a3 in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f640557436b in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f640557454c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f640c46b90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f640c4109ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f640c22f22a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f640c23416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f640761f6db in start_thread (arg=0x7f62b5e87700) at
pthread_create.c:463
#9  0x7f640b90988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30 (Thread 0x7f62b6d37700 (LWP 8999)):
#0  0x7f640b8fcbf9 in __GI___poll (fds=0x7f62b0004a10, nfds=1,
timeout=10334) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  

[kmail2] [Bug 394505] Many "unnamed" identities are created without intervention

2018-09-12 Thread Adam Bark
https://bugs.kde.org/show_bug.cgi?id=394505

Adam Bark  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[kleopatra] [Bug 398556] New: changing key expiration reports success after 3 failed passphrase attempts

2018-09-12 Thread Ted Parvu
https://bugs.kde.org/show_bug.cgi?id=398556

Bug ID: 398556
   Summary: changing key expiration reports success after 3 failed
passphrase attempts
   Product: kleopatra
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: t...@tedstechshack.com
CC: kdepim-bugs@kde.org, m...@kde.org
  Target Milestone: ---

Version 3.1.2

Key has expired. I edit the key to change the expiration. But I seem to have
forgotten my passphrase.

An empty passphrase reports success. Expiration unchanged.


3 invalid passphrases, after the 3rd Kleo reports;

"Expiry date changed successfully."

Expiration unchanged.

I would expect to see something reporting that I got the passphrase incorrect
not that the expiration was changed.

cheers,

--Ted

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

[kmail2] [Bug 387931] KMail 5.7.0 is missing the show message structure option

2018-09-12 Thread Mateusz Kowalewski
https://bugs.kde.org/show_bug.cgi?id=387931

Mateusz Kowalewski  changed:

   What|Removed |Added

 CC||mateusz.f.kowalewski@gmail.
   ||com

--- Comment #25 from Mateusz Kowalewski  ---
(In reply to Laurent Montel from comment #9)
> (In reply to Kamil Dudka from comment #8)
> > Laurent, could you please stop removing or hiding kmail's features which you
> > think are not useful or important?
> > 
> > Those features were originally implemented for a reason and kmail's users
> > have been successfully using them for quite some time.  If you keep the
> > current pace of downgrading user experience with each subsequent release of
> > kmail, you are going loose existing users of kmail for no real benefit.
> > 
> > You should really focus on fixing existing bugs instead of removing existing
> > stable features that nobody complains about.
> 
> Just a question:
> Are you the kmail maintainer ?
> no I don't think.
> I am.
> 
> So if I think that it's better to reduce menu or hide not useful feature for
> enduser it's my choice.
> 
> You work on redhat so make your work as packager and stop to cry.
> 
> Thanks.

Dear maintainer,

There is another problem with your "choice" here: The documentation did not
reflect this change! That's an absolute no go!

I'm currently looking for some other bug in Kmail/Akonadi and reading the
mailing-list archives. I discovered this bug report by chance now.

Some time ago I (as an end-user) needed to look up the message structure of one
mail. I was very upset as I saw the menu entry I knew was there for years was
gone. I tired to "google" for this issue but did not find this bug report then.
I also did not find any information about a removal of this feature. The
documentation says it is still in the menu! I thought it is a very strange bug.
I even started to look for the relevant code in Kmail (but did not push this
endeavor any further than out of lack of time).

In the end I exported the raw mail an used some tools on it to extract the part
of the mail I was interested in. Looking into this issue and coming up with a
workaround was a waste of several hours!

"Hiding" or removing features "for power users" is a think I would expect form
the Gnome people. But never ever from a KDE app! Please don't do something like
that again!

There are some usability standards under KDE now for years: Everything you can
find in the GUI is also available as a toolbar. But not the other way around!

Till said: "'toolbar' \subseteq 'menu' is a typical pattern". I think it's not
only a "typical pattern" it's how things work all over KDE apps since most
likely pre V1.0 versions. (Maybe I don't recall correctly the version but it
works like that since "ever")! It's not anything you could make a "choice"
about.

You just wasted the time of several people by making a "choice" like that. But
there was no gain whatsoever in doing so! KDE isn't for people who like
"hidden" or striped down features.

Thank you for being now aware that with "choices" like that you will annoy a
lot of long time KDE users.


Best regards,
Mateusz

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

[kaddressbook] [Bug 397438] Not Able to Import Data

2018-09-12 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=397438

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Christophe Giboudeaux  ---
No feedback. Closing

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

[kmail2] [Bug 387251] Kmail stops retrieving emails after a while

2018-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=387251

tro...@free.fr changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from tro...@free.fr ---
This bug has stopped happening for a while now.

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

[Akonadi] [Bug 385817] Akonadi stops checking for new emails after some time.

2018-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=385817

tro...@free.fr changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from tro...@free.fr ---
This bug stopped happening for a while now.

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

[kmail2] [Bug 398530] New: Kmail crashes after clicking new maildir in maildir list panel

2018-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=398530

Bug ID: 398530
   Summary: Kmail crashes after clicking new maildir in maildir
list panel
   Product: kmail2
   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: mat...@ant.gliwice.pl
  Target Milestone: ---

Application: kmail (5.7.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
Started KMail.
Clicked "check new mail".
KMail starter processing, with unusuall hangs in displaying current mail lists.
After while crash.

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

Thread 35 (Thread 0x7fc0eaffd700 (LWP 4106)):
#0  0x7fc19c0d4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc0eaffc7e0, expected=0, futex_word=0x7fc10c004414) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fc0eaffc880, mutex=0x7fc10c0043c0,
cond=0x7fc10c0043e8) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7fc10c0043e8, mutex=0x7fc10c0043c0,
abstime=0x7fc0eaffc880) at pthread_cond_wait.c:667
#3  0x7fc190fa4652 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fc190f7a799 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fc190f7acfb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fc190f735eb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fc19c0ce6db in start_thread (arg=0x7fc0eaffd700) at
pthread_create.c:463
#8  0x7fc1a67de88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 34 (Thread 0x7fc03b9b8700 (LWP 2863)):
#0  0x7fc19c0d49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x562c1fd69f0c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x562c1fd69eb8,
cond=0x562c1fd69ee0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x562c1fd69ee0, mutex=0x562c1fd69eb8) at
pthread_cond_wait.c:655
#3  0x7fc190f75c95 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fc190f76177 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fc190f76f11 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fc190f735eb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fc19c0ce6db in start_thread (arg=0x7fc03b9b8700) at
pthread_create.c:463
#8  0x7fc1a67de88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 33 (Thread 0x7fc03c1b9700 (LWP 2862)):
#0  0x7fc19c0d49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x562c1fd69f0c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x562c1fd69eb8,
cond=0x562c1fd69ee0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x562c1fd69ee0, mutex=0x562c1fd69eb8) at
pthread_cond_wait.c:655
#3  0x7fc190f75c95 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fc190f76177 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fc190f76f11 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fc190f735eb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fc19c0ce6db in start_thread (arg=0x7fc03c1b9700) at
pthread_create.c:463
#8  0x7fc1a67de88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 32 (Thread 0x7fc0bd3ee700 (LWP 2861)):
#0  0x7fc19c0d49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fc18d83efb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7fc18d83ef68,
cond=0x7fc18d83ef90) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7fc18d83ef90, mutex=0x7fc18d83ef68) at
pthread_cond_wait.c:655
#3  0x7fc18d5485f4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7fc18d548639 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7fc19c0ce6db in start_thread (arg=0x7fc0bd3ee700) at
pthread_create.c:463
#6  0x7fc1a67de88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 31 (Thread 0x7fc0beca5700 (LWP 2832)):
#0  0x7fc1a67cd0b4 in __GI___libc_read (fd=77, buf=0x7fc0beca4810,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fc19a4bd980 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc19a478f27 in g_main_context_check () from

[akregator] [Bug 398516] UI - Akregator comments section font seems to be hard coded. Font is tiny on a 4k monitor

2018-09-12 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=398516

--- Comment #1 from Christophe Giboudeaux  ---
What is the "comment section" ? mind posting a screenshot ?

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

[kmail2] [Bug 385289] Kmail: Crash when moving or deleting imap folder (Wayland)

2018-09-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=385289

k...@palkeo.com changed:

   What|Removed |Added

 CC||k...@palkeo.com

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