[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"

2023-10-07 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=473897

--- Comment #31 from Erasmo Caponio  ---
(In reply to Cyrille Dunant from comment #29)
> I have managed to add the agent by creating it in the console, then shutting
> down akonadi, then editing the agent config file to add the network section
> which was missing:
> 
> [network]
> Authentication=9
> UserName=XXX
> 
> I am uncertain the username is required. But the [network] section
> definitely is, and I don't know why it's not created.

Thanks, for the workroit seems to work now (In reply to caxilbund from comment
#28)
> I was able to set it up and configure it within korganizer. However, it came
> up with "the configured account doesn't exist" error message after I had
> supposedly configured it and the calendar did not appear. I hit the reset
> button in the settings calendar dialog, the error message disappeared, the
> ready message appeared, and lo and behold the calendar entries actually
> appeared in the user interface.

Thanks, I had the same problem; it seems to work now by your workaround. Let's
see if it works stably finally ... Anyway, thanks to KDE developers!!

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

[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"

2023-09-20 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=473897

--- Comment #24 from Erasmo Caponio  ---
(In reply to Erasmo Caponio from comment #23)
> (In reply to Cyrille Dunant from comment #22)
> > In 23.08.1, still occurs -- in fact the dialog to configure the resource
> > doesn't even show up any more, which it did previously.
> 
> I confirm this on Manjaro with KDE Plasma 5.27.8

and Kontact 23.08.1

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

[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"

2023-09-20 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=473897

Erasmo Caponio  changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

--- Comment #23 from Erasmo Caponio  ---
(In reply to Cyrille Dunant from comment #22)
> In 23.08.1, still occurs -- in fact the dialog to configure the resource
> doesn't even show up any more, which it did previously.

I confirm this on Manjaro with KDE Plasma 5.27.8

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

[Akonadi] [Bug 444288] Akonadi "losing connection" to Google Calendars after some uptime / waking from sleep until either akonadictrl restart is used or Google Groupware is restarted in Korganizer.

2022-01-21 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=444288

Erasmo Caponio  changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

--- Comment #8 from Erasmo Caponio  ---
(In reply to Alex Dewar from comment #6)
> I was experiencing this bug and now things seem to have got worse --
> restarting Google Groupware (or the whole of the akonadi service) doesn't
> fix it, so I can't view my Google Calendar at all :-(

I confirm this

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

[kontact] [Bug 443581] After last update, google contacts don't show in kontact anymore (nor calendars)

2021-10-25 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=443581

--- Comment #8 from Erasmo Caponio  ---
(In reply to Erasmo Caponio from comment #7)
> (In reply to Kishore Gopalakrishnan from comment #4)
> > Related to bug 439285?
> 
> After reviewing comments for bug 439285, I would say yes, it's the same bug


In particular this comment explains well what the bug is 
https://bugs.kde.org/show_bug.cgi?id=439285#c15

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

[kontact] [Bug 443581] After last update, google contacts don't show in kontact anymore (nor calendars)

2021-10-25 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=443581

--- Comment #7 from Erasmo Caponio  ---
(In reply to Kishore Gopalakrishnan from comment #4)
> Related to bug 439285?

After reviewing comments for bug 439285, I would say yes, it's the same bug

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

2021-10-25 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=439285

Erasmo Caponio  changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

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

[kontact] [Bug 443581] After last update, google contacts don't show in kontact anymore (nor calendars)

2021-10-25 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=443581

Erasmo Caponio  changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

--- Comment #6 from Erasmo Caponio  ---
(In reply to Martin Tlustos from comment #3)
> Adding a calendar entry/task works and gets synchronized, so it only happens
> to contacts.

I can confirm this bug for google contacts in Kontact under Manjaro  too

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

[kontact] [Bug 403109] kontact chashes when it is closed

2021-01-11 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=403109

Erasmo Caponio  changed:

   What|Removed |Added

Version|unspecified |5.16.1
 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED
   Platform|Neon Packages   |Manjaro

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2020-08-16 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=411093

--- Comment #32 from Erasmo Caponio  ---
This bug seems solved in kde neon based on Ubuntu 20.04 (at least on my
upgraded system). Removing and reinstalling apparmor and snapd may help (Anyway
I still have snapd removed)

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2019-10-26 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=411093

--- Comment #9 from Erasmo Caponio  ---
*** Bug 411417 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 411417] akonadi server won't start

2019-10-26 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=411417

Erasmo Caponio  changed:

   What|Removed |Added

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

--- Comment #1 from Erasmo Caponio  ---


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

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2019-10-26 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=411093

Erasmo Caponio  changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

--- Comment #8 from Erasmo Caponio  ---
Same problem here. I am running kde neon user edition, plasma version 5.17.1

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

[Akonadi] [Bug 411417] New: akonadi server won't start

2019-08-29 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=411417

Bug ID: 411417
   Summary: akonadi server won't start
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: erasmocapo...@tiscali.it
  Target Milestone: ---

SUMMARY
akonadi server won't start after last KDE neon (user version) upgrade

STEPS TO REPRODUCE
1. open kontact

OBSERVED RESULT
akonadi server does not start

EXPECTED RESULT
akonadi server starts

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.16
(available in About System)
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3


ADDITIONAL INFORMATION

A workaround  that I have found here
https://forum.kde.org/viewtopic.php?f=215=162053:
$ sudo service apparmor teardown
$ sudo service apparmor start

but afer rebooting the system akonadi still does not start after starting
kontact

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

[kontact] [Bug 403109] New: kontact chashes when it is closed

2019-01-11 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=403109

Bug ID: 403109
   Summary: kontact chashes when it is closed
   Product: kontact
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: erasmocapo...@tiscali.it
  Target Milestone: ---

Application: kontact (5.10.0)

Qt Version: 5.11.2
Frameworks Version: 5.53.0
Operating System: Linux 4.15.0-43-generic x86_64
Distribution: KDE neon User Edition 5.14

-- Information about the crash:
- What I was doing when the application crashed:
I closed the application and then the system message about crashing of the same
application appeared

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f546795ebc0 (LWP 1448))]

Thread 30 (Thread 0x7f534964d700 (LWP 11765)):
#0  0x7f545fc0eed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f534964c740, expected=0, futex_word=0x7f534964c928) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f545fc0eed9 in __pthread_cond_wait_common (abstime=0x7f534964c7e0,
mutex=0x7f534964c8d8, cond=0x7f534964c900) at pthread_cond_wait.c:533
#2  0x7f545fc0eed9 in __pthread_cond_timedwait (cond=0x7f534964c900,
mutex=0x7f534964c8d8, abstime=0x7f534964c7e0) at pthread_cond_wait.c:667
#3  0x7f54551dc917 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f54551debf7 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f54551dece2 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f54551e3d61 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f54551e50ff in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f54551edff1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f545fc086db in start_thread (arg=0x7f534964d700) at
pthread_create.c:463
#10 0x7f546430388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7f5324d72700 (LWP 11758)):
#0  0x7f545fc0eed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5324d71740, expected=0, futex_word=0x7f5324d71928) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f545fc0eed9 in __pthread_cond_wait_common (abstime=0x7f5324d717e0,
mutex=0x7f5324d718d8, cond=0x7f5324d71900) at pthread_cond_wait.c:533
#2  0x7f545fc0eed9 in __pthread_cond_timedwait (cond=0x7f5324d71900,
mutex=0x7f5324d718d8, abstime=0x7f5324d717e0) at pthread_cond_wait.c:667
#3  0x7f54551dc917 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f54551debf7 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f54551dece2 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f54551e3d61 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f54551e52e9 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f54551edff1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f545fc086db in start_thread (arg=0x7f5324d72700) at
pthread_create.c:463
#10 0x7f546430388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7f53ed0f1700 (LWP 11757)):
#0  0x7f545fc0eed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f53ed0f0740, expected=0, futex_word=0x7f53ed0f0928) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f545fc0eed9 in __pthread_cond_wait_common (abstime=0x7f53ed0f07e0,
mutex=0x7f53ed0f08d8, cond=0x7f53ed0f0900) at pthread_cond_wait.c:533
#2  0x7f545fc0eed9 in __pthread_cond_timedwait (cond=0x7f53ed0f0900,
mutex=0x7f53ed0f08d8, abstime=0x7f53ed0f07e0) at pthread_cond_wait.c:667
#3  0x7f54551dc917 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f54551debf7 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f54551dece2 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f54551e3d61 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f54551e52e9 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f54551edff1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f545fc086db in start_thread (arg=0x7f53ed0f1700) at
pthread_create.c:463
#10 0x7f546430388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f5338669700 (LWP 11647)):
#0  0x7f545fc0eed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5338668740, expected=0, futex_word=0x7f5338668928) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f545fc0eed9 in __pthread_cond_wait_common (abstime=0x7f53386687e0,

[kmail2] [Bug 339181] moving mails from cached imap to local folder leaves mails without RID

2015-01-08 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=339181

Erasmo Caponio erasmocapo...@tiscali.it changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

--- Comment #5 from Erasmo Caponio erasmocapo...@tiscali.it ---
I confirm this terrible bug. Kubuntu 14.04, kde 4.14.2

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


[kontact] [Bug 326548] kmail hanging on a imap account

2015-01-08 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=326548

Erasmo Caponio erasmocapo...@tiscali.it changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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


Make the world a better place. Donate to our year end fundraiser 
https://www.kde.org/fundraisers/yearend2014/
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kontact] [Bug 326548] New: kmail hanging on a imap account

2013-10-24 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=326548

Bug ID: 326548
   Summary: kmail hanging on a imap account
Classification: Unclassified
   Product: kontact
   Version: 4.11.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: erasmocapo...@tiscali.it

Application: kontact (4.11.2)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-12-generic x86_64
Distribution: Ubuntu 13.10

-- Information about the crash:
I was trying to read email messages in a imap account
kde 4.11.2 on Kubuntu 13.10

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7fb7e9dad7c0 (LWP 10017))]

Thread 6 (Thread 0x7fb7cb2b7700 (LWP 10018)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb7e4b381cd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fb7e4b38209 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fb7e123ff6e in start_thread (arg=0x7fb7cb2b7700) at
pthread_create.c:311
#4  0x7fb7e72f29cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 5 (Thread 0x7fb78a9b4700 (LWP 10019)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb7e4878bbd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fb7e4b67a76 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fb7e123ff6e in start_thread (arg=0x7fb78a9b4700) at
pthread_create.c:311
#4  0x7fb7e72f29cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7fb776b07700 (LWP 10041)):
#0  0x7fb7e799777a in qt_gettime () at tools/qelapsedtimer_unix.cpp:146
#1  0x7fb7e7a70fe5 in updateCurrentTime (this=0x7fb770002660) at
kernel/qeventdispatcher_unix.cpp:354
#2  QTimerInfoList::timerWait (this=0x7fb770002660, tm=...) at
kernel/qeventdispatcher_unix.cpp:461
#3  0x7fb7e7a6f82c in timerSourcePrepareHelper (src=optimized out,
timeout=0x7fb776b06bb4) at kernel/qeventdispatcher_glib.cpp:136
#4  0x7fb7e7a6f8d5 in timerSourcePrepare (source=optimized out,
timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169
#5  0x7fb7e0d5fd4d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb7e0d605c3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fb7e0d607ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fb7e7a6fa76 in QEventDispatcherGlib::processEvents
(this=0x7fb778c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#9  0x7fb7e7a415ef in QEventLoop::processEvents
(this=this@entry=0x7fb776b06d70, flags=...) at kernel/qeventloop.cpp:149
#10 0x7fb7e7a418e5 in QEventLoop::exec (this=this@entry=0x7fb776b06d70,
flags=...) at kernel/qeventloop.cpp:204
#11 0x7fb7e794088f in QThread::exec (this=this@entry=0xe62550) at
thread/qthread.cpp:542
#12 0x7fb7e7a22d13 in QInotifyFileSystemWatcherEngine::run (this=0xe62550)
at io/qfilesystemwatcher_inotify.cpp:265
#13 0x7fb7e7942f2f in QThreadPrivate::start (arg=0xe62550) at
thread/qthread_unix.cpp:338
#14 0x7fb7e123ff6e in start_thread (arg=0x7fb776b07700) at
pthread_create.c:311
#15 0x7fb7e72f29cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fb775266700 (LWP 10050)):
#0  0x7fb7e72e46bd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb7e0d9f670 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb7e0d601cc in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb7e0d6063b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb7e0d607ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb7e7a6fa76 in QEventDispatcherGlib::processEvents
(this=0x7fb76c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x7fb7e7a415ef in QEventLoop::processEvents
(this=this@entry=0x7fb775265db0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7fb7e7a418e5 in QEventLoop::exec (this=this@entry=0x7fb775265db0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7fb7e794088f in QThread::exec (this=optimized out) at
thread/qthread.cpp:542
#9  0x7fb7e7942f2f in QThreadPrivate::start (arg=0x96fee0) at
thread/qthread_unix.cpp:338
#10 0x7fb7e123ff6e in start_thread (arg=0x7fb775266700) at
pthread_create.c:311
#11 0x7fb7e72f29cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fb775a67700 (LWP 10607)):
#0  0x7fb7e0da00ed in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0

[kontact] [Bug 326548] kmail hanging on a imap account

2013-10-24 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=326548

Erasmo Caponio erasmocapo...@tiscali.it changed:

   What|Removed |Added

  Component|general |mail

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


[kontact] [Bug 326548] kmail hanging on a imap account

2013-10-24 Thread Erasmo Caponio
https://bugs.kde.org/show_bug.cgi?id=326548

Erasmo Caponio erasmocapo...@tiscali.it changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

--- Comment #1 from Erasmo Caponio erasmocapo...@tiscali.it ---
It seems that the problem happens every time I resume my system from suspend
having Kontact been left running

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