[Akonadi] [Bug 428536] org.kde.pim.maildispatcher: Item does not have the required attribute Address.

2021-04-04 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=428536

Matthew Dawson  changed:

   What|Removed |Added

 CC||matt...@mjdsystems.ca

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

[kontact] [Bug 433610] KDE PIM memory/CPU leak

2021-03-14 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=433610

Matthew Dawson  changed:

   What|Removed |Added

 CC||matt...@mjdsystems.ca

--- Comment #3 from Matthew Dawson  ---
This issue is likely caused by an downstream issue in Gentoo's qtwebengine
package (see here: https://bugs.gentoo.org/773919 ).  Can you try taking the
steps outlined in this comment: https://bugs.gentoo.org/773919#c21 and see if
that resolves your problem?

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

[Akonadi] [Bug 402673] New: Akonadi server incompatible with latest Mysql defaults (NO_ZERO_DATE enabled by default) when using database created using older akonadi versions

2018-12-28 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=402673

Bug ID: 402673
   Summary: Akonadi server incompatible with latest Mysql defaults
(NO_ZERO_DATE enabled by default) when using database
created using older akonadi versions
   Product: Akonadi
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: matt...@mjdsystems.ca
  Target Milestone: ---

After updating my system to the latest packages on Gentoo, akonadi (upgrading
from 18.08.2 to 18.12.0) no longer starts.  Enabling verbose output gives the
following text:

org.kde.pim.akonadiserver: Updating indexes
org.kde.pim.akonadiserver: "CREATE  INDEX PimItemTable_mimeTypeIndex ON
PimItemTable (mimeTypeId)"
org.kde.pim.akonadiserver: Updating index failed:  
Sql error: Invalid default value for 'atime' QMYSQL: Unable to execute query
Query: CREATE  INDEX PimItemTable_mimeTypeIndex ON PimItemTable (mimeTypeId)

It appears mysql 5.7 by defaults enables NO_ZERO_DATE.  When attempting to
update the database, mysql refuses to touch the affected table as the table
definition is invalid.  I assume I didn't have issues on the older Akonadi
versions as I only got upgraded to 5.7 in Novemeber, and there were no
interesting updates at that time to the PimItemTable.  As the default wasn't
used during insert, Akonadi was able to operate normally.

It seems to the best option is to add a migration to change all TIMESTAMP
columns to have an appropriate default, or disable NO_ZERO_DATE in the mysql
configuration explicitly.  I'd be happy to create/contribute a patch for either
option (I have a backup of my database to test against!).

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

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

2016-09-05 Thread Matthew Dawson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364342

Matthew Dawson <matt...@mjdsystems.ca> changed:

   What|Removed |Added

 CC||matt...@mjdsystems.ca

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


[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

2016-09-02 Thread Matthew Dawson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364342

Matthew Dawson <matt...@mjdsystems.ca> changed:

   What|Removed |Added

 CC||bernhard+...@scheirle.de

--- Comment #13 from Matthew Dawson <matt...@mjdsystems.ca> ---
*** Bug 368139 has been marked as a duplicate of this bug. ***

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


[kleopatra] [Bug 343264] New: Kleopatra randomly crashes in the background, potentially while dealing with signed emails

2015-01-24 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=343264

Bug ID: 343264
   Summary: Kleopatra randomly crashes in the background,
potentially while dealing with signed emails
   Product: kleopatra
   Version: 2.2.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: matt...@mjdsystems.ca
CC: m...@kde.org

-- Information about the crash:
While I was working on my computer, Kelopatra randomly crashed in the
background (I wasn't even aware it was running at the time).  I think I may
have been looking at some signed emails around that time.

I double checked the generated binary, all the null checks are present.  It did
fail copying the fpr member of subkeys, and the register holding the pointer
for subkeys had an address of 0x90, which seems weird to me.

I have a core dumped if you have something more you'd like me to poke into, and
I can keep the debug symbols/source code around for a couple of days.  I lurk
in #kde-devel as MJD, feel free to ping me.

-- Backtrace:
Application: Kleopatra (kleopatra), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f67cfca9800 (LWP 14228))]

Thread 3 (Thread 0x7f67b7d66700 (LWP 14286)):
#0  __GI___pthread_mutex_lock (mutex=0x7f67ba60) at
../nptl/pthread_mutex_lock.c:70
#1  0x7f67c6e5ec31 in g_mutex_lock (mutex=mutex@entry=0x7f67b9a0) at
/usr/src/debug/dev-libs/glib-2.40.2/glib-2.40.2/glib/gthread-posix.c:209
#2  0x7f67c6e1868b in g_main_context_check
(context=context@entry=0x7f67b9a0, max_priority=2147483647,
fds=fds@entry=0x7f67b00034d0, n_fds=n_fds@entry=1) at
/usr/src/debug/dev-libs/glib-2.40.2/glib-2.40.2/glib/gmain.c:3577
#3  0x7f67c6e18c23 in g_main_context_iterate
(context=context@entry=0x7f67b9a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=optimized out) at
/usr/src/debug/dev-libs/glib-2.40.2/glib-2.40.2/glib/gmain.c:3731
#4  0x7f67c6e18dac in g_main_context_iteration (context=0x7f67b9a0,
may_block=1) at
/usr/src/debug/dev-libs/glib-2.40.2/glib-2.40.2/glib/gmain.c:3795
#5  0x7f67cd344356 in QEventDispatcherGlib::processEvents
(this=0x7f67b8c0, flags=...) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/kernel/qeventdispatcher_glib.cpp:452
#6  0x7f67cd3127c1 in QEventLoop::processEvents
(this=this@entry=0x7f67b7d65d80, flags=...) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/kernel/qeventloop.cpp:149
#7  0x7f67cd312b65 in QEventLoop::exec (this=this@entry=0x7f67b7d65d80,
flags=...) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/kernel/qeventloop.cpp:204
#8  0x7f67cd201129 in QThread::exec (this=this@entry=0x28b26f0) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread.cpp:538
#9  0x7f67cd2f2893 in QInotifyFileSystemWatcherEngine::run (this=0x28b26f0)
at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f67cd203acf in QThreadPrivate::start (arg=0x28b26f0) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread_unix.cpp:349
#11 0x7f67ced18333 in start_thread (arg=0x7f67b7d66700) at
pthread_create.c:309
#12 0x7f67cb96d8ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f67b7565700 (LWP 14831)):
#0  pthread_cond_timedwait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f67cd20403c in wait (time=2000, this=0x28efe40) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0x28efb98,
mutex=mutex@entry=0x28efb90, time=time@entry=2000) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qwaitcondition_unix.cpp:158
#3  0x005f7034 in (anonymous namespace)::ReaderStatusThread::run
(this=0x28efb80) at
/usr/src/debug/kde-base/kleopatra-4.14.3/kleopatra-4.14.3/kleopatra/smartcard/readerstatus.cpp:543
#4  0x7f67cd203acf in QThreadPrivate::start (arg=0x28efb80) at
/usr/src/debug/dev-qt/qtcore-4.8.6-r1/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread_unix.cpp:349
#5  0x7f67ced18333 in start_thread (arg=0x7f67b7565700) at
pthread_create.c:309
#6  0x7f67cb96d8ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f67cfca9800 (LWP 14228)):
[KCrash Handler]
#6  0x7f67cf59e131 in GpgME::Key::primaryFingerprint
(this=this@entry=0x2ab3e60) at

[Bug 208778] KMail crash while reading email.

2011-12-26 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=208778


Matthew Dawson matt...@mjdsystems.ca changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WORKSFORME




--- Comment #5 from Matthew Dawson matthew mjdsystems ca  2011-12-27 04:10:02 
---
Since I've yet to reproduce this on any recent kmail version, and with kmail 2
completely redoing the whole stack (and probably fixing this bug), I'm marking
it works for me for now.  If anyone else still has this issue on a recent
version of kmail, feel free to reopen this bug.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs