[kmail2] [Bug 422651] Bad paragraph spacing

2020-06-08 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=422651

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.14.2
 CC||mon...@kde.org
 Status|REPORTED|RESOLVED

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

[kmail2] [Bug 422651] New: Bad paragraph spacing

2020-06-08 Thread David Rose
https://bugs.kde.org/show_bug.cgi?id=422651

Bug ID: 422651
   Summary: Bad paragraph spacing
   Product: kmail2
   Version: 5.14.1
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ppnmmw9zj...@absolutesix.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Create an email with an HTML signature
2. Type some text
2. Hit the Enter Key twice to create a new paragraph
3. Type more text

OBSERVED RESULT
When the email is sent or saved the double line breaks are converted to this:
SOME
TEXT
MORE
TEXT

The added "" creates huge whitespaces between each paragraph.

EXPECTED RESULT
A normal sized empty line between each paragraph.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Void Linux & Manjaro with KDE Plasma
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
This behavior is the same in both Void Linux and Manjaro.
Kmail 5.13.x does not have this issue.

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

[kontact] [Bug 422649] Kontact starting problem on Pinebook Pro with Manjaro ARM newest patchlevel

2020-06-08 Thread Uwe Herczeg
https://bugs.kde.org/show_bug.cgi?id=422649

Uwe Herczeg  changed:

   What|Removed |Added

Summary|Kotact starting problem on  |Kontact starting problem on
   |Pinebook Pro with Manjaro   |Pinebook Pro with Manjaro
   |ARM newest patchlevel   |ARM newest patchlevel

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

[kontact] [Bug 422649] New: Kotact starting problem on Pinebook Pro with Manjaro ARM newest patchlevel

2020-06-08 Thread Uwe Herczeg
https://bugs.kde.org/show_bug.cgi?id=422649

Bug ID: 422649
   Summary: Kotact starting problem on Pinebook Pro with Manjaro
ARM newest patchlevel
   Product: kontact
   Version: 5.14.1
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: uherc...@mail.ru
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. start kontact
2. 
3. 

OBSERVED RESULT

app starts but hangs/freezes and is unusable. The single apps like
kmail/korganizer could be started separately and are working flawlessly.

Journalctl says:

Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x88299820) )
Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver:
Subscriber "" disconnected
Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x881c3c90) )
Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x881c3c90) )
Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x88127bc0) )
Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x882d7b20) )
Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x88299b30) )
Jun 08 21:10:21 munin kernel: Purging 8388608 bytes
Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver:
Subscriber Akonadi::Server::NotificationSubscriber(0x88299820) identified
as "TagCacheMonitor - 187650858043648"
Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver:
Subscriber Akonadi::Server::NotificationSubscriber(0x881c3c90) identified
as "ETMCalendarMonitor - 187650858330464"
Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver:
Subscriber Akonadi::Server::NotificationSubscriber(0x88127bc0) identified
as "TagCacheMonitor - 187650858682448"
Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver:
Subscriber Akonadi::Server::NotificationSubscriber(0x882d7b20) identified
as "ItemMonitorMonitor - 187650859137952"
Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver:
Subscriber Akonadi::Server::NotificationSubscriber(0x88299b30) identified
as "TagCacheMonitor - 187650859766896"
Jun 08 21:10:22 munin kwin_x11[1164]: qt.qpa.xcb: QXcbConnection: XCB error: 3
(BadWindow), sequence: 21563, resource id: 37763433, major code: 3
(GetWindowAttributes), minor code: 0
Jun 08 21:10:22 munin kwin_x11[1164]: qt.qpa.xcb: QXcbConnection: XCB error: 3
(BadWindow), sequence: 21887, resource id: 165675019, major code: 18
(ChangeProperty), minor code: 0
Jun 08 21:10:23 munin kded5[1122]: Registering ":1.131/StatusNotifierItem" to
system tray
Jun 08 21:10:23 munin plasmashell[1166]: QQuickItem::stackAfter: Cannot stack
StatusNotifierItem_QMLTYPE_382(0xf415dd60, parent=0xf2c54820,
geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_382(0xf36caab0), which
must be a sibling
Jun 08 21:10:23 munin kwin_x11[1164]: qt.qpa.xcb: QXcbConnection: XCB error: 3
(BadWindow), sequence: 22069, resource id: 165675019, major code: 18
(ChangeProperty), minor code: 0

Any tips for me?





EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kmail2] [Bug 422648] KMail crash when moving window around/focusing

2020-06-08 Thread Jay
https://bugs.kde.org/show_bug.cgi?id=422648

Jay  changed:

   What|Removed |Added

 CC||jay.aurab...@gmail.com
Version|unspecified |5.13.2

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

[kmail2] [Bug 422648] New: KMail crash when moving window around/focusing

2020-06-08 Thread Jay
https://bugs.kde.org/show_bug.cgi?id=422648

Bug ID: 422648
   Summary: KMail crash when moving window around/focusing
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jay.aurab...@gmail.com
  Target Milestone: ---

Application: kmail (5.13.2 (19.12.2))

Qt Version: 5.13.2
Frameworks Version: 5.70.0
Operating System: Linux 5.6.15-300.fc32.x86_64 x86_64
Windowing system: X11
Distribution: "Fedora release 32 (Thirty Two)"

-- Information about the crash:
Tried running KMail outside KDE environment. I have kwalletd5 running in the
background. KMail crashes intermittently. Sometimes it takes a while, sometimes
pretty quick. Sometimes moving the KMail window to another workspace (awesome
wm) kills it. Sometimes focusing to KMail kills it.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5b236f8340 (LWP 17252))]

Thread 35 (Thread 0x7f5ab93b1700 (LWP 18991)):
#0  0x7f5b305f91b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5b2a786dfa in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7f5b2a787843 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7f5b2a7879c1 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#4  0x7f5b2a73de61 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f5b2a740ee2 in base::internal::SchedulerWorker::RunWorker() () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7f5b2a7417d4 in base::internal::SchedulerWorker::RunPooledWorker() ()
from /lib64/libQt5WebEngineCore.so.5
#7  0x7f5b2a789d6a in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0
#9  0x7f5b329c49d3 in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7f5a95ffb700 (LWP 17502)):
#0  0x7f5b305f91b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5b2a786dfa in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7f5b2a787843 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7f5b2a7879c1 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#4  0x7f5b2a73de61 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f5b2a74127b in base::internal::SchedulerWorker::RunWorker() () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7f5b2a7417d4 in base::internal::SchedulerWorker::RunPooledWorker() ()
from /lib64/libQt5WebEngineCore.so.5
#7  0x7f5b2a789d6a in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0
#9  0x7f5b329c49d3 in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f5a69625700 (LWP 17354)):
#0  0x7f5b329b9b6f in poll () from /lib64/libc.so.6
#1  0x7f5b2fbd5ace in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#2  0x7f5b2fbd5c03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f5b32f12c23 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f5b32ec621b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f5b32d3a577 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f5b32d3b846 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0
#8  0x7f5b329c49d3 in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f5a6ac55700 (LWP 17341)):
#0  0x7f5b305f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5b149141db in util_queue_thread_func () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f5b14913cab in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5b329c49d3 in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f5a6b456700 (LWP 17340)):
#0  0x7f5b305f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5b2a786cfc in base::ConditionVariable::Wait() () from
/lib64/libQt5WebEngineCore.so.5
#2  0x7f5b2a787850 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks

[kleopatra] [Bug 421216] Notepad widget allows rich text to be pasted

2020-06-08 Thread Andre Heinecke
https://bugs.kde.org/show_bug.cgi?id=421216

Andre Heinecke  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/pim/
   ||kleopatra/commit/089ae0574b
   ||15bcabcf67aa8a01511864995ad
   ||870
 Resolution|--- |FIXED

--- Comment #1 from Andre Heinecke  ---
Git commit 089ae0574b15bcabcf67aa8a01511864995ad870 by Andre Heinecke.
Committed on 08/06/2020 at 13:33.
Pushed by aheinecke into branch 'master'.

Do not accept rich text in notepad

Accepting rich text breaks too often better to
convert to plain before this.
GnuPG-Bug-Id: T4969

M  +1-0src/view/padwidget.cpp

https://invent.kde.org/pim/kleopatra/commit/089ae0574b15bcabcf67aa8a01511864995ad870

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

[Akonadi] [Bug 422624] New: Akonadi does full rescan on every change in maildir

2020-06-08 Thread Lars Doelle
https://bugs.kde.org/show_bug.cgi?id=422624

Bug ID: 422624
   Summary: Akonadi does full rescan on every change in maildir
   Product: Akonadi
   Version: 5.14.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: lars.doe...@on-line.de
  Target Milestone: ---

Hi All,

for some days now, akonadi apparently fully scans the maildir whenever anything
is changed, i.e. mail received, sent, deleted, etc. This process takes about 2
minutes for the 10.000 mails i have in the maildir. Beside this problem makes
kmail virtually unusable for more but a few actions per day, it also has the
potential to age the SSD.

Unfortunately, i cannot give much further information, but i usually experience
such kind of errors during scanning, when something fails to parse. Thus the
issue could be triggered by some mail not formatted as it should be, perhaps.
In any case, i believe it is a local issue.

I write for any suggestion what i could do to further narrow the bug or work
around it.

I already tried without success:

  $ akonadictl fsck

Kind regards

  Lars

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

[Akonadi] [Bug 338571] Performance Regression: Folder synchronisation in Akonadi 16.08 (actually in any release, starting with KDE 4.14) very slow, compared to kMail from KDE 4.13.x

2020-06-08 Thread Gard Spreemann
https://bugs.kde.org/show_bug.cgi?id=338571

Gard Spreemann  changed:

   What|Removed |Added

 CC|gspreem...@gmail.com|

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

[kontact] [Bug 422617] New: Update Messenger list - information not saved

2020-06-08 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=422617

Bug ID: 422617
   Summary: Update Messenger list - information not saved
   Product: kontact
   Version: 5.14.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: contacts
  Assignee: kdepim-bugs@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

Contact allows adding messenger information.
This lst is a bit outdated (ICQ - huh?)
Please addMatrix
Telegram
Matrix
because without adding a messenger it does not save the messenger-ID (which is
a bug IMO)

Operating System: openSUSE Tumbleweed 20200604
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0
Kernel Version: 5.6.14-1-default

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