[kontact] [Bug 440811] Calendar events don't show up at all for some calendars

2021-08-09 Thread Thea Barnes
https://bugs.kde.org/show_bug.cgi?id=440811

Thea Barnes  changed:

   What|Removed |Added

Version|unspecified |5.17.3

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

[kontact] [Bug 440811] Calendar events don't show up at all for some calendars

2021-08-09 Thread Thea Barnes
https://bugs.kde.org/show_bug.cgi?id=440811

Thea Barnes  changed:

   What|Removed |Added

Summary|Calendar events don't sho   |Calendar events don't show
   |up at all for some  |up at all for some
   |calendars   |calendars

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

[kontact] [Bug 440811] New: Calendar events don't sho up at all for some calendars

2021-08-09 Thread Thea Barnes
https://bugs.kde.org/show_bug.cgi?id=440811

Bug ID: 440811
   Summary: Calendar events don't sho up at all for some calendars
   Product: kontact
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: calendar
  Assignee: kdepim-bugs@kde.org
  Reporter: t...@tsbarnes.com
  Target Milestone: ---

SUMMARY
Calendar events don't show up at all for some calendars

STEPS TO REPRODUCE
1. Add a calendar that uses DavMail
2. Notice that the events are never displayed
3. Check the DavMail logs, they show it successfully retrieving them

OBSERVED RESULT
No events are shown from the bugged calendar

EXPECTED RESULT
Events should be shown from all the calendars

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I've had this issue with EWS calendars as well, and occasionally with a Google
account, though with Google accounts removing it and re-adding it will
sometimes fix it.

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

[kmail2] [Bug 370385] EMail Addresses with Underscores in Contacts Not Recognised

2021-08-09 Thread jc_gargma
https://bugs.kde.org/show_bug.cgi?id=370385

--- Comment #5 from jc_gargma  ---
I still experience this bug with kmail Version 5.17.3 (21.04.3)

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Thiago Macieira
https://bugs.kde.org/show_bug.cgi?id=439769

--- Comment #14 from Thiago Macieira  ---
Fix in Qt: https://codereview.qt-project.org/c/qt/qtbase/+/363880

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Stefan
https://bugs.kde.org/show_bug.cgi?id=439769

--- Comment #13 from Stefan  ---
> Looks like opensuse packages mariadb-connector-c separately, instead of using 
> the bundled one in mariadb. So you'll be affected if you update 
> mariadb-connector-c to 3.2.3, regardless of the mariadb package version.

Thank you very much for your analysis, your right.

This was a real monday-challenge for a common simple user like me. At first i
was confused because no package "mariadb-connector-c" found on my machine. The
package is (also?) called libmariadb3
(https://software.opensuse.org/package/libmariadb3)

cat /var/log/zypp/history | grep libmariadb3

2021-07-04 08:43:18|install|libmariadb3|3.1.13-2.1
2021-08-07 21:48:18|install|libmariadb3|3.2.3-1.1

sudo zypper install --oldpackage
http://download.opensuse.org/tumbleweed/repo/oss/x86_64/libmariadb3-3.1.13-2.1.x86_64.rpm

After a reboot, the first sync takes a amount of time, but everything works as
before the 2021-08-07.

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

[akregator] [Bug 440574] Memory Leak / Memory Usage For Large Feeds

2021-08-09 Thread barray
https://bugs.kde.org/show_bug.cgi?id=440574

--- Comment #10 from barray  ---
Created attachment 140612
  --> https://bugs.kde.org/attachment.cgi?id=140612=edit
Valgrind log after running for quite a few hours on built source

It was horrifically slow, but I tried to use it as normal over a decent time
window. Hopefully this valgrind log is more useful for debugging memory use.

My experience of reading valgrind output is quite limited, but I will take a
look in a few days.

In the meantime, if you would like me to check anything else, please let me
know.

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=439769

--- Comment #12 from Antonio Rojas  ---
(In reply to Stefan from comment #10)
> > What's your mariadb client (not server) version?
> 
> Installed by zypper 

Looks like opensuse packages mariadb-connector-c separately, instead of using
the bundled one in mariadb. So you'll be affected if you update
mariadb-connector-c to 3.2.3, regardless of the mariadb package version.

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Meinhard Ritscher
https://bugs.kde.org/show_bug.cgi?id=439769

Meinhard Ritscher  changed:

   What|Removed |Added

 CC||mr203010s...@gmx.net

--- Comment #11 from Meinhard Ritscher  ---
I was hit by this bug too.

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

[kontact] [Bug 440750] Caldav and Cardav Support For Mailfence Email Service Not Working

2021-08-09 Thread postix
https://bugs.kde.org/show_bug.cgi?id=440750

postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Stefan
https://bugs.kde.org/show_bug.cgi?id=439769

--- Comment #10 from Stefan  ---
> What's your mariadb client (not server) version?

Installed by zypper 

https://software.opensuse.org/package/mariadb-client

$ zypper se -s mariadb-client
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S | Name   | Type  | Version | Arch   | Repository
--++---+-++---
i | mariadb-client | Paket | 10.5.10-1.1 | x86_64 | Haupt-Repository (OSS)
i | mariadb-client | Paket | 10.5.10-1.1 | x86_64 | openSUSE-20210604-0

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=439769

Antonio Rojas  changed:

   What|Removed |Added

 CC||s.pa...@spiekerbros.com

--- Comment #9 from Antonio Rojas  ---
*** Bug 440781 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 440781] Kmail fails to append item/ akonadi db states wrong date format

2021-08-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=440781

Antonio Rojas  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||aro...@archlinux.org

--- Comment #1 from Antonio Rojas  ---


*** This bug has been marked as a duplicate of bug 439769 ***

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=439769

--- Comment #8 from Antonio Rojas  ---
(In reply to Stefan from comment #7)
> Sorry, yes there are the same messages in
> ~/.local/share/akonadi/Akonadi.error

What's your mariadb client (not server) version?

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Stefan
https://bugs.kde.org/show_bug.cgi?id=439769

--- Comment #7 from Stefan  ---
Sorry, yes there are the same messages in ~/.local/share/akonadi/Akonadi.error

2021-08-09T13:16:05 [CRITICAL] org.kde.pim.akonadiserver:   Error code: "1292"
2021-08-09T13:16:05 [CRITICAL] org.kde.pim.akonadiserver:   DB error: 
"Incorrect datetime value: '2021-08-09T11:16:05Z' for column
`akonadi`.`pimitemtable`.`atime` at row 1"
2021-08-09T13:16:05 [CRITICAL] org.kde.pim.akonadiserver:   Error text:
"Incorrect datetime value: '2021-08-09T11:16:05Z' for column
`akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht
ausgeführt werden"
2021-08-09T13:16:05 [CRITICAL] org.kde.pim.akonadiserver:   Values: QMap((":0",
QVariant(QDateTime, QDateTime(2021-08-09 11:16:05.608 UTC Qt::UTC)))(":1",
QVariant(qlonglong, 46287)))
2021-08-09T13:16:05 [CRITICAL] org.kde.pim.akonadiserver:   Query: "UPDATE
PimItemTable SET atime = :0 WHERE ( ( PimItemTable.id = :1 ) )"
2021-08-09T13:16:05 [WARN ] org.kde.pim.akonadiserver: Unable to update item
access time
2021-08-09T13:16:05 [INFO ] org.kde.pim.akonadiserver.search: Executing search
"kontact-3240686485-SearchSession"
2021-08-09T13:16:05 [INFO ] org.kde.pim.akonadiserver.search: Search 
"kontact-3240686485-SearchSession" done (without remote search)
2021-08-09T13:16:08 [CRITICAL] org.kde.pim.akonadiserver: DATABASE ERROR:
2021-08-09T13:16:08 [CRITICAL] org.kde.pim.akonadiserver:   Error code: "1292"
2021-08-09T13:16:08 [CRITICAL] org.kde.pim.akonadiserver:   DB error: 
"Incorrect datetime value: '2021-08-09T11:16:08Z' for column
`akonadi`.`pimitemtable`.`atime` at row 1"
2021-08-09T13:16:08 [CRITICAL] org.kde.pim.akonadiserver:   Error text:
"Incorrect datetime value: '2021-08-09T11:16:08Z' for column
`akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL: Die Abfrage konnte nicht
ausgeführt werden"
2021-08-09T13:16:08 [CRITICAL] org.kde.pim.akonadiserver:   Values: QMap((":0",
QVariant(int, 1))(":1", QVariant(QString, "12512"))(":10", QVariant(qlonglong,
3))(":2", QVariant(QString, ""))(":3", QVariant(QString, ""))(":4",
QVariant(qlonglong, 284))(":5", QVariant(qlonglong, 3))(":6",
QVariant(QDateTime, QDateTime(2021-07-14 08:23:39.000 CEST
Qt::LocalTime)))(":7", QVariant(QDateTime, QDateTime(2021-08-09 11:16:08.395
UTC Qt::UTC)))(":8", QVariant(bool, false))(":9", QVariant(qlonglong, 20637)))
2021-08-09T13:16:08 [CRITICAL] org.kde.pim.akonadiserver:   Query: "UPDATE
PimItemTable SET rev = :0, remoteId = :1, remoteRevision = :2, gid = :3,
collectionId = :4, mimeTypeId = :5, datetime = :6, atime = :7, dirty = :8, size
= :9 WHERE ( id = :10 )"
2021-08-09T13:16:08 [WARN ] org.kde.pim.akonadiserver: Error during updating
record with id 3  in table "PimItemTable" "Incorrect datetime value:
'2021-08-09T11:16:08Z' for column `akonadi`.`pimitemtable`.`atime` at row 1
QMYSQL: Die Abfrage konnte nicht ausgeführt werden"
2021-08-09T13:16:08 [WARN ] org.kde.pim.akonadiserver: Error while handling
command CreateItem on connection akonadi_imap_resource_1 (0x55c06fcdd970)

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

[Akonadi] [Bug 440781] New: Kmail fails to append item/ akonadi db states wrong date format

2021-08-09 Thread Frits Spieker
https://bugs.kde.org/show_bug.cgi?id=440781

Bug ID: 440781
   Summary: Kmail fails to append item/ akonadi db states wrong
date format
   Product: Akonadi
   Version: 5.17.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-bugs@kde.org
  Reporter: s.pa...@spiekerbros.com
  Target Milestone: ---

SUMMARY
Since last update Kmail/ Akonadi fails to get new email from IMAP server. Kmail
reports "failed to append item" when synchronising mailbox. The Akonadi error
log states: 
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver: DATABASE ERROR:
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver:   Error code: "1292"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver:   DB error: 
"Incorrect datetime value: '2021-08-09T12:00:17Z' for column
`akonadi`.`pimitemtable`.`datetime` at row 1"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver:   Error text:
"Incorrect datetime value: '2021-08-09T12:00:17Z' for column
`akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Unable to execute query"
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver:   Values: QMap((":0",
QVariant(int, 0))(":1", QVariant(QString, "6773"))(":2", QVariant(QString,
""))(":3", QVariant(QString, ""))(":4", QVariant(qlonglong, 21))(":5",
QVariant(qlonglong, 3))(":6", QVariant(QDateTime, QDateTime(2021-08-09
12:00:17.471 UTC Qt::UTC)))(":7", QVariant(QDateTime, QDateTime(2021-08-09
12:00:17.471 UTC Qt::UTC)))(":8", QVariant(bool, false))(":9",
QVariant(qlonglong, 2491777)))
2021-08-09T14:00:17 [CRITICAL] org.kde.pim.akonadiserver:   Query: "INSERT INTO
PimItemTable (rev, remoteId, remoteRevision, gid, collectionId, mimeTypeId,
datetime, atime, dirty, size) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9)"
2021-08-09T14:00:17 [WARN ] org.kde.pim.akonadiserver: Error during insertion
into table "PimItemTable" "Incorrect datetime value: '2021-08-09T12:00:17Z' for
column `akonadi`.`pimitemtable`.`datetime` at row 1 QMYSQL: Unable to execute
query"
2021-08-09T14:00:17 [WARN ] org.kde.pim.akonadiserver: Error while handling
command CreateItem on connection akonadi_imap_resource_0 (0x559fee8e4a30)
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"MessageViewerMonitor - 94908118964128" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"MessageListTagMonitor - 94908119944352" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber "KMail Kernel
ETM - 94908118071664" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"SpecialCollectionsMonitor - 94908118206576" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"FilterManagerTagMonitor - 94908124039120" disconnected
2021-08-09T14:00:26 [INFO ] org.kde.pim.akonadiserver: Subscriber
"TagActionManagerMonitor - 94908124186832" disconnected


This even happens with a completely new user set up. The directory structure as
present on the IMAP server is correctly created in KMAIL upon setup, but
retrieving messages fails with the above error. 

STEPS TO REPRODUCE
1. Try to get new mail from imap server


OBSERVED RESULT
KMAIL states "failed to append item" and does not show emails coming in upon
sync; as a result all email folders are empty and stay empty when setting up as
a new user.

EXPECTED RESULT
Emails actually show up in Kmail

I´ĺl happily create any logfile or anything else you need to squash this ugly
bug

OS: OpenSuse Tumbleweed
KDE:5.22.4
KDE Framework: 5.84.0

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=439769

--- Comment #6 from Antonio Rojas  ---
(In reply to Stefan from comment #5)
> Is it sure that this issue is related to MariaDB 1.6?
> 
> mysql --socket=/run/user/1000/akonadi/mysql.socket -e "SELECT @@version;"   
> 
> +-+
> | @@version   |
> +-+
> | 10.5.10-MariaDB |
> +-+
> 
> Is this the current version of mariaDB what is used by akonadi?
> 
> I am running into the same today and have no idea whats changed since
> yesterday

What do you mean by "the same"? The same symptoms doesn't mean it's the same
issue. If you don't have the "Incorrect datetime value" in akonadi's output
then your problem is a different one.

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Stefan
https://bugs.kde.org/show_bug.cgi?id=439769

Stefan  changed:

   What|Removed |Added

 CC||menis...@gmx.net

--- Comment #5 from Stefan  ---
Is it sure that this issue is related to MariaDB 1.6?

mysql --socket=/run/user/1000/akonadi/mysql.socket -e "SELECT @@version;"   
+-+
| @@version   |
+-+
| 10.5.10-MariaDB |
+-+

Is this the current version of mariaDB what is used by akonadi?

I am running into the same today and have no idea whats changed since yesterday

I tried Ricados suggestion with 

"innodb_force_recovery = 2"

but after restarting akonadi, the same messages appear again and i can not send
nor receives mails.


Operating System: openSUSE Tumbleweed 20210806
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Kernel Version: 5.13.6-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000

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

[kmail2] [Bug 416700] Folder list: the Size" column has too large width, unchangeable, showing size numbers out of view

2021-08-09 Thread Friedrich W. H. Kossebau
https://bugs.kde.org/show_bug.cgi?id=416700

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Friedrich W. H. Kossebau  ---
I looked around in the respective codebases, but could not find a reason why
such a large minimum column size was calculated, also could not reproduce in a
separate account.

I then removed the State entry from the [CollectionFolderView] entry in
kmail2rc, restarted kmail, and the issue was gone.

So seems Qt had some internal bad state encoded in that data blob which
enforced the insane large column width, possibly some incompatibility acros
versions.
Sadly I lost the value of the State entry, so also cannot try to investigate
where Qt might need fixing.

Thus just closing now, as it seems no bug in KDE code :)

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

[Akonadi] [Bug 440777] New: Akonadi crashed when reading IMAP inbox.

2021-08-09 Thread Vladimir Timonin
https://bugs.kde.org/show_bug.cgi?id=440777

Bug ID: 440777
   Summary: Akonadi crashed when reading IMAP inbox.
   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: timo...@mindspring.com
  Target Milestone: ---

Application: akonadiserver (5.17.3 (21.04.3))

Qt Version: 5.15.2
Frameworks Version: 5.84.0
Operating System: Linux 5.13.6-1-default x86_64
Windowing System: X11
Drkonqi Version: 5.22.4
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

Started Kmail - it didn't retreve latest emails. Pressed "Check mail", after
some activity got notification "akonadi crashed".
Repeateable, either after akonadi restart or computer reboot.
Account IMAP. There are several filters on Inbox, deleted all filters, same
crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fd278130840
(LWP 1837))]
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#7  0x7fd27a5c9864 in __GI_abort () at abort.c:79
#8  0x7fd27a622b17 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7fd27a733826 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#9  0x7fd27a62a73c in malloc_printerr (str=str@entry=0x7fd27a7365a0
"tcache_thread_shutdown(): unaligned tcache chunk detected") at malloc.c:5626
#10 0x7fd27a62f91c in tcache_thread_shutdown () at malloc.c:3131
#11 __malloc_arena_thread_freeres () at
/usr/src/debug/glibc-2.33-9.1.x86_64/malloc/arena.c:1001
#12 0x7fd27a632ea5 in __libc_thread_freeres () at thread-freeres.c:42
#13 0x7fd279cca27f in start_thread (arg=0x7fd22effd640) at
pthread_create.c:495
#14 0x7fd27a6a32b3 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7fd249ffb640 (LWP 2084) "0x55d075e6aee0-"):
#1  0x7fd278eb7a35 in g_source_iter_next (iter=iter@entry=0x7fd249ffa650,
source=source@entry=0x7fd249ffa648) at ../glib/gmain.c:1063
#2  0x7fd278eb94db in g_main_context_check
(context=context@entry=0x7fd234000c20, max_priority=2147483647,
fds=fds@entry=0x7fd234005240, n_fds=1241491024, n_fds@entry=1) at
../glib/gmain.c:3931
#3  0x7fd278eb9ad5 in g_main_context_iterate
(context=context@entry=0x7fd234000c20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4128
#4  0x7fd278eb9c4f in g_main_context_iteration (context=0x7fd234000c20,
may_block=1) at ../glib/gmain.c:4196
#5  0x7fd27acd7ec6 in QEventDispatcherGlib::processEvents
(this=0x7fd234000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fd27ac7f36b in QEventLoop::exec (this=this@entry=0x7fd249ffa850,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#7  0x55d074f8ef88 in Akonadi::Server::Connection::handleIncomingData
(this=0x55d075e6aee0) at /usr/include/qt5/QtCore/qflags.h:121
#8  0x7fd27acacf5e in QObject::event (this=0x55d075e6aee0,
e=0x7fd234004780) at kernel/qobject.cpp:1314
#9  0x7fd27ac8093f in doNotify (event=0x7fd234004780,
receiver=0x55d075e6aee0) at kernel/qcoreapplication.cpp:1154
#10 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1140
#11 QCoreApplication::notifyInternal2 (receiver=0x55d075e6aee0,
event=0x7fd234004780) at kernel/qcoreapplication.cpp:1064
#12 0x7fd27ac839b7 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55d075e6b090) at
kernel/qcoreapplication.cpp:1821
#13 0x7fd27acd87d3 in postEventSourceDispatch (s=s@entry=0x7fd234004fe0) at
kernel/qeventdispatcher_glib.cpp:277
#14 0x7fd278eb980f in g_main_dispatch (context=0x7fd234000c20) at
../glib/gmain.c:3337
#15 g_main_context_dispatch (context=0x7fd234000c20) at ../glib/gmain.c:4055
#16 0x7fd278eb9b98 in g_main_context_iterate
(context=context@entry=0x7fd234000c20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131
#17 0x7fd278eb9c4f in g_main_context_iteration (context=0x7fd234000c20,
may_block=1) at ../glib/gmain.c:4196
#18 0x7fd27acd7e54 in QEventDispatcherGlib::processEvents
(this=0x7fd234000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x7fd27ac7f36b in QEventLoop::exec (this=this@entry=0x7fd249ffacc0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x7fd27aa9ac9e in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x7fd27aa9bdd1 in QThreadPrivate::start (arg=0x55d075e6b070) at
thread/qthread_unix.cpp:329
#22 0x7fd279cca259 in start_thread (arg=0x7fd249ffb640) at
pthread_create.c:481

[Akonadi] [Bug 440772] Sending mail is not working anymore, because of database error code 1292.

2021-08-09 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=440772

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Christophe Giboudeaux  ---


*** This bug has been marked as a duplicate of bug 439769 ***

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

[Akonadi] [Bug 439769] Akonadi fails with Mariadb 10.6.3

2021-08-09 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=439769

Christophe Giboudeaux  changed:

   What|Removed |Added

 CC||fab...@web2.0-apps.de

--- Comment #4 from Christophe Giboudeaux  ---
*** Bug 440772 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 440772] New: Sending mail is not working anymore, because of database error code 1292.

2021-08-09 Thread Fabian
https://bugs.kde.org/show_bug.cgi?id=440772

Bug ID: 440772
   Summary: Sending mail is not working anymore, because of
database error code 1292.
   Product: Akonadi
   Version: 5.17.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: fab...@web2.0-apps.de
  Target Milestone: ---

Created attachment 140598
  --> https://bugs.kde.org/attachment.cgi?id=140598=edit
akonadictl output

SUMMARY
Sending mail is not working anymore, because of database error code 1292.


Sending mail was working before last update.

STEPS TO REPRODUCE
1. Write a new mail
2. Hit send

OBSERVED RESULT
German error message "Es gab Probleme beim Einreihen der Nachricht in die
Sende-Warteschlange: Failed to append item".

EXPECTED RESULT
Mail is sent.

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

ADDITIONAL INFORMATION

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