[kmail2] [Bug 453297] KMail + Akonadi crash

2022-07-01 Thread Erik Quaeghebeur
https://bugs.kde.org/show_bug.cgi?id=453297

--- Comment #1 from Erik Quaeghebeur  ---
Created attachment 150333
  --> https://bugs.kde.org/attachment.cgi?id=150333=edit
New crash information added by DrKonqi

kmail (5.19.3 (21.12.3)) using Qt 5.15.4

- What I was doing when the application crashed:
I was restarting kmail for a second time after I had closed it down because it
was stuck loading folder contents (likely because akonadi was stuck…). The
first time also kmail crashed, but in a different way, but for that no crash
report could be sent, for some reason.

-- Backtrace (Reduced):
#4  0x7964fe145417 in std::__atomic_base::load(std::memory_order)
const (__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/bits/atomic_base.h:481
#5  QAtomicOps::loadRelaxed(std::atomic const&)
(_q_value=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed() const (this=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QtPrivate::RefCount::isShared() const (this=) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/tools/qrefcount.h:101
#8  QList::append(QWidget* const&) (this=0x598b1af40100,
t=@0x7ffce7a3af00: 0x598b1b13ae70) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/tools/qlist.h:622

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

[kmail2] [Bug 453297] KMail + Akonadi crash

2022-07-01 Thread Erik Quaeghebeur
https://bugs.kde.org/show_bug.cgi?id=453297

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||bugs.kde@e3q.eu

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

[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"

2022-07-01 Thread Antonis K
https://bugs.kde.org/show_bug.cgi?id=439285

Antonis K  changed:

   What|Removed |Added

 CC||antk...@gmail.com

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

[Akonadi] [Bug 456227] linksite

2022-07-01 Thread staceytim
https://bugs.kde.org/show_bug.cgi?id=456227

staceytim  changed:

   What|Removed |Added

URL||https://ckudqqa.xyz/

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

[Akonadi] [Bug 456227] New: linksite

2022-07-01 Thread staceytim
https://bugs.kde.org/show_bug.cgi?id=456227

Bug ID: 456227
   Summary: linksite
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Birthdays Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: staceytim...@gmail.com
  Target Milestone: ---

https://ckudqqa.xyz/; title="카지노사이트">home

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

[kontact] [Bug 393054] In summary view, birthdays and anniversaries are always shown both under upcoming events, and upcoming special dates

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=393054

--- Comment #2 from gjditchfi...@acm.org ---
Git commit 9a73aa319ed25e75d0719667138749f93f159b55 by Glen Ditchfield, on
behalf of Glen Ditchfield.
Committed on 02/07/2022 at 01:02.
Pushed by gditchfield into branch 'release/22.04'.

Fix special dates summary configuration

In the "Contact List" portion of the Kontact Summary View configuration
dialog

 * Unchecking "Show birthdays" hid *all* special dates.
 * Unchecking "Show anniversaries" did nothing.

In the "Calendar" portion, unchecking "Show anniversaries" hid both
kinds of anniversaries.

M  +26   -19   src/kontactplugin/specialdates/sdsummarywidget.cpp

https://invent.kde.org/pim/korganizer/commit/9a73aa319ed25e75d0719667138749f93f159b55

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

[kmail2] [Bug 91308] virtual threading to add sent emails to a thread

2022-07-01 Thread Yuri Gorshkov
https://bugs.kde.org/show_bug.cgi?id=91308

Yuri Gorshkov  changed:

   What|Removed |Added

 CC||m...@koshaq.net

--- Comment #12 from Yuri Gorshkov  ---
Would it be difficult to integrate this possibility into KMail? I'd say (just
to clarify), this is something akin to symlinks for replies. I have not much
more to add, but still would be nice if this was a feature after um... 17 years
of waiting (wow... i'm old! :).

PS. Sorry for necrobumping.

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

[libkgapi] [Bug 419713] KOrganizer deletes events in calendar without prompting

2022-07-01 Thread Murz
https://bugs.kde.org/show_bug.cgi?id=419713

Murz  changed:

   What|Removed |Added

 CC||mur...@gmail.com

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

[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=336581

missol...@protonmail.com changed:

   What|Removed |Added

 CC||missol...@protonmail.com

--- Comment #14 from missol...@protonmail.com ---
Just to confirm that the issue is still there for Kmail 5.20.2. The akonadi
database gets corrupted randomly (happened to me after a distro upgrade that
otherwise went perfectly fine) and after removing Akonadi's corrupted data
folders and syncing again, all folder associations were messed up. 

Can't way for the day when our whole company can start relying on KDE PIM's
framework. It looks very promising and the vision behind akonadi is brilliant,
but this data corruption issue is a deal breaker. I hope you manage to fix this
soon, stability and durability are so important for this kind of application. 

If a solution is known but what is lacking is manpower, please let the
community know so that we can try to organize sponsorship. This is such a
critical issue (I am referring to the data corruption. Folder assignment is
more a symptom. If data corruption wasn't there in the first place, folder
assignment mix up wouldn't be an issue. I feel it would probably be better to
fix the fragility of the storage system to make such symptoms non-issues by
removing a vast class of failure modes rather than rather than trying to come
up with global ids).

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

[kmail2] [Bug 456196] New: Title formatting not properly restored for HTML messages (templates, edit as new)

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456196

Bug ID: 456196
   Summary: Title formatting not properly restored for HTML
messages (templates, edit as new)
   Product: kmail2
   Version: 5.20.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: missol...@protonmail.com
  Target Milestone: ---

SUMMARY

When opening a previously saved HTML message in the composer to edit it
(whether it is a template in the templates folder of the email account, or a
regular email that the user wants to "Edit as new"), all the rich formatting
related to titles is not properly restored. To be specific:

If some text has the style "Title" applied to it, after saving the message as a
template and reopening it in the composer, the text will now have the style
"Basic text" and will only be bold (its font size has decreased: the text is as
small as Basic Text). The same happens when editing a message as new. 

>From a user perspective, the main nuisance is in the template use case since
the goal of templates is to have the formatting all set up in advance. Beyond a
permanent fix, I would appreciate a temporary workaround if any exists as this
is really affecting quality of life for email intensive workflows (customer
service, sales, etc...).


STEPS TO REPRODUCE
1. Create a new message with Rich Text, insert some text and give it the
"Title" style 
2. Save the message as Template
3. Open the message again in the composer to edit it by double clicking it in
the folder template or by using the "Edit as New" option

OBSERVED RESULT

The title has now been switched back to the style "Basic text" and while its
boldness is still there, its font size has decreased (it now has the font-size
of basic text)

EXPECTED RESULT

The title style should still be present after reopening the message in the
composer.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20220625
(available in About System)
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.2
Kernel version: 5.18.6-1-default (64-bit)

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