[kmail2] [Bug 364558] Flagging as "unread" triggers multiple-selection

2020-12-22 Thread Thiago Sueto
https://bugs.kde.org/show_bug.cgi?id=364558

Thiago Sueto  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Thiago Sueto  ---
Thank you for replying :)
Marking this as fixed. If you ever come back to using KMail and experience this
again, please file a new bug report.

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

[korganizer] [Bug 409912] Quietly "saves" invalid event (incidence) start or end times as midnight (particularly affects fr_CA sub-locale)

2020-12-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409912

gjditchfi...@acm.org changed:

   What|Removed |Added

   Version Fixed In||5.16.0
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
 CC||gjditchfi...@acm.org

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

[Akonadi] [Bug 430722] New: kmail keeps crashing after latest update

2020-12-22 Thread Graeme Murray
https://bugs.kde.org/show_bug.cgi?id=430722

Bug ID: 430722
   Summary: kmail keeps crashing after latest update
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: graeme.w.mur...@gmail.com
  Target Milestone: ---

Application: akonadiserver (5.16.0 (20.12.0))

Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.9.14-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- Unusual behavior I noticed:
After the latest update to Tumbleweed, kmail just keeps crashing.

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault

[KCrash Handler]
#4  0x561fd94fdd77 in ?? ()
#5  0x7f40fc8532b1 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f40fc82725f in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#7  0x7f40fc829cc1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#8  0x7f40fc87f153 in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f40faacccf7 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f40faacd078 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x7f40faacd12f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x7f40fc87e7fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#13 0x7f40fc825c4b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#14 0x7f40fc644d0e in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#15 0x7f40fc645e51 in ?? () from /usr/lib64/libQt5Core.so.5
#16 0x7f40fb8993e9 in start_thread () from /lib64/libpthread.so.0
#17 0x7f40fc279943 in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f40f7f0f640 (LWP 4258) "QDBusConnection"):
#1  0x7f40fab1944f in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f40faacc98a in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f40faaccfb5 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f40faacd12f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f40fc87e7fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f40fc825c4b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f40fc644d0e in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f40fcb837c7 in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x7f40fc645e51 in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x7f40fb8993e9 in start_thread () from /lib64/libpthread.so.0
#11 0x7f40fc279943 in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f40fcbf5840 (LWP 4255) "akonadiserver"):
#1  0x7f40fc64bd54 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f40fc645b39 in QThread::wait(QDeadlineTimer) () from
/usr/lib64/libQt5Core.so.5
#3  0x7f40fc644a6c in QThread::wait(unsigned long) () from
/usr/lib64/libQt5Core.so.5
#4  0x561fd951c0d7 in ?? ()
#5  0x561fd94fb0da in ?? ()
#6  0x561fd9447371 in ?? ()
#7  0x561fd943de24 in ?? ()
#8  0x7f40fc1a0152 in __libc_start_main () from /lib64/libc.so.6
#9  0x561fd9440e7e in ?? ()
[Inferior 1 (process 4255) detached]

Possible duplicates by query: bug 430698, bug 430623, bug 430543, bug 430286,
bug 430186.

Reported using DrKonqi

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

[kmail2] [Bug 430721] New: some attachments are not shown with setting header/standard in eMail window

2020-12-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=430721

Bug ID: 430721
   Summary: some attachments are not shown with setting
header/standard in eMail window
   Product: kmail2
   Version: 5.15.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: pug...@yahoo.de
  Target Milestone: ---

SUMMARY
When view/header/standard is configured some attachments are not shown in the
email window, so that there is no indication of an attachment there. Switching
to view/header/decorative shows the attachments in the same email window's
header section.

Example code for not shown attachment with standard header ([UUID] is a
placeholder):
--Apple-Mail=_[UUID]
Content-Disposition: inline;
filename="filename.pdf"
Content-Type: application/pdf;
x-unix-mode=0644;
name="filename.pdf"
Content-Transfer-Encoding: base64

[code]

Example code for shown attachment with standard header:
--multipart_alternative.123456789--

--multipart_mixed.987654321
Content-Type: application/pdf
Content-Length: 42000
Content-Disposition: attachment; filename="filename.pdf"
Content-Transfer-Encoding: base64

[code]

OBSERVED RESULT
No indication of an attachment in the email window.

EXPECTED RESULT
An attachment is shown in standard view in all emails

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.2

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

[kmail2] [Bug 430719] New: Navigate through emails in email message windows: next, previous, next unread, previous unread

2020-12-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=430719

Bug ID: 430719
   Summary: Navigate through emails in email message windows:
next, previous, next unread, previous unread
   Product: kmail2
   Version: 5.15.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: pug...@yahoo.de
  Target Milestone: ---

SUMMARY
Dear Maintainer,

when opening emails in windows on their own the next email has to opened by
closing the current window, selecting the next one in the folder and opening it
in another window. It would be desirable to be able to navigate through email
from within the email window.
Fun fact, this was an unanswered question on stackexchange 4 years and 9
mtónths ago: https://unix.stackexchange.com/questions/259812/next-unread-
message-shortcut-in-kmail-message-window

This is amplified by kmail's misbehaviour on KDE Wayland. Through the inability
to show the email in the preview pane, emails have to be opened in email
message windows on Wayland (see https://bugs.kde.org/show_bug.cgi?id=414955)

STEPS TO REPRODUCE
1. Open an email in a window of its own
2. To open the next, previous,... email there is no button

OBSERVED RESULT
No button or shortcut to switch to the next, previous, ...

EXPECTED RESULT
A convenient way to move between emails inside a folder without having to close
the email window

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.2

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

[Akonadi] [Bug 310210] Cannot add apple / icloud address book resource with CardCAV

2020-12-22 Thread Sunny
https://bugs.kde.org/show_bug.cgi?id=310210

Sunny  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

--- Comment #7 from Sunny  ---
Hi, i have the same problem. i cannot add apple carddav account to
KAddressBook. it works with Evolution and thunderbird though. with CalDav I can
add the account but the events do not sync.

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

[Akonadi] [Bug 310210] Cannot add apple / icloud address book resource with CardCAV

2020-12-22 Thread Sunny
https://bugs.kde.org/show_bug.cgi?id=310210

--- Comment #6 from Sunny  ---
Created attachment 134271
  --> https://bugs.kde.org/attachment.cgi?id=134271=edit
Cannot add Carddav iCloud

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

[kmail2] [Bug 364558] Flagging as "unread" triggers multiple-selection

2020-12-22 Thread Tim Holy
https://bugs.kde.org/show_bug.cgi?id=364558

--- Comment #2 from Tim Holy  ---
Apologies, but I now use my institution's webmail rather than kmail. Sounds
like it may have been fixed, though, thanks!

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

[Akonadi] [Bug 310210] Cannot add apple / icloud address book resource with CardCAV

2020-12-22 Thread Sunny
https://bugs.kde.org/show_bug.cgi?id=310210

Sunny  changed:

   What|Removed |Added

 CC||sunnykoduk...@yahoo.com

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

[kcalutils] [Bug 430718] New: Display time zone information in calendar invitation e-mail

2020-12-22 Thread Laurent Pinchart
https://bugs.kde.org/show_bug.cgi?id=430718

Bug ID: 430718
   Summary: Display time zone information in calendar invitation
e-mail
   Product: kcalutils
   Version: git
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: laurent.pinch...@ideasonboard.com
  Target Milestone: ---

SUMMARY

When korganizer sends an e-mail with an invitation, the body of the e-mail is
created by IncidenceFormatter::MailBodyVisitor::visit(). It contains the start
and end date and time of the event, but doesn't display any time zone
information. The attached .ics file contains the time zone information, but a
casual glance at the e-mail may give incorrect time information to the
recipient. Including the time zone in the e-mail body would be useful.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


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.

[kontact] [Bug 396443] Crashes whith Kontact after importation

2020-12-22 Thread Jipeget
https://bugs.kde.org/show_bug.cgi?id=396443

Jipeget  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

--- Comment #4 from Jipeget  ---
The platform is Kubuntu 18.04

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

[kontact] [Bug 396443] Crashes whith Kontact after importation

2020-12-22 Thread Jipeget
https://bugs.kde.org/show_bug.cgi?id=396443

Jipeget  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #3 from Jipeget  ---
Kontact still krashes, when for example, I add a Ical Calendar whereas this
same Calendar can be opened in Korganizer alone with no worries.

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

[kmail2] [Bug 430678] Allow to only enable specific external images

2020-12-22 Thread xdmx
https://bugs.kde.org/show_bug.cgi?id=430678

--- Comment #4 from xdmx  ---
(In reply to Laurent Montel from comment #2)
> Ok I found it 
> https://support.mozilla.org/en-US/kb/remote-content-in-messages

Yes, this is exactly the feature I was referring to.

One thing to note is that when you click on those entries to allow them, that's
saved for future (/past/other) emails as well. So if for example you enable
images from assets.kde.org in 1 email, then all emails will allow that url as
well (with the "edit remote content preferences" option to remove it if
needed/clicked by mistake)

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

[kontact] [Bug 425931] Application: Kontact (kontact), signal: Segmentation fault

2020-12-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=425931

--- Comment #19 from john4deidre2...@xtra.co.nz ---
Created attachment 134261
  --> https://bugs.kde.org/attachment.cgi?id=134261=edit
New crash information added by DrKonqi

kontact (5.16.0 (20.12.0)) using Qt 5.15.2

- What I was doing when the application crashed:

This error still exists in the latest 20.12.  this is a very long-term issue

-- Backtrace (Reduced):
#4  std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at
/usr/include/c++/10/bits/atomic_base.h:420
#5  QAtomicOps::loadRelaxed (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QtPrivate::RefCount::isShared (this=) at
../../include/QtCore/../../src/corelib/tools/qrefcount.h:101
#8  QList::append (this=0x100, t=@0x7ffd20d5aac0: 0x5599df409640) at
../../include/QtCore/../../src/corelib/tools/qlist.h:622

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

[Akonadi] [Bug 430698] New: akonadi crashes in case of opening addressbook

2020-12-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=430698

Bug ID: 430698
   Summary: akonadi crashes in case of opening addressbook
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: tho...@posteo.de
  Target Milestone: ---

Application: akonadiserver (5.14.2 (20.04.2))

Qt Version: 5.12.7
Frameworks Version: 5.71.0
Operating System: Linux 5.3.18-lp152.152.g8c0e3b7-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.2"

-- Information about the crash:
- What I was doing when the application crashed:
open adressbook
addressbook told "akonadi is not running - please press start"
while aconadi tries to start it crashes

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f8689a08700 (LWP 2850)):
[KCrash Handler]
#4  0x7f869431c520 in raise () from /lib64/libc.so.6
#5  0x7f869431db01 in abort () from /lib64/libc.so.6
#6  0x7f869435f957 in __libc_message () from /lib64/libc.so.6
#7  0x7f8694366173 in malloc_printerr () from /lib64/libc.so.6
#8  0x7f8694367a79 in _int_free () from /lib64/libc.so.6
#9  0x5599bd08076f in QTypedArrayData::deallocate
(data=) at /usr/include/qt5/QtCore/qarraydata.h:239
#10 QString::~QString (this=0x7f86640a1530, __in_chrg=) at
/usr/include/qt5/QtCore/qstring.h:1135
#11 QHashNode
>::~QHashNode (this=, __in_chrg=) at
/usr/include/qt5/QtCore/qhash.h:149
#12 QHash >::deleteNode2
(node=0x7f86640a1520) at /usr/include/qt5/QtCore/qhash.h:547
#13 QHash >::deleteNode
(node=0x7f86640a1520, this=0x5599bdc17f10) at
/usr/include/qt5/QtCore/qhash.h:537
#14 QHash >::erase
(this=this@entry=0x5599bdc17f10, it=..., it@entry=...) at
/usr/include/qt5/QtCore/qhash.h:874
#15 0x5599bd07f1ff in QHash >::erase (it=...,
this=0x5599bdc17f10) at /usr/include/qt5/QtCore/qhash.h:477
#16 Akonadi::Server::ItemRetrievalManager::processRequest (this=) at
/usr/src/debug/akonadi-server-20.04.2-lp152.2.3.1.x86_64/src/server/storage/itemretrievalmanager.cpp:136
#17 0x7f8694f6a9e2 in QObject::event (this=0x5599bdc17ee0, e=) at kernel/qobject.cpp:1261
#18 0x7f8694f3a311 in doNotify (event=0x7f8684017d60,
receiver=0x5599bdc17ee0) at kernel/qcoreapplication.cpp:1178
#19 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1164
#20 QCoreApplication::notifyInternal2 (receiver=0x5599bdc17ee0,
event=0x7f8684017d60) at kernel/qcoreapplication.cpp:1088
#21 0x7f8694f3a4fe in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7f8684017d60) at kernel/qcoreapplication.cpp:1476
#22 0x7f8694f3cee7 in QCoreApplicationPrivate::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x5599bdc67a30) at kernel/qcoreapplication.cpp:1825
#23 0x7f8694f3d488 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1679
#24 0x7f8694f97d93 in postEventSourceDispatch (s=0x7f8664004770) at
kernel/qeventdispatcher_glib.cpp:276
#25 0x7f8690b084a4 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#26 0x7f8690b08840 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x7f8690b088cc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#28 0x7f8694f973af in QEventDispatcherGlib::processEvents
(this=0x7f8664000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#29 0x7f8694f3857a in QEventLoop::exec (this=this@entry=0x7f8689a07cb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#30 0x7f8694d5d90a in QThread::exec (this=) at
thread/qthread.cpp:531
#31 0x7f8694d5f0b2 in QThreadPrivate::start (arg=0x5599bdc0bb20) at
thread/qthread_unix.cpp:361
#32 0x7f86931064f9 in start_thread () from /lib64/libpthread.so.0
#33 0x7f86943defbf in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f868a209700 (LWP 2849)):
#0  0x7f8694f96cbf in qt_gettime () at kernel/qelapsedtimer_unix.cpp:182
#1  0x7f8694f954e9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f8668005120) at kernel/qtimerinfo_unix.cpp:91
#2  0x7f8694f95ac5 in QTimerInfoList::timerWait (this=0x7f8668005120,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#3  0x7f8694f9710e in timerSourcePrepareHelper (timeout=0x7f868a208ae4,
src=) at kernel/qeventdispatcher_glib.cpp:132
#4  timerSourcePrepare (source=, timeout=0x7f868a208ae4) at
kernel/qeventdispatcher_glib.cpp:165
#5  0x7f8690b07d19 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f8690b086eb in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7f8690b088cc in 

[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on starting connection to backend postgresql database

2020-12-22 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=430689

--- Comment #4 from Christophe Giboudeaux  ---
(In reply to stuart from comment #3)
> This started in August after the initial upgrade to 20.08 while I was
> running postgresql 12.4.  I later upgraded to postgresql t0 13.1.  After
> [...]

Major version updates require upgrading the database manually.

Read https://userbase.kde.org/Akonadi/Postgres_update for the generic way to do
this.

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