[Akonadi] [Bug 338571] Performance Regression: Folder synchronisation in 4.14 very slow compared to kMail from KDE 4.13.x

2014-11-17 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=338571

Marco Clemencic marco.clemen...@gmail.com changed:

   What|Removed |Added

 CC||marco.clemen...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 285676] akonadi blocks kmail because of searching for bogus emails

2011-11-29 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=285676





--- Comment #19 from Marco Clemencic marco clemencic gmail com  2011-11-29 
15:34:43 ---
the suggestion of comment #17 works, but it is a workaround and not a fix. BTW,
that's what I did to be able to work.

To answer to comment #18:
1. my understanding of the difference is that in one case the top level
directory can contain mails while the other not: 'kmail folders' (broken one)
is a directory containing MailDirs, while 'local folders' (working one) is a
MailDir... so it can contain nested MailDirs.
2. after the migration you get the broken one.

-- 
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

[Bug 285676] akonadi blocks kmail because of searching for bogus emails

2011-11-12 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=285676





--- Comment #9 from Marco Clemencic marco clemencic gmail com  2011-11-12 
10:48:40 ---
Ok, I managed to reproduce the problem.

From a fresh account, start Kontact (KMail2 should be enough).
Prepare a directory with this kind of substructure:

testing
└── fldr1
├── cur
├── new
└── tmp

From the KMail settings create a KMail Maildir account making it pointing to
the directory testing.

Create a new mail and save it as draft.

Copy the file in the new subdirectory of the drafts directory (somewhere in
~/.local/share/.local-mail.directory/) to the directory testing/fldr1/new.

From the KMail interface select the folder fldr1 and synchronize it (F5 or
right-click and synchronize). 

Nothing seems to happen, but go to the KMail settings, then accounts, and you
will see that the testing account got stuck in the synchronization and is
unusable.


The Maildir type of account (not KMail Maildir) doesn't seem to have the
problem. If you try the same procedure using a Maildir account, it behaves
correctly.

Cheers
Marco

-- 
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

[Bug 285676] akonadi blocks kmail because of searching for bogus emails

2011-11-11 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=285676


Marco Clemencic marco.clemen...@gmail.com changed:

   What|Removed |Added

 CC||marco.clemen...@gmail.com




--- Comment #7 from Marco Clemencic marco clemencic gmail com  2011-11-11 
11:45:29 ---
Same for me.

KMail is unusable: my the outbox folder is stuck because of that, so I have to
use another mail client to be able to send emails.

-- 
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

[Bug 285676] akonadi blocks kmail because of searching for bogus emails

2011-11-11 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=285676





--- Comment #8 from Marco Clemencic marco clemencic gmail com  2011-11-11 
18:31:21 ---
I managed to recover my outbox folder.

What probably happened is that the Akonadi database and the maildir directory
got desynchronized after a crash of the system (I have troubles with the
suspend).

In this situation the akonadi_mixedmaildir_resource seems to get stuck trying
to synchronize.

To recover the outbox I had to remove the files that were in the 'new'
directory and remove the pim items from the database by hand.

If I manage to reproduce the problem in a simple case I'll post it here.

Cheers
Marco

-- 
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

[Bug 282889] New: Kontact (KMail) crash with proxy

2011-09-27 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=282889

   Summary: Kontact (KMail) crash with proxy
   Product: kontact
   Version: 4.4.10
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: marco.clemen...@gmail.com


Application: kontact (4.4.10)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic x86_64
Distribution: Ubuntu 11.04

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

I clicked the button to check for new mails.

- Custom settings of the application:

I have enabled a proxy server in the system configuration using a .pac file.
I might be that the proxy server is not well configured, but it works for http
and https.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fed4841c7a0 (LWP 2698))]

Thread 3 (Thread 0x7fed2773b700 (LWP 2917)):
#0  0x7fed45877f03 in __poll (fds=value optimized out, nfds=value
optimized out, timeout=value optimized out) at
../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7fed3f2ed104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fed3f2ed9f2 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed28852c44 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7fed3f3143e4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fed3f7b8d8c in start_thread (arg=0x7fed2773b700) at
pthread_create.c:304
#6  0x7fed4588504d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x in ?? ()

Thread 2 (Thread 0x7fed27f3c700 (LWP 3005)):
#0  0x7fed45877f03 in __poll (fds=value optimized out, nfds=value
optimized out, timeout=value optimized out) at
../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7fed3f2ed104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fed3f2ed639 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed45fbf446 in QEventDispatcherGlib::processEvents (this=0x4edeec0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7fed45f93882 in QEventLoop::processEvents (this=value optimized
out, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fed45f93abc in QEventLoop::exec (this=0x7fed27f3bdb0, flags=...) at
kernel/qeventloop.cpp:201
#6  0x7fed45eaa924 in QThread::exec (this=value optimized out) at
thread/qthread.cpp:492
#7  0x7fed45f75c2f in QInotifyFileSystemWatcherEngine::run (this=0x52e25e0)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x7fed45ead175 in QThreadPrivate::start (arg=0x52e25e0) at
thread/qthread_unix.cpp:320
#9  0x7fed3f7b8d8c in start_thread (arg=0x7fed27f3c700) at
pthread_create.c:304
#10 0x7fed4588504d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x in ?? ()

Thread 1 (Thread 0x7fed4841c7a0 (LWP 2698)):
[KCrash Handler]
#6  detach (this=0x0, job=0x5691b10) at /usr/include/qt4/QtCore/qhash.h:299
#7  operator[] (this=0x0, job=0x5691b10) at /usr/include/qt4/QtCore/qhash.h:738
#8  KIO::ProtoQueue::removeJob (this=0x0, job=0x5691b10) at
../../kio/kio/scheduler.cpp:483
#9  0x7fed37a7 in KIO::SchedulerPrivate::assignJobToSlave (this=value
optimized out, slave=0x4d20810, job=0x5691b10) at
../../kio/kio/scheduler.cpp:1273
#10 0x7fed38b2 in KIO::Scheduler::assignJobToSlave (slave=0x4d20810,
job=0x5691b10) at ../../kio/kio/scheduler.cpp:841
#11 0x7fed2b690877 in KMail::PopAccount::connectJob (this=value optimized
out) at ../../kmail/popaccount.cpp:279
#12 0x7fed2b692f43 in KMail::PopAccount::startJob (this=0x3b2bf00) at
../../kmail/popaccount.cpp:414
#13 0x7fed2b699a19 in KMail::PopAccount::processNewMail (this=0x3b2bf00,
_interactive=true) at ../../kmail/popaccount.cpp:196
#14 0x7fed2b5de9c4 in KMail::AccountManager::processNextCheck
(this=0x3267ba0, _newMail=value optimized out) at
../../kmail/accountmanager.cpp:231
#15 0x7fed2b5df30a in KMail::AccountManager::singleCheckMail
(this=0x3267ba0, account=0x3b2bf00, interactive=value optimized out) at
../../kmail/accountmanager.cpp:157
#16 0x7fed2b5e06a2 in KMail::AccountManager::checkMail (this=0x3267ba0,
_interactive=true) at ../../kmail/accountmanager.cpp:353
#17 0x7fed2b77b1d2 in KMMainWidget::qt_metacall (this=0x3b53300,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fff8e6f4560) at
./kmmainwidget.moc:363
#18 0x7fed45fa95f8 in QMetaObject::activate (sender=0x3cc9f70, m=value
optimized out, local_signal_index=value optimized out, argv=0x7fff8e6f4560)
at kernel/qobject.cpp:3287
#19 0x7fed4694a122 in QAction::triggered (this=value optimized out,
_t1=false) at .moc/release-shared/moc_qaction.cpp:263
#20 0x7fed4694a30f in QAction::activate (this=0x3cc9f70, event=value

[Bug 206221] New: kontact (kmail) crashes after an imap connection is lost

2009-09-04 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=206221

   Summary: kontact (kmail) crashes after an imap connection is
lost
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: marco.clemen...@gmail.com


Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
After the connection is lost (for any reason) a notification message is display
and, when I close it, kontact crashes.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KIO::Slave::deref (this=0x30c5a20) at
/build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:242
#6  0x7fac578cdf6f in KIO::Slave::gotInput (this=0x30c5a20) at
/build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:335
#7  0x7fac578d01c8 in KIO::Slave::qt_metacall (this=0x30c5a20,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff62e79010) at
/build/buildd/kde4libs-4.3.1/obj-x86_64-linux-gnu/kio/slave.moc:76
#8  0x7fac553cbea2 in QMetaObject::activate (sender=0x30d4a30,
from_signal_index=value optimized out, to_signal_index=4, argv=0x5e6fb70) at
kernel/qobject.cpp:3113
#9  0x7fac577eadb1 in KIO::ConnectionPrivate::dequeue (this=0x30e9310) at
/build/buildd/kde4libs-4.3.1/kio/kio/connection.cpp:82
#10 0x7fac577eb20a in KIO::Connection::qt_metacall (this=0x30d4a30,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x322ca40)
at /build/buildd/kde4libs-4.3.1/obj-x86_64-linux-gnu/kio/connection.moc:73
#11 0x7fac553c65d8 in QObject::event (this=0x30d4a30, e=0x31fd5b0) at
kernel/qobject.cpp:
#12 0x7fac55f36f4d in QApplicationPrivate::notify_helper (this=0x155c020,
receiver=0x30d4a30, e=0x31fd5b0) at kernel/qapplication.cpp:4056
#13 0x7fac55f3f18a in QApplication::notify (this=0x7fff62e7b830,
receiver=0x30d4a30, e=0x31fd5b0) at kernel/qapplication.cpp:4021
#14 0x7fac5733bdeb in KApplication::notify (this=0x7fff62e7b830,
receiver=0x30d4a30, event=0x31fd5b0) at
/build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302
#15 0x7fac553b66ac in QCoreApplication::notifyInternal
(this=0x7fff62e7b830, receiver=0x30d4a30, event=0x31fd5b0) at
kernel/qcoreapplication.cpp:610
#16 0x7fac553b731a in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x152f850) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0x7fac553dfe03 in postEventSourceDispatch (s=value optimized out) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#18 0x7fac4eb0720a in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#19 0x7fac4eb0a8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x7fac4eb0aa7c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#21 0x7fac553dfa8f in QEventDispatcherGlib::processEvents (this=0x152f0a0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327
#22 0x7fac55fcfbdf in QGuiEventDispatcherGlib::processEvents (this=0x20,
flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x7fac553b4f42 in QEventLoop::processEvents (this=value optimized
out, flags={i = 1659345296}) at kernel/qeventloop.cpp:149
#24 0x7fac553b5314 in QEventLoop::exec (this=0x7fff62e799d0, flags={i =
1659345392}) at kernel/qeventloop.cpp:201
#25 0x7fac563cde3e in QDialog::exec (this=0x5911c40) at
dialogs/qdialog.cpp:498
#26 0x7fac572c1862 in KMessageBox::createKMessageBox (dialog=0x5911c40,
icon=value optimized out, te...@0x7fff62e7a340, strli...@0x7fff62e7a120,
a...@0x7fff62e7a020, 
checkboxReturn=0x7fff62e7a09f, options={i = 1659346784},
detai...@0x7fff62e7a010, notifyType=QMessageBox::Information) at
/build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:331
#27 0x7fac572c29f7 in KMessageBox::createKMessageBox (dialog=0x5911c40,
icon=QMessageBox::Information, te...@0x7fff62e7a340, strli...@0x7fff62e7a120,
a...@0x7fff62e7a020, 
checkboxReturn=0x7fff62e7a09f, options={i = 1659347056},
detai...@0x7fff62e7a010) at
/build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:151
#28 0x7fac572c4fa7 in KMessageBox::informationListWId (parent_id=0,
te...@0x7fff62e7a340, strli...@0x7fff62e7a120, capti...@0x7fff62e7a300,
dontshowagainna...@0x7fff62e7a2d0, options=
  {i = 1659347168}) at
/build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:1008
#29 0x7fac572c5103 in KMessageBox::informationList (parent=0x0,
te...@0x7fff62e7a340, strli...@0x7fff62e7a120, capti...@0x7fff62e7a300,
dontshowagainna...@0x7fff62e7a2d0, 
options=value optimized out) at
/build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:977
#30 0x7fac572c5151 in

[Bug 206221] kontact (kmail) crashes after an imap connection is lost

2009-09-04 Thread Marco Clemencic 
https://bugs.kde.org/show_bug.cgi?id=206221


Marco Clemencic marco.clemen...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE




--- Comment #1 from Marco Clemencic marco clemencic gmail com  2009-09-04 
11:01:22 ---


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

-- 
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