[kmail2] [Bug 365753] search results are not updated in the search folder (Last Search)

2017-01-11 Thread Björn Wolf 
https://bugs.kde.org/show_bug.cgi?id=365753

Björn Wolf  changed:

   What|Removed |Added

 CC||bjoern.w...@gmail.com

--- Comment #2 from Björn Wolf  ---
I get this bug, too.

Kubuntu 14.04 LTS
KMail 4.13.3
KDE Platform Version 4.13.3

I did some Re-Indexing according to
https://forum.kde.org/viewtopic.php?f=154=120988 but this did not help

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

[Akonadi] [Bug 366112] [regression] Akonadi does not load remote calendar source

2017-01-11 Thread Dan 
https://bugs.kde.org/show_bug.cgi?id=366112

Dan  changed:

   What|Removed |Added

Version|5.2.0   |5.4.0

--- Comment #3 from Dan  ---
The regression is still present in Akonadi 5.4. Which information is missing to
get this issue confirmed?

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

[kontact] [Bug 374945] kontact crash after closing

2017-01-11 Thread d-sha 
https://bugs.kde.org/show_bug.cgi?id=374945

--- Comment #1 from d-sha  ---
Sorry NOT related to  bug 372712

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

[kontact] [Bug 374945] New: kontact crash after closing

2017-01-11 Thread d-sha 
https://bugs.kde.org/show_bug.cgi?id=374945

Bug ID: 374945
   Summary: kontact crash after closing
   Product: kontact
   Version: 5.2.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: deanshann...@gmail.com
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
Selected file -> quit

I believe this is related to bug # 366422 but the crash reporting assistant
would not attach to that bug report

-- 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 0x7f888cdb0940 (LWP 11753))]

Thread 27 (Thread 0x7f870202c700 (LWP 23068)):
#0  0x7f88a31c156d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f889b36f9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f889b36fb0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f88a3ceb01b in QEventDispatcherGlib::processEvents
(this=0x7f87e8c14e80, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f88a3c9497a in QEventLoop::exec (this=this@entry=0x7f870202bc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f88a3ac20f3 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f88a3ac6da8 in QThreadPrivate::start (arg=0x5590889d5140) at
thread/qthread_unix.cpp:368
#7  0x7f889d123464 in start_thread (arg=0x7f870202c700) at
pthread_create.c:333
#8  0x7f88a31ca9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 26 (Thread 0x7f870282d700 (LWP 23063)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67
#1  0x7f88a31c1562 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f889b36f9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f889b36fb0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f88a3ceb01b in QEventDispatcherGlib::processEvents
(this=0x7f87dc017f10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f88a3c9497a in QEventLoop::exec (this=this@entry=0x7f870282cc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f88a3ac20f3 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f88a3ac6da8 in QThreadPrivate::start (arg=0x559088865a10) at
thread/qthread_unix.cpp:368
#8  0x7f889d123464 in start_thread (arg=0x7f870282d700) at
pthread_create.c:333
#9  0x7f88a31ca9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 25 (Thread 0x7f8720858700 (LWP 23021)):
#0  0x7fffab2b89f0 in clock_gettime ()
#1  0x7f88a31d7886 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f87208579e0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f88a3b6c061 in qt_clock_gettime (ts=0x7f87208579e0, clock=) at tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x7f88a3ce8c99 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f8710015060) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f88a3ce9245 in QTimerInfoList::timerWait (this=0x7f8710015060,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f88a3cea5ee in timerSourcePrepareHelper (timeout=0x7f8720857ab4,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=, timeout=0x7f8720857ab4) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x7f889b36eedd in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f889b36f91b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f889b36fb0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f88a3ceb01b in QEventDispatcherGlib::processEvents
(this=0x7f8710015550, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7f88a3c9497a in QEventLoop::exec (this=this@entry=0x7f8720857c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x7f88a3ac20f3 in QThread::exec (this=) at
thread/qthread.cpp:507
#15 0x7f88a3ac6da8 in QThreadPrivate::start (arg=0x559084076430) at
thread/qthread_unix.cpp:368
#16 0x7f889d123464 in start_thread (arg=0x7f8720858700) at
pthread_create.c:333
#17 0x7f88a31ca9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 24 (Thread 0x7f8707df5700 (LWP 23019)):
#0  0x7f88a3cea8d2 in postEventSourceCheck (source=0x7f871400c400) at
kernel/qeventdispatcher_glib.cpp:268
#1  0x7f889b36f3f9 in g_main_context_check () from

[kontact] [Bug 308352] kontact crash when moving folders

2017-01-11 Thread Sérgio Basto 
https://bugs.kde.org/show_bug.cgi?id=308352

--- Comment #3 from Sérgio Basto  ---
OK , sorry for nor reply sooner

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

[kmail2] [Bug 339181] moving mails from cached imap to local folder leaves mails without RID

2017-01-11 Thread Knut Hildebrandt 
https://bugs.kde.org/show_bug.cgi?id=339181

--- Comment #21 from Knut Hildebrandt  ---
Hello Martin,

(In reply to Martin Steigerwald from comment #20)
> Kurt, I was tempted to just reopen the bug report, but as… 

I made my comment #19 here because the problem was solved for me after this bug
has been marked "RESOLVED FIXED".

As you proposed I wrote a new Bug 374925 report.

But since the issue has been described in various bug reports someone with
knowledge of the code base should sort out which of these bugs should be closed
or marked as duplicates. These are the bugs I see related to this bug:

Bug 344242: Mails that are copied do not appear on my harddrive

Bug 341192: Moving messages does not synchronize to disk

Bug 360834: no mechanism to reattempt to store items without rid (just in db)
into the resource

Bug 338238: copied or moved mails are often not processed correctly (POP3)


Thanks for looking into the matter.

Knut

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

[kmail2] [Bug 374926] New: Printout of Mails with umlauts from kmail 5.3 isn´t possible

2017-01-11 Thread Jürgen Möschk 
https://bugs.kde.org/show_bug.cgi?id=374926

Bug ID: 374926
   Summary: Printout of Mails with umlauts from kmail 5.3 isn´t
possible
   Product: kmail2
   Version: 5.3.44 pre (QtWebEngine)
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: juergen.moes...@t-online.de
  Target Milestone: ---

Created attachment 103360
  --> https://bugs.kde.org/attachment.cgi?id=103360=edit
In this textfile your can see the original E-mail text and the printout text
version.

When i wont to print a E-Mail from K-Mail 5.3 and this E-Mail includes umlauts
like ä, ö or ü, this umlauts are konverted in other symbols.

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

[Akonadi] [Bug 374925] New: Moving Mails from an IMAP folder to a local folder does not copy files to respective directories on the hard disk

2017-01-11 Thread Knut Hildebrandt 
https://bugs.kde.org/show_bug.cgi?id=374925

Bug ID: 374925
   Summary: Moving Mails from an IMAP folder to a local folder
does not copy files to respective directories on the
hard disk
   Product: Akonadi
   Version: 5.4.0
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: knut.hildebra...@gmx.de
  Target Milestone: ---

This bug seemed to have been fixed awhile ago but reappeared after a recent
update. For me everything worked fine after Bug 339181 had been marked
"RESOLVED FIXED".


Bug description:
When I move more than one mail from an IMAP account to a local folder only one
of the mail bodies is copied to the respective directory under
"~/.local/share/.local-mail.directory/" on the hard disk even though in Kmail
all mails are shown in the local folder.

Steps to reproduce:
Move more than one mail at a time from an IMAP account to a local folder. Check
the respective directory under  "~/.local/share/.local-mail.directory/" an see
how many of the mail bodies are copied there.

Workaround:
If the mails are not moved but copied all mail bodies appear in the directory
on the hard disk.

Versions used:
KMail 5.4.0
akonadi 16.12.0


As I wrote in Bug 339181 I see this bug related to a couple of other bugs and
thus would propose that someone with knowledge of the code base should sort out
which of these bugs should be closed or marked as duplicates. These are the
bugs I see related to this bug:

Bug 339181: moving mails from cached imap to local folder leaves mails without
RID

Bug 344242: Mails that are copied do not appear on my harddrive

Bug 341192: Moving messages does not synchronize to disk

Bug 360834: no mechanism to reattempt to store items without rid (just in db)
into the resource

Bug 338238: copied or moved mails are often not processed correctly (POP3)


Thanks for looking into the matter.

Knut

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

[kontact] [Bug 374923] cannot used Ctrl-n in kontact to create new mail

2017-01-11 Thread jetojedno 
https://bugs.kde.org/show_bug.cgi?id=374923

jetojedno  changed:

   What|Removed |Added

 Attachment #103358|lontact shortcuts settings  |kontact shortcuts settings
description||

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

[kontact] [Bug 374923] cannot used Ctrl-n in kontact to create new mail

2017-01-11 Thread jetojedno 
https://bugs.kde.org/show_bug.cgi?id=374923

--- Comment #2 from jetojedno  ---
Created attachment 103359
  --> https://bugs.kde.org/attachment.cgi?id=103359=edit
more kontact shortcut settings

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

[kontact] [Bug 374923] cannot used Ctrl-n in kontact to create new mail

2017-01-11 Thread jetojedno 
https://bugs.kde.org/show_bug.cgi?id=374923

--- Comment #1 from jetojedno  ---
Created attachment 103358
  --> https://bugs.kde.org/attachment.cgi?id=103358=edit
lontact shortcuts settings

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

[kontact] [Bug 374923] New: cannot used Ctrl-n in kontact to create new mail

2017-01-11 Thread jetojedno 
https://bugs.kde.org/show_bug.cgi?id=374923

Bug ID: 374923
   Summary: cannot used Ctrl-n in kontact to create new mail
   Product: kontact
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-bugs@kde.org
  Reporter: ad...@different-perspectives.com
  Target Milestone: ---

Created attachment 103357
  --> https://bugs.kde.org/attachment.cgi?id=103357=edit
ambiguous popup box

Fresh update from openSUSE.  Kontact 5.3.0.  Defined shortcut Ctrl-n in kmail
for new message.  In Kontact, with mail selected.  Ctrl-n results in a popup
box saying the shortcut is ambiguous, and to edit the Shortcuts.  The
shourtcuts (in Kontact) look right to me.

The shortcut is not ambiguous in the context.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

2017-01-11 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=374734

--- Comment #6 from stefanfr...@gmx.net ---
Crash report of akonadi server:
Application: akonadiserver (akonadiserver), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcb47c55080 (LWP 1116))]

Thread 39 (Thread 0x7fcacbfff700 (LWP 1917)):
#0  0x7fcb42ba5c33 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#1  0x7fcb42ba66ab in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fcb42ba689c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fcb468142db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fcb467bdd3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fcb465e0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 38 (Thread 0x7fcae67fc700 (LWP 1907)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 37 (Thread 0x7fcaa6ffd700 (LWP 1906)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 36 (Thread 0x7fcae4ff9700 (LWP 1905)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 35 (Thread 0x7fcae57fa700 (LWP 1904)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 34 (Thread 0x7fcaa77fe700 (LWP 1903)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 33 (Thread 0x7fcaa5ffb700 (LWP 1875)):
#0  0x7fcb45cda48d in poll () from /usr/lib/libc.so.6
#1  0x7fcb42ba6786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fcb42ba689c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fcb468142db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fcb467bdd3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fcb465e0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 32 (Thread 0x7fcaa67fc700 (LWP 1776)):
#0  0x7fcb42bebdd4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7fcb42ba5d60 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fcb42ba66ab in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fcb42ba689c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fcb468142db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fcb467bdd3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fcb465e0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fcb4487d454 in start_thread () from

[kmail2] [Bug 374917] New: Trash button in message detail window should not be inactive when opened from notification

2017-01-11 Thread sedrubal 
https://bugs.kde.org/show_bug.cgi?id=374917

Bug ID: 374917
   Summary: Trash button in message detail window should not be
inactive when opened from notification
   Product: kmail2
   Version: 5.3.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@sedrubal.de
  Target Milestone: ---

Created attachment 103353
  --> https://bugs.kde.org/attachment.cgi?id=103353=edit
Trash button is inactive when window was opened from notification

When double clicking on an email in the message list or when clicking on the
button in the notification, when a new mail arrives, a window with this email
opens.

In this window there is a "Trash" button, which is inactive/not click-able,
when it was opened from the notification.

It was nice if this button would delete the mail and close the window, like it
does, when you open the window by double clicking on a mail in message list.

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

[akregator] [Bug 374221] akregator does not start on MATE

2017-01-11 Thread Laurent Bonnaud 
https://bugs.kde.org/show_bug.cgi?id=374221

Laurent Bonnaud  changed:

   What|Removed |Added

Summary|akregator does not on MATE  |akregator does not start on
   ||MATE

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

[kontact] [Bug 363024] New contact editor misses options to display messages in HTML

2017-01-11 Thread Till Schäfer 
https://bugs.kde.org/show_bug.cgi?id=363024

--- Comment #3 from Till Schäfer  ---
3. Add another tab "message display" or "appearance"


=> what do you think? I would prefer option 1.

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

[kontact] [Bug 363024] New contact editor misses options to display messages in HTML

2017-01-11 Thread Till Schäfer 
https://bugs.kde.org/show_bug.cgi?id=363024

--- Comment #2 from Till Schäfer  ---
I see a few options here to place the settings: 


1. Rename the tab "crypto settings" to security and add the options here. This
would also align with the global settings structure. One needs to rename the
groups labels from "Allowed Protocols" to "Allowed Crypto Protocols" and
"Message Preference" to "Crypto Message Preference" in this case.
2. Add the Settings to the Contact tab.

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

[kontact] [Bug 363024] New contact editor misses options to display messages in HTML

2017-01-11 Thread Till Schäfer 
https://bugs.kde.org/show_bug.cgi?id=363024

Till Schäfer  changed:

   What|Removed |Added

Summary|Kontact 16.12.0: New|New contact editor misses
   |contact editor misses   |options to display messages
   |options to display messages |in HTML
   |in HTML |
Version|unspecified |5.4.0

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

[kontact] [Bug 369247] Kontact 5.4.0: settings between Kontact and components (e.g. KMail) are not synchronized

2017-01-11 Thread Till Schäfer 
https://bugs.kde.org/show_bug.cgi?id=369247

Till Schäfer  changed:

   What|Removed |Added

Summary|Kontact 5.3.1: settings |Kontact 5.4.0: settings
   |between Kontact and |between Kontact and
   |components (e.g. KMail) are |components (e.g. KMail) are
   |not synchronized|not synchronized

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

[kontact] [Bug 369247] Kontact 5.3.1: settings between Kontact and components (e.g. KMail) are not synchronized

2017-01-11 Thread Denis Kurz 
https://bugs.kde.org/show_bug.cgi?id=369247

Denis Kurz  changed:

   What|Removed |Added

Version|GIT (master)|5.4.0

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

[kontact] [Bug 369247] Kontact 5.3.1: settings between Kontact and components (e.g. KMail) are not synchronized

2017-01-11 Thread Denis Kurz 
https://bugs.kde.org/show_bug.cgi?id=369247

Denis Kurz  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||kde...@posteo.de

--- Comment #3 from Denis Kurz  ---
Confirmed for 5.4.0 using the example setting from Comment 2.

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

[kmail2] [Bug 308444] %OLONGTIME template variable does not yield timezone information

2017-01-11 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=308444

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/mes |https://commits.kde.org/mes
   |sagelib/2fafabbf7563c44d75f |sagelib/48ecc0d629cb55e2c45
   |9e9b06b5314ef3dce4763   |d4facd62b9012db385cff

--- Comment #9 from Laurent Montel  ---
Git commit 48ecc0d629cb55e2c45d4facd62b9012db385cff by Montel Laurent.
Committed on 11/01/2017 at 12:29.
Pushed by mlaurent into branch 'Applications/16.12'.

Apply patch from  Matt Whitlock + add autotest to validate it

QDateTime::time() returns a QTime, which conveys no time zone information.
QLocale::toString(const QTime &, QLocale::FormatType) then assumes that the
passed QTime is a local time. This causes a problem when processing a template
in that the time zone information of the Date header in the original message is
ignored, and the time part is then reinterpreted as a local time, which is
incorrect.

Example illustrating the problem:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
1:31:25 PM EST

QLocale apparently offers no method to format a QTime with a specific
QTimeZone, so the best that can be done is to convert the QDateTime of the
original message into a local time by calling QDateTime::toLocalTime().

After applying this fix, the above example becomes:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
2:31:25 PM EST
Related: bug 355195, bug 366768
(cherry picked from commit 2fafabbf7563c44d75f9e9b06b5314ef3dce4763)

M  +52   -14   templateparser/autotests/templateparsertest.cpp
M  +3-0templateparser/autotests/templateparsertest.h
M  +8-8templateparser/src/templateparser.cpp

https://commits.kde.org/messagelib/48ecc0d629cb55e2c45d4facd62b9012db385cff

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

[kmail2] [Bug 366768] Reply quote header uses UTC timestamp instead of local time zone

2017-01-11 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=366768

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/mes |https://commits.kde.org/mes
   |sagelib/2fafabbf7563c44d75f |sagelib/48ecc0d629cb55e2c45
   |9e9b06b5314ef3dce4763   |d4facd62b9012db385cff

--- Comment #5 from Laurent Montel  ---
Git commit 48ecc0d629cb55e2c45d4facd62b9012db385cff by Montel Laurent.
Committed on 11/01/2017 at 12:29.
Pushed by mlaurent into branch 'Applications/16.12'.

Apply patch from  Matt Whitlock + add autotest to validate it

QDateTime::time() returns a QTime, which conveys no time zone information.
QLocale::toString(const QTime &, QLocale::FormatType) then assumes that the
passed QTime is a local time. This causes a problem when processing a template
in that the time zone information of the Date header in the original message is
ignored, and the time part is then reinterpreted as a local time, which is
incorrect.

Example illustrating the problem:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
1:31:25 PM EST

QLocale apparently offers no method to format a QTime with a specific
QTimeZone, so the best that can be done is to convert the QDateTime of the
original message into a local time by calling QDateTime::toLocalTime().

After applying this fix, the above example becomes:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
2:31:25 PM EST
Related: bug 308444, bug 355195
(cherry picked from commit 2fafabbf7563c44d75f9e9b06b5314ef3dce4763)

M  +52   -14   templateparser/autotests/templateparsertest.cpp
M  +3-0templateparser/autotests/templateparsertest.h
M  +8-8templateparser/src/templateparser.cpp

https://commits.kde.org/messagelib/48ecc0d629cb55e2c45d4facd62b9012db385cff

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

[kmail2] [Bug 355195] date and time are ambiguous when replying to and forwarding messages (no timezone information)

2017-01-11 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=355195

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/mes |https://commits.kde.org/mes
   |sagelib/2fafabbf7563c44d75f |sagelib/48ecc0d629cb55e2c45
   |9e9b06b5314ef3dce4763   |d4facd62b9012db385cff

--- Comment #7 from Laurent Montel  ---
Git commit 48ecc0d629cb55e2c45d4facd62b9012db385cff by Montel Laurent.
Committed on 11/01/2017 at 12:29.
Pushed by mlaurent into branch 'Applications/16.12'.

Apply patch from  Matt Whitlock + add autotest to validate it

QDateTime::time() returns a QTime, which conveys no time zone information.
QLocale::toString(const QTime &, QLocale::FormatType) then assumes that the
passed QTime is a local time. This causes a problem when processing a template
in that the time zone information of the Date header in the original message is
ignored, and the time part is then reinterpreted as a local time, which is
incorrect.

Example illustrating the problem:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
1:31:25 PM EST

QLocale apparently offers no method to format a QTime with a specific
QTimeZone, so the best that can be done is to convert the QDateTime of the
original message into a local time by calling QDateTime::toLocalTime().

After applying this fix, the above example becomes:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
2:31:25 PM EST
Related: bug 308444, bug 366768
(cherry picked from commit 2fafabbf7563c44d75f9e9b06b5314ef3dce4763)

M  +52   -14   templateparser/autotests/templateparsertest.cpp
M  +3-0templateparser/autotests/templateparsertest.h
M  +8-8templateparser/src/templateparser.cpp

https://commits.kde.org/messagelib/48ecc0d629cb55e2c45d4facd62b9012db385cff

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

[kmail2] [Bug 308444] %OLONGTIME template variable does not yield timezone information

2017-01-11 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=308444

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/mes
   ||sagelib/2fafabbf7563c44d75f
   ||9e9b06b5314ef3dce4763
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #8 from Laurent Montel  ---
Git commit 2fafabbf7563c44d75f9e9b06b5314ef3dce4763 by Montel Laurent.
Committed on 11/01/2017 at 12:27.
Pushed by mlaurent into branch 'master'.

Apply patch from  Matt Whitlock + add autotest to validate it

QDateTime::time() returns a QTime, which conveys no time zone information.
QLocale::toString(const QTime &, QLocale::FormatType) then assumes that the
passed QTime is a local time. This causes a problem when processing a template
in that the time zone information of the Date header in the original message is
ignored, and the time part is then reinterpreted as a local time, which is
incorrect.

Example illustrating the problem:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
1:31:25 PM EST

QLocale apparently offers no method to format a QTime with a specific
QTimeZone, so the best that can be done is to convert the QDateTime of the
original message into a local time by calling QDateTime::toLocalTime().

After applying this fix, the above example becomes:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
2:31:25 PM EST
Related: bug 355195, bug 366768

M  +52   -14   templateparser/autotests/templateparsertest.cpp
M  +3-0templateparser/autotests/templateparsertest.h
M  +8-8templateparser/src/templateparser.cpp

https://commits.kde.org/messagelib/2fafabbf7563c44d75f9e9b06b5314ef3dce4763

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

[kmail2] [Bug 355195] date and time are ambiguous when replying to and forwarding messages (no timezone information)

2017-01-11 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=355195

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/mes
   ||sagelib/2fafabbf7563c44d75f
   ||9e9b06b5314ef3dce4763
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Laurent Montel  ---
Git commit 2fafabbf7563c44d75f9e9b06b5314ef3dce4763 by Montel Laurent.
Committed on 11/01/2017 at 12:27.
Pushed by mlaurent into branch 'master'.

Apply patch from  Matt Whitlock + add autotest to validate it

QDateTime::time() returns a QTime, which conveys no time zone information.
QLocale::toString(const QTime &, QLocale::FormatType) then assumes that the
passed QTime is a local time. This causes a problem when processing a template
in that the time zone information of the Date header in the original message is
ignored, and the time part is then reinterpreted as a local time, which is
incorrect.

Example illustrating the problem:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
1:31:25 PM EST

QLocale apparently offers no method to format a QTime with a specific
QTimeZone, so the best that can be done is to convert the QDateTime of the
original message into a local time by calling QDateTime::toLocalTime().

After applying this fix, the above example becomes:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
2:31:25 PM EST
Related: bug 308444, bug 366768

M  +52   -14   templateparser/autotests/templateparsertest.cpp
M  +3-0templateparser/autotests/templateparsertest.h
M  +8-8templateparser/src/templateparser.cpp

https://commits.kde.org/messagelib/2fafabbf7563c44d75f9e9b06b5314ef3dce4763

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

[kmail2] [Bug 366768] Reply quote header uses UTC timestamp instead of local time zone

2017-01-11 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=366768

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/mes
   ||sagelib/2fafabbf7563c44d75f
   ||9e9b06b5314ef3dce4763
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Laurent Montel  ---
Git commit 2fafabbf7563c44d75f9e9b06b5314ef3dce4763 by Montel Laurent.
Committed on 11/01/2017 at 12:27.
Pushed by mlaurent into branch 'master'.

Apply patch from  Matt Whitlock + add autotest to validate it

QDateTime::time() returns a QTime, which conveys no time zone information.
QLocale::toString(const QTime &, QLocale::FormatType) then assumes that the
passed QTime is a local time. This causes a problem when processing a template
in that the time zone information of the Date header in the original message is
ignored, and the time part is then reinterpreted as a local time, which is
incorrect.

Example illustrating the problem:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
1:31:25 PM EST

QLocale apparently offers no method to format a QTime with a specific
QTimeZone, so the best that can be done is to convert the QDateTime of the
original message into a local time by calling QDateTime::toLocalTime().

After applying this fix, the above example becomes:

Original message header:
Date: Sun, 1 Jan 2017 13:31:25 -0600

%OTIMELONG in reply template expands to:
2:31:25 PM EST
Related: bug 308444, bug 355195

M  +52   -14   templateparser/autotests/templateparsertest.cpp
M  +3-0templateparser/autotests/templateparsertest.h
M  +8-8templateparser/src/templateparser.cpp

https://commits.kde.org/messagelib/2fafabbf7563c44d75f9e9b06b5314ef3dce4763

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

[Akonadi] [Bug 362420] DAV Resource 16.12.0: Segfaults randomly

2017-01-11 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=362420

jan...@hbz-nrw.de changed:

   What|Removed |Added

 CC||jan...@hbz-nrw.de

--- Comment #3 from jan...@hbz-nrw.de ---
Might be the same as #360792 ?

Looks like I´m affected on latest openSUSE Tumbleweed with KDE apps 16.12

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

[Akonadi] [Bug 366238] KMail does not fetch mails from imap.kabelmail.de

2017-01-11 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=366238

--- Comment #4 from franz-joseph.barth...@kabelmail.de ---
Unfortunately, there is no further debug output.

I only observe the difference between mails on the server and local mails.

Using openSUSE Tumbleweed, the most recent version of KDE Applications 16.12 is
available for testing. But the behavior has not changed.

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

[kmail2] [Bug 374903] New: KMail crashing so often it renders usless.

2017-01-11 Thread Nikolai 
https://bugs.kde.org/show_bug.cgi?id=374903

Bug ID: 374903
   Summary: KMail crashing so often it renders usless.
   Product: kmail2
   Version: 5.4.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: niko...@fastmail.fm
  Target Milestone: ---

Created attachment 103345
  --> https://bugs.kde.org/attachment.cgi?id=103345=edit
kmail strace dump

Sometimes as much as from resizing the sidebar, or going through unread mail
filter...not just once a day, every time kmail is in use it will crash out,
needs to be restarted and if i finish sending email without crash i consider it
good try.
It could be nouveau driver related or maybe not... i'm adding strace dump from
last two crashes.

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

[kmail2] [Bug 339181] moving mails from cached imap to local folder leaves mails without RID

2017-01-11 Thread Martin Steigerwald 
https://bugs.kde.org/show_bug.cgi?id=339181

--- Comment #20 from Martin Steigerwald  ---
Kurt, I was tempted to just reopen the bug report, but as… it may contain more
than one issue in one report from a quick glance at the comments, I kindly ask
you to open a new bug report with exactly the versions you use and concrete
steps on how to reproduce it. Please add a note in the comment here so people
can find the new report. Its sufficient to write a comment like "I opened bug
#number" as Bugzilla will automatically generated a link. Also please reference
this bug report from the new one with one sentence. Thank you, Martin

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

[Akonadi] [Bug 374866] Dialog for adding a vCard file has text layout issues (text cut off)

2017-01-11 Thread Laurent Montel 
https://bugs.kde.org/show_bug.cgi?id=374866

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kde
   ||pim-runtime/4d998c27dc0cb41
   ||e8b282aa1d9ea41e7c443e8cb
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Laurent Montel  ---
Git commit 4d998c27dc0cb41e8b282aa1d9ea41e7c443e8cb by Montel Laurent.
Committed on 11/01/2017 at 08:02.
Pushed by mlaurent into branch 'master'.

Allow to show text. QLabel + wordwrap doesn't work.

So I replaced it with qtextedit in readonly

Adding  setMinimumSize(sizeHint()) doesn't work when we add it on each
qlabel

M  +84   -60  
resources/shared/singlefileresource/singlefileresourceconfigdialog_desktop.ui
M  +1-1   
resources/shared/singlefileresource/singlefileresourceconfigdialogbase.cpp

https://commits.kde.org/kdepim-runtime/4d998c27dc0cb41e8b282aa1d9ea41e7c443e8cb

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