[kmail2] [Bug 403313] Encoding problem on kmail2 5.10.1 when creating composer from command line

2019-01-17 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=403313

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.10.2
 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/kma
   ||il/3cebe77c92460505af04827d
   ||efeb0a9e358ba00b

--- Comment #1 from Laurent Montel  ---
Git commit 3cebe77c92460505af04827defeb0a9e358ba00b by Laurent Montel.
Committed on 17/01/2019 at 21:56.
Pushed by mlaurent into branch 'Applications/18.12'.

Fix Bug 403313 - Encoding problem on kmail2 5.10.1 when creating composer from
command line

FIXED-IN: 5.10.2

M  +1-1src/job/opencomposerjob.cpp

https://commits.kde.org/kmail/3cebe77c92460505af04827defeb0a9e358ba00b

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

[korganizer] [Bug 385364] Timezone RRULE entry has bot UNTIL and COUNT property

2019-01-17 Thread Paul Gouin
https://bugs.kde.org/show_bug.cgi?id=385364

--- Comment #7 from Paul Gouin  ---
Comment on attachment 117519
  --> https://bugs.kde.org/attachment.cgi?id=117519
PKGBUILD for patched kcalcore 18.12.1 on Arch

Same issue here with kcalcore 18.12.1 on Arch Linux.

Thanks to Ingo's helpful comments, I was able to patch it with the attached
PKGBUILD.

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

[korganizer] [Bug 385364] Timezone RRULE entry has bot UNTIL and COUNT property

2019-01-17 Thread Paul Gouin
https://bugs.kde.org/show_bug.cgi?id=385364

Paul Gouin  changed:

   What|Removed |Added

 CC||p...@pablomalo.fr

--- Comment #6 from Paul Gouin  ---
Created attachment 117519
  --> https://bugs.kde.org/attachment.cgi?id=117519=edit
PKGBUILD for patched kcalcore 18.12.1 on Arch

PKGBUILD for patched kcalcore 18.12.1 on Arch

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

[kontact] [Bug 403317] KMAIL2; "Share Text" plugin segfaults

2019-01-17 Thread Tobias Klaus
https://bugs.kde.org/show_bug.cgi?id=403317

Tobias Klaus  changed:

   What|Removed |Added

  Component|general |mail

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

[kontact] [Bug 403317] KMAIL2; "Share Text" plugin segfaults

2019-01-17 Thread Tobias Klaus
https://bugs.kde.org/show_bug.cgi?id=403317

Tobias Klaus  changed:

   What|Removed |Added

Summary|KMAIL2 segfaults during |KMAIL2; "Share Text" plugin
   |startup |segfaults

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

[kontact] [Bug 403317] KMAIL2 segfaults during startup

2019-01-17 Thread Tobias Klaus
https://bugs.kde.org/show_bug.cgi?id=403317

--- Comment #1 from Tobias Klaus  ---
After activating/deactivating every of the "Editor Plugins" I could reproduce
this by activating the "Share Text" plugin and mitigate this issue by
deactivating this  plugin.

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

[kontact] [Bug 403317] New: KMAIL2 segfaults during startup

2019-01-17 Thread Tobias Klaus
https://bugs.kde.org/show_bug.cgi?id=403317

Bug ID: 403317
   Summary: KMAIL2 segfaults during startup
   Product: kontact
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ek+...@meskal.net
  Target Milestone: ---

Application: kontact (5.10.1)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.13-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
Whenever I try to compose a new Mail (mostly using Strg+N) kmail2 crashes with
a segfault. After this happens kmail crashed during startup with the attached
backtrace.

This happens until I manually remove all autosaved mails from
.local/share/kmail2/autosave/.

If needed I can supply a backtrace of the inital crash too.

The crash can be reproduced every time.

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

Thread 31 (Thread 0x7f7fe9dca700 (LWP 19404)):
#0  0x7f812c0528a4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f812c00b229 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f812c00b9a7 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f812c00bb3c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f8132cd8c5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f8132c84b4a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f8132ae6b4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f8132af05ef in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0
#9  0x7f813216a56f in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f7fea5cb700 (LWP 19403)):
#0  0x7f813215e993 in poll () from /lib64/libc.so.6
#1  0x7f812c00ba29 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f812c00bb3c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8132cd8c5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f8132c84b4a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f8132ae6b4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f8132af05ef in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0
#8  0x7f813216a56f in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f7feb22a700 (LWP 19402)):
#0  0x7f813215e993 in poll () from /lib64/libc.so.6
#1  0x7f812c00ba29 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f812c00bb3c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8132cd8c5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f8132c84b4a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f8132ae6b4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f8132af05ef in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0
#8  0x7f813216a56f in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f80bcd77700 (LWP 19393)):
#0  0x7f8119968a58 in evutil_vsnprintf () from /usr/lib64/libevent-2.1.so.6
#1  0x7f811996bf2d in ?? () from /usr/lib64/libevent-2.1.so.6
#2  0x7f811996c21c in event_warn () from /usr/lib64/libevent-2.1.so.6
#3  0x7f811996d924 in ?? () from /usr/lib64/libevent-2.1.so.6
#4  0x7f81199636f5 in event_base_loop () from /usr/lib64/libevent-2.1.so.6
#5  0x7f81235c5331 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f81235e59fb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f812360975f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f8123605141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0
#10 0x7f813216a56f in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f80bd7fa700 (LWP 19385)):
#0  0x7f812df1491a in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f81235f2ad7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f81235f4037 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f81235f4122 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f81235f91a1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f81235fa53f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f8123605141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f812df0d9aa in start_thread () from /lib64/libpthread.so.0
#8  0x7f813216a56f in clone 

[kmail2] [Bug 403313] New: Encoding problem on kmail2 5.10.1 when creating composer from command line

2019-01-17 Thread alfazaz
https://bugs.kde.org/show_bug.cgi?id=403313

Bug ID: 403313
   Summary: Encoding problem on kmail2 5.10.1 when creating
composer from command line
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: yalme...@free.fr
  Target Milestone: ---

SUMMARY

When I create a kmail composer window from command line, it gives bad
characters in the body when they are not ascii ; it's annoying because creating
a pre-filled window for editing is broken now. 
I think it's an encoding problem (it didn't happen before a latest upgrade...).
I'm on the latest rolling release version of archlinux.

kmail2 5.10.1 (from kmail 18.12.1-1)
qt5 5.12.0-1

STEPS TO REPRODUCE

1. Open a terminal

2. Type in it 
kmail --subject Vélo --body "J'ai élevé à ma façon des vélos !"

OBSERVED RESULT
A kmail message editor is opened with a good subject (Vélo) but with this bad
body :
J'ai élevé à ma façon des vélos !

EXPECTED RESULT
A kmail message editor opened with a good subject (Vélo) but also with a good
body like this :
J'ai élevé à ma façon des vélos !

There is the same bug with the --msg option of kmail...

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux uptodate/Plasma desktop 5.14.5-2/kde 18.12.1
KDE Frameworks 5.54.0
Qt 5.12.0

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

[kontact] [Bug 403309] New: akregator crash when switching to it in Kontact

2019-01-17 Thread Robby Engelmann
https://bugs.kde.org/show_bug.cgi?id=403309

Bug ID: 403309
   Summary: akregator crash when switching to it in Kontact
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

Application: kontact (5.10.1)

Qt Version: 5.12.0
Frameworks Version: 5.54.0
Operating System: Linux 4.20.0-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
akregator crash when switching to it in Kontact. Happened first time here.

The crash can be reproduced sometimes.

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

Thread 30 (Thread 0x7f0daa7db700 (LWP 24626)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f0daafdc700 (LWP 24625)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f0dbd70b700 (LWP 24624)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f0dbdf0c700 (LWP 24623)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f0dbe70d700 (LWP 24622)):
#0  0x7f0ee74888c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0ee05e2e97 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f0ee05e37fa in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f0ee05e38e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f0ee05a1321 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f0ee05a4186 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f0ee05a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f0ee05e59f1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f0ee7482554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0ee8851ccf in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f0ebcff9700 (LWP 24621)):

[kmail2] [Bug 165419] Hide Top Level "Local Folders" when there is no IMAP account configured

2019-01-17 Thread Pavel Raiskup
https://bugs.kde.org/show_bug.cgi?id=165419

Pavel Raiskup  changed:

   What|Removed |Added

 CC||prais...@redhat.com

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

[Akonadi] [Bug 401692] Akonadi components crash on logout

2019-01-17 Thread Bruno Friedmann
https://bugs.kde.org/show_bug.cgi?id=401692

--- Comment #15 from Bruno Friedmann  ---
Here's a list of event that can be related 

Jan 17 11:29:13 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 12025, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:29:13 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 12045, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:29:13 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 12048, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:30:14 qt-kt akonadi_archivemail_agent[3570]: "Item query returned
empty result set"
Jan 17 11:30:14 qt-kt akonadi_mailfilter_agent[3600]: "Item query returned
empty result set"
Jan 17 11:30:14 qt-kt kmail[30141]: "Item query returned empty result set"
Jan 17 11:30:30 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 16665, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:30:30 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 16685, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:30:30 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 16688, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:30:39 qt-kt kmail[30141]:
QNetworkReplyHttpImplPrivate::_q_startOperation was called more than once
QUrl("https://secure.gravatar.com:443/avatar/c5c31f7c3041dfedc2b2c10d09661bfe?d=404;)
Jan 17 11:31:00 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 18447, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:31:00 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 18467, resource id: 134217775, major code: 130 (Unknown),
minor code: 3
Jan 17 11:31:00 qt-kt kmail[30141]: qt.qpa.xcb: QXcbConnection: XCB error: 8
(BadMatch), sequence: 18470, resource id: 134217775, major code: 130 (Unknown),
minor code: 3

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

2019-01-17 Thread Alexander Olofsson
https://bugs.kde.org/show_bug.cgi?id=393002

Alexander Olofsson  changed:

   What|Removed |Added

 CC||a...@haxalot.com

--- Comment #10 from Alexander Olofsson  ---
Ran into the same issue here as well after doing system upgrades. PIM 18.12.0

I tried creating a password manually in kwalletmanager as well, but didn't
realize that the title was the resource id followed by 'rc', so of course it
didn't read that one either.

I was able to set a new password as mentioned in
https://bugs.kde.org/show_bug.cgi?id=389369#c5 though, which is what revealed
the naming difference to me.

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

2019-01-17 Thread Tom Kijas
https://bugs.kde.org/show_bug.cgi?id=393002

Tom Kijas  changed:

   What|Removed |Added

 CC||t.ki...@gmail.com

--- Comment #9 from Tom Kijas  ---
I created account in KMail (EWS), opened kwallet manager, added password into
"passwords" in "akonadi-ews" and nothing changed.

In terminal it says Service
'org.freedesktop.Akonadi.Resource.akonadi_ews_resource_5/' is not a valid name.

KMail is totally useless now for work/corporate.

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

[kmail2] [Bug 403159] Blank page on print preview

2019-01-17 Thread MAG4
https://bugs.kde.org/show_bug.cgi?id=403159

--- Comment #4 from MAG4  ---
We also on all messages, plain text and html ...

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