[kmail2] [Bug 357313] Column-width in the main window, i.e. "subject", "from", "date" not kept, crowded to left
https://bugs.kde.org/show_bug.cgi?id=357313 Christian Reiner changed: What|Removed |Added CC||f...@christian-reiner.info --- Comment #7 from Christian Reiner --- I still have this issue on current KDE Neon using KMail and Kontact in version 4.20 as delivered by the distribution. It does not always happen. I have the impression that it mostly happens when I close KMail before closing the KDE session. So it could be connected to different strategies of how an application performs the shutdown. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 322760] New: Kontact crashes upon shutdown when knode was enabled
https://bugs.kde.org/show_bug.cgi?id=322760 Bug ID: 322760 Summary: Kontact crashes upon shutdown when knode was enabled Classification: Unclassified Product: kontact Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: f...@christian-reiner.info Application: kontact (4.10.5) KDE Platform Version: 4.10.5 release 4 Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.16-desktop x86_64 Distribution: openSUSE 12.3 (x86_64) -- Information about the crash: - What I was doing when the application crashed: Every time I shutdown the kontact shell I get a KCrash handler after a while (often 1-2 minutes after the shutdown). - Custom settings of the application: I have the impression that this crash only happens, when knode had been enabled (used) inside that kontact session. This issue has been around for a few years now (if I remember correctly). Here I am referring to the dependency that knode has to be enabled to produce a crash. I failed to find prior reports for this although I remember I made one myself. Maybe they got removed because of being older? The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f14fa1d07c0 (LWP 9321))] Thread 5 (Thread 0x7f14ddabc700 (LWP 9322)): #0 0x7f14f193a964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f14f69522f0 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f14f6952329 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f14f1936e0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f14f77327dd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f14dd1bb700 (LWP 9323)): #0 0x7f14f193a964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f14f66d0157 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f14f697981e in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f14f1936e0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f14f77327dd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f148b209700 (LWP 9334)): #0 0x7fff7f7ff847 in clock_gettime () #1 0x7f14f774453d in clock_gettime () from /lib64/libc.so.6 #2 0x7f14f8a8bd94 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x7f14f8b60bed in ?? () from /usr/lib64/libQtCore.so.4 #4 0x7f14f8b60f33 in ?? () from /usr/lib64/libQtCore.so.4 #5 0x7f14f8b5f99c in ?? () from /usr/lib64/libQtCore.so.4 #6 0x7f14f8b5fa45 in ?? () from /usr/lib64/libQtCore.so.4 #7 0x7f14f092a338 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #8 0x7f14f092a9cb in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f14f092abc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7f14f8b602e6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #11 0x7f14f8b30adf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #12 0x7f14f8b30d68 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #13 0x7f14f8a330f0 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #14 0x7f14f8a360cc in ?? () from /usr/lib64/libQtCore.so.4 #15 0x7f14f1936e0f in start_thread () from /lib64/libpthread.so.0 #16 0x7f14f77327dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f148ba0a700 (LWP 17576)): #0 0x7fff7f7ff847 in clock_gettime () #1 0x7f14f774453d in clock_gettime () from /lib64/libc.so.6 #2 0x7f14f8a8bd94 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x7f14f8b60bed in ?? () from /usr/lib64/libQtCore.so.4 #4 0x7f14f8b60f33 in ?? () from /usr/lib64/libQtCore.so.4 #5 0x7f14f8b5f99c in ?? () from /usr/lib64/libQtCore.so.4 #6 0x7f14f8b5fa45 in ?? () from /usr/lib64/libQtCore.so.4 #7 0x7f14f092a338 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #8 0x7f14f092a9cb in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f14f092abc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7f14f8b602e6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #11 0x7f14f8b30adf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #12 0x7f14f8b30d68 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #13 0x7f14f8a330f0 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #14 0x7f14f44caa4e in KIO::NameLookUpThread::run (this=0x46bdb20) at /usr/src/debug/kdelibs-4.10.5/kio/kio/hostinfo.cpp:226 #15 0x7f14f8a360cc in ?? () from
[Akonadi] [Bug 274799] akonadi_imap_resource hangs while syncing Inbox
https://bugs.kde.org/show_bug.cgi?id=274799 --- Comment #8 from Christian Reiner f...@christian-reiner.info --- I installed a completely new system over the last days, openSUSE-12.3. I am now running KDE_4.10 form the openSUSE repo KDE:Release.410 and did NOT restore any data whatsover from a previous system. Instead I configured my PIM ressources from scratch. As a result I have a fully functional system (as expected), BUT: the issue I described above on 2013-02-09 exists with exactly the same symptoms: all works fine for some time, but sooner or later an imap resource with suddenly hang (no error) and stay locked, no matter how long you wait (well, I waited 2 hours...). Only when I restart akonadi or use the procedure sketched above: toggling the ressource to offline _twice_ I can get it to sync again. Then it works fine, until the next hang. I checked on server side and failed to see any suspicious message in the imap servers logs. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 274799] akonadi_imap_resource hangs while syncing Inbox
https://bugs.kde.org/show_bug.cgi?id=274799 Christian Reiner f...@christian-reiner.info changed: What|Removed |Added CC||f...@christian-reiner.info --- Comment #7 from Christian Reiner f...@christian-reiner.info --- I too encounter such 'hangs' again and again, not only on INBOX, but most often on that folder. Removing the resource and adding it again did not solve the problem. I hesitate to wipe the whole database, since I have quite a lot of resources... Akonadi has been upgraded a few times inbetween, no change. Currently running stable opensuse-KDE-4.10 packages. On thing I notice: when using 'aknadiresource' I can temporarily fix this issue (reanimate for the time being) by chosing 'Toggle Online/Offline' whilst the resource hangs. Currently I have to do this _two_ times: after the first times the display changes, another folder is said to be synced but things still hang. Note that the resource is still marked as 'online', although I clicked to switch to offline. After the second click the display changes again: still online, but now it simply says 'Ready' and then starts to sync fine after maybe 2-3 seconds. I have the impression that 2 or 3 agents are running in parallel, both being somehow blocked?!? I am happy to provide any information required. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 312960] Sieve script manager inside Kmail2 mingles editing and activating scripts.
https://bugs.kde.org/show_bug.cgi?id=312960 --- Comment #3 from Christian Reiner f...@christian-reiner.info --- Unbelievable. Thanks! -- 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
[kmail2] [Bug 312923] Server side errors not visualized when managing sieve scripts
https://bugs.kde.org/show_bug.cgi?id=312923 --- Comment #2 from Christian Reiner f...@christian-reiner.info --- The number of scripts a user can maintain in his personal area is controlled by the configuration option 'sieve_maxscripts' in file /etc/imapd.conf. This is if you use the cyrus implementation. Maybe your server has a higher limit you don't reach? -- 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
[kmail2] [Bug 312960] New: Sieve script manager inside Kmail2 mingles editing and activating scripts.
https://bugs.kde.org/show_bug.cgi?id=312960 Bug ID: 312960 Summary: Sieve script manager inside Kmail2 mingles editing and activating scripts. Classification: Unclassified Product: kmail2 Version: 4.9.5 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-bugs@kde.org Reporter: f...@christian-reiner.info Kmail2 offers an integrated sieve script manager. It works fine, though it is a little 'raw'... One thing that really needs to be changed: 'Activating' and 'editing' a script are logically two completely independent things. Yet the manager mingles both: it is impossible to simply edit a script without activating it as the default script. That makes little sense and is not neccessary. Instead of the current solution I suggest to separate both aspects: - highlighting an entry (a script) should only select it to be able to run one of the actions offered below. The activation of a script (setting it as 'default' on the server side) should be completely separate. There is absolutely no reason to connect both aspects. - selecting one of the radio buttons in from of the entries should trigger that second aspect. Certainly even now it is possible to get your scripts configured and sorted out. But looking closer the current solution forces periods where scripts are active (selected as default) that are not meant to. What for? Reproducible: Always -- 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
[kmail2] [Bug 312923] New: Server side errors not visualized when managing sieve scripts
https://bugs.kde.org/show_bug.cgi?id=312923 Bug ID: 312923 Summary: Server side errors not visualized when managing sieve scripts Classification: Unclassified Product: kmail2 Version: 4.9.5 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-bugs@kde.org Reporter: f...@christian-reiner.info I just found out about the reason a problem I faced for several weeks: When managing my personal sieve scripts using kmail2s interface I always got a Error unknown whatever I tried. Managing the scripts had worked before, actually I setup the scripts using kmail2s interface. I failed to find out what the actual problem is. Today I finally used 'sieveshell' to give it another try and was presented a clear and easy to understand error, when trying to upload a modified script: you are only allowed to setup 5 scripts. Wow. Ok, that is something that actually helps! 1.) I know what the problem is 2.) is was a question of seconds to fix the problem 3.) I was able to manage my scripts again So my question is: why does kmail2 not display that error message? Why the Error unknown? Reproducible: Always Steps to Reproduce: 1. Use a cyrus imap account and maintain sieve scripts, more than are actually allowed on the server 2. Try to make _any_ modifications to the existing sieve scripts using kmail2s script manager 3. Shake your head at the great error message you get Actual Results: I get a meaningless error message: Error unknown for whatever modification I try, except activating a script or another. Expected Results: I would expect to get the error message the server generates. This is what error messages are there for. It actually sometimes helps users to give them the error message. -- 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 310694] New: Kmail thinks it is offline, switching online as offered does not work
https://bugs.kde.org/show_bug.cgi?id=310694 Bug ID: 310694 Severity: normal Version: 4.9.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail thinks it is offline, switching online as offered does not work Classification: Unclassified OS: Linux Reporter: f...@christian-reiner.info Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 Sometimes KMail2 thinks it is offline, after startup when network is missing or during a session when internet connection is lost. Fine so far. KMail2 shows this message inside the main area: KMail is currently in offline mode. Click here to go online . . . Klicking the here to do so never changes anything. When in these cases I use akonadiconsole to toggle the configured imap account online this works without a problem (1-2 secs) and also KMail2 then picks up activity again without a problem. Reproducible: Always Steps to Reproduce: 1. Start KDE session without internet connection 2. Start KMail2, it will show the message that it is offline 3. Click the here in the message as offered to toggle to online Actual Results: Nothing happens. Using the workaround mentioned in the description works on all cases. Expected Results: KMail2 should toggle to online. I guess that means the imap ressource in akonadi should be toggled to online. -- 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 310695] New: Kontact crashes on ever startup after an unclean shutdown, launches fine on secont attempt.
https://bugs.kde.org/show_bug.cgi?id=310695 Bug ID: 310695 Severity: crash Version: 4.9.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes on ever startup after an unclean shutdown, launches fine on secont attempt. Classification: Unclassified OS: Linux Reporter: f...@christian-reiner.info Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.3) KDE Platform Version: 4.9.3 release 520 Qt Version: 4.8.3 Operating System: Linux 3.4.11-2.16-desktop x86_64 Distribution: openSUSE 12.2 (x86_64) -- Information about the crash: Often Kontact crashes on startup (see backtrace), but it always starts fine on a second attempt. I assume the crashed attempted did do some cleanup work? - What I was doing when the application crashed: Kontact has been shutdown unclean one or the other way. I assume it is not able to cleanup propperly in those cases. I think the effect depends on having had more than just KMail2 activated in the previous session. - I think this is an old bug that was around for many many month and finally closed about a year ago. Exactly the same symptoms. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f78d2a51780 (LWP 4268))] Thread 3 (Thread 0x7f78b9dfb700 (LWP 4269)): #0 0x7f78ca8788f4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f78cf267eb7 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f78cfc6c2a0 WTF::pageheap_memory) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7f78cf267ee9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7f78ca874e0e in start_thread () from /lib64/libpthread.so.0 #4 0x7f78cffc92bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f78b94fa700 (LWP 4270)): #0 0x7f78cffc113f in poll () from /lib64/libc.so.6 #1 0x7f78ca2c9684 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f78ca2c97a4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f78d073ccf6 in QEventDispatcherGlib::processEvents (this=0x7f78b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f78d070d85f in QEventLoop::processEvents (this=this@entry=0x7f78b94f9e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f78d070dae8 in QEventLoop::exec (this=0x7f78b94f9e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f78d060ffc0 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f78d0612f9c in QThreadPrivate::start (arg=0x2553bb0) at thread/qthread_unix.cpp:338 #8 0x7f78ca874e0e in start_thread () from /lib64/libpthread.so.0 #9 0x7f78cffc92bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f78d2a51780 (LWP 4268)): [KCrash Handler] #6 activateInitialPluginModule (this=0x2677120) at /usr/src/debug/kdepim-4.9.3/kontact/src/mainwindow.cpp:322 #7 Kontact::MainWindow::activateInitialPluginModule (this=0x2677120) at /usr/src/debug/kdepim-4.9.3/kontact/src/mainwindow.cpp:317 #8 0x004040aa in KontactApp::newInstance (this=0x7fff8ced37c0) at /usr/src/debug/kdepim-4.9.3/kontact/src/main.cpp:148 #9 0x7f78d1e278d2 in KUniqueApplicationAdaptor::newInstance (this=0x26a5da0, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.9.3/kdeui/kernel/kuniqueapplication.cpp:442 #10 0x7f78d1e27954 in qt_static_metacall (_a=0x7fff8ced2a00, _id=optimized out, _o=optimized out, _c=optimized out) at /usr/src/debug/kdelibs-4.9.3/build/kdeui/kuniqueapplication_p.moc:58 #11 KUniqueApplicationAdaptor::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=0x7fff8ced2a00) at /usr/src/debug/kdelibs-4.9.3/build/kdeui/kuniqueapplication_p.moc:52 #12 0x7f78d1e27a8b in KUniqueApplicationAdaptor::qt_metacall (this=0x26a5da0, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0x7fff8ced2a00) at /usr/src/debug/kdelibs-4.9.3/build/kdeui/kuniqueapplication_p.moc:102 #13 0x7f78cd016c1a in QDBusConnectionPrivate::deliverCall (this=this@entry=0x253b8d0, object=object@entry=0x26a5da0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:947 #14 0x7f78cd017d15 in QDBusConnectionPrivate::activateCall (this=this@entry=0x253b8d0, object=0x26a5da0, flags=flags@entry=337, msg=...) at qdbusintegrator.cpp:857 #15 0x7f78cd018686 in QDBusConnectionPrivate::activateObject (this=0x253b8d0, node=..., msg=..., pathStartPos=optimized out) at qdbusintegrator.cpp:1423 #16 0x7f78cd01877b in QDBusActivateObjectEvent::placeMetaCall (this=0x3245c60) at qdbusintegrator.cpp:1537 #17 0x7f78d07234ee in QObject::event (this=0x7fff8ced37c0, e=optimized out) at
[Bug 303087] Reproduceable crash of imap ressource
https://bugs.kde.org/show_bug.cgi?id=303087 --- Comment #5 from Christian Reiner f...@christian-reiner.info --- Additional information: I fixed a problem on the imap server (cyrus-2.3.16), an invalid 'Trash' folder Wherever that came from (akonadi?) this fixed most of the problems for me. I do not experience any more crashes, though the imap resource is pretty slow (unresponsive) right now. This fits to what I saw in the mail client: diggin deeper I saw a message about a non existing job being queued. -- You are receiving this mail because: 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 303087] Reproduceable crash of imap ressource
https://bugs.kde.org/show_bug.cgi?id=303087 --- Comment #3 from Christian Reiner f...@christian-reiner.info --- Unfortunately I have to report that the issue is _not_ fixed. It appears the ressource still crashes, but not in all situations. I will keep an eye on that (cannot really miss it, error popups every few minutes). I got the impression these crashes happen when there are latencies in the network connection. -- You are receiving this mail because: 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 303087] New: Reproduceable crash of imap ressource
https://bugs.kde.org/show_bug.cgi?id=303087 Bug ID: 303087 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Reproduceable crash of imap ressource Classification: Unclassified OS: Linux Reporter: f...@christian-reiner.info Hardware: openSUSE RPMs Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.4 (4.8.4) release 7 Qt Version: 4.8.2 Operating System: Linux 3.4.3-30-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: The system had a longer period of high network load that lead to several timeouts of different applications. The system runs fine otherwise. I restartet the akoadi server and retried, it appears the crashes can be reproduced. I will try to restart the whole system in a minute. The crash can be reproduced every time. -- Backtrace: Application: c-r.info of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7f8b7a7fd760 (LWP 31732))] Thread 3 (Thread 0x7f8b69228700 (LWP 31851)): #0 0x7fffc0dff82f in clock_gettime () #1 0x7f8b74df3d9a in clock_gettime () from /lib64/librt.so.1 #2 0x7f8b79bb7014 in do_gettime (frac=0x7f8b69227bc8, sec=0x7f8b69227bc0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7f8b79c8e59d in QTimerInfoList::updateCurrentTime (this=0x7f8b64002860) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7f8b79c8e8d3 in QTimerInfoList::timerWait (this=0x7f8b64002860, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #6 0x7f8b79c8d30c in timerSourcePrepareHelper (src=optimized out, timeout=0x7f8b69227c9c) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7f8b79c8d3b5 in timerSourcePrepare (source=optimized out, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169 #8 0x7f8b74b433ce in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #9 0x7f8b74b43bcb in ?? () from /usr/lib64/libglib-2.0.so.0 #10 0x7f8b74b43dd4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #11 0x7f8b79c8de36 in QEventDispatcherGlib::processEvents (this=0x7f8b640008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7f8b79c5d842 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #13 0x7f8b79c5da97 in QEventLoop::exec (this=0x7f8b69227e00, flags=...) at kernel/qeventloop.cpp:204 #14 0x7f8b79b5d5f7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #15 0x7f8b78874119 in KIMAP::SessionThread::run (this=0x16b5130) at /usr/src/debug/kdepimlibs-4.8.4/kimap/sessionthread.cpp:181 #16 0x7f8b79b6061b in QThreadPrivate::start (arg=0x16b5130) at thread/qthread_unix.cpp:307 #17 0x7f8b75aa7f05 in start_thread () from /lib64/libpthread.so.0 #18 0x7f8b761f510d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8b61eb1700 (LWP 328)): #0 0x7f8b761ebff3 in poll () from /lib64/libc.so.6 #1 0x7f8b74b43ca6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8b74b43dd4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8b79c8de36 in QEventDispatcherGlib::processEvents (this=0x7f8b58005d60, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f8b79c5d842 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f8b79c5da97 in QEventLoop::exec (this=0x7f8b61eb0e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f8b79b5d5f7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f8b78874119 in KIMAP::SessionThread::run (this=0x1827a30) at /usr/src/debug/kdepimlibs-4.8.4/kimap/sessionthread.cpp:181 #8 0x7f8b79b6061b in QThreadPrivate::start (arg=0x1827a30) at thread/qthread_unix.cpp:307 #9 0x7f8b75aa7f05 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8b761f510d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8b7a7fd760 (LWP 31732)): [KCrash Handler] #6 0x in ?? () #7 0x7f8b78887357 in qDeleteAllQListKIMAP::Job*::const_iterator (end=optimized out, begin=optimized out) at /usr/include/QtCore/qalgorithms.h:322 #8 qDeleteAllQQueueKIMAP::Job* (c=...) at /usr/include/QtCore/qalgorithms.h:330 #9 KIMAP::SessionPrivate::clearJobQueue (this=0x1802720) at /usr/src/debug/kdepimlibs-4.8.4/kimap/session.cpp:401 #10 0x7f8b79c77e06 in QObject::event (this=0x1821770, e=optimized out) at kernel/qobject.cpp:1204 #11 0x7f8b78fe1fe4 in notify_helper (e=0x7f8b58007fd0, receiver=0x1821770, this=0x14b4470) at kernel/qapplication.cpp:4551 #12 QApplicationPrivate::notify_helper (this=0x14b4470, receiver=0x1821770, e=0x7f8b58007fd0) at
[Bug 303087] Reproduceable crash of imap ressource
https://bugs.kde.org/show_bug.cgi?id=303087 --- Comment #2 from Christian Reiner f...@christian-reiner.info --- Surprising enough I got that issue fixed by restarting the imap server ! It is a cyrus imap server in version 2.3.16. Since that restart I did not experience a single crash anyone. -- You are receiving this mail because: 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 295657] Random crashes independent from specific action
https://bugs.kde.org/show_bug.cgi?id=295657 Christian Reiner f...@christian-reiner.info changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Christian Reiner f...@christian-reiner.info --- It appears, the issue has been fixed by whatever coincidence. I did not experience a single crash during the last week. -- 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 295657] Random crashes independent from specific action
https://bugs.kde.org/show_bug.cgi?id=295657 --- Comment #2 from Christian Reiner f...@christian-reiner.info --- Funny: I haven't had a crash for three days now. I saw that openSUSE integrated a few backports and provided new packages four days ago. Maybe the bug has been fixed by coincidence ? Anyway, I installed the debug package (thought I had before...) and promise to generate a better backtrace in case of another crash. -- 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 285802] kmail - no filters are applied on incomming messages
https://bugs.kde.org/show_bug.cgi?id=285802 Christian Reiner f...@christian-reiner.info changed: What|Removed |Added CC||f...@christian-reiner.info --- Comment #4 from Christian Reiner f...@christian-reiner.info --- I confirm this bug for KDE-4.8 (openSUSE rpms). Manually apllying filters works fine in all aspects for me, but the filters are not applied automatically to incoming messages in an imap account, thought the option is checked. This problem is old, it has been said to be fixed again and again and again, yet it comes back again and again and again. -- 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 296013] New: Sporadic segfaults of KMail2
https://bugs.kde.org/show_bug.cgi?id=296013 Bug ID: 296013 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Sporadic segfaults of KMail2 Classification: Unclassified OS: Linux Reporter: f...@christian-reiner.info Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) release 481 Qt Version: 4.8.0 Operating System: Linux 3.2.7-10-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: Nothing special. I see these crashes since upgrading to KDE-4.8, KDE-4.8.1 did not fix it. KMail2 crashes after a while, between 1 to 5 minutes. Often it is not even a user action triggering the segfault, but it just happens. I would call KMail2 currently very unstable because of this issue, I see about 10-20 crashes a day ! The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0x7f7855d51760 (LWP 6417))] Thread 4 (Thread 0x7f783d31e700 (LWP 6418)): #0 0x7f784dbf3e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7852582c12 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f7852f211a0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7f7852582c49 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7f784dbeff05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f785327410d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f783ca05700 (LWP 6419)): #0 0x7fffe31ad8de in ?? () #1 0x7f784b6cbd9a in clock_gettime () from /lib64/librt.so.1 #2 0x7f785390ba24 in do_gettime (frac=0x7f783ca04bf8, sec=0x7f783ca04bf0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7f78539e20bd in QTimerInfoList::updateCurrentTime (this=0x7f78380020d0) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7f78539e1d71 in timerSourceCheckHelper (src=optimized out) at kernel/qeventdispatcher_glib.cpp:150 #6 timerSourceCheckHelper (src=optimized out) at kernel/qeventdispatcher_glib.cpp:144 #7 0x7f784d6e0264 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #8 0x7f784d6e0ab2 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f784d6e0f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7f78539e1956 in QEventDispatcherGlib::processEvents (this=0x7f78380008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #11 0x7f78539b1682 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #12 0x7f78539b18d7 in QEventLoop::exec (this=0x7f783ca04e20, flags=...) at kernel/qeventloop.cpp:204 #13 0x7f78538b2537 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #14 0x7f78538b555b in QThreadPrivate::start (arg=0x7a0780) at thread/qthread_unix.cpp:298 #15 0x7f784dbeff05 in start_thread () from /lib64/libpthread.so.0 #16 0x7f785327410d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f77edbe5700 (LWP 6543)): [KCrash Handler] #6 0x7f78531cdd95 in raise () from /lib64/libc.so.6 #7 0x7f78531cf2ab in abort () from /lib64/libc.so.6 #8 0x7f7848a47655 in _dbus_abort () at dbus-sysdeps.c:94 #9 0x7f7848a3e5f1 in _dbus_warn_check_failed (format=0x7f7848a4d920 arguments to %s() were incorrect, assertion \%s\ failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n) at dbus-internals.c:289 #10 0x7f78503ef10f in q_dbus_pending_call_unref (pending=optimized out) at qdbus_symbols_p.h:321 #11 QDBusPendingCallPrivate::~QDBusPendingCallPrivate (this=0x7f77e0010920, __in_chrg=optimized out) at qdbuspendingcall.cpp:137 #12 0x7f78503ef2c3 in ~QExplicitlySharedDataPointer (this=optimized out, __in_chrg=optimized out) at ../../src/corelib/tools/qshareddata.h:166 #13 ~QDBusPendingCall (this=optimized out, __in_chrg=optimized out) at qdbuspendingcall.cpp:271 #14 QDBusPendingCall::~QDBusPendingCall (this=optimized out, __in_chrg=optimized out) at qdbuspendingcall.cpp:271 #15 0x7f784b452ebd in ~QDBusPendingReply (this=0x7f77edbe4870, __in_chrg=optimized out) at /usr/include/QtDBus/qdbuspendingreply.h:115 #16 Nepomuk::ResourceWatcher::addResource (this=optimized out, res=optimized out) at /usr/src/debug/kdelibs-4.8.1/nepomuk/core/resourcewatcher.cpp:143 #17 0x7f784b434dcb in Nepomuk::ResourceData::load (this=0x7f77e0002240) at /usr/src/debug/kdelibs-4.8.1/nepomuk/core/resourcedata.cpp:405 #18 0x7f784b4357bc in Nepomuk::ResourceData::property (this=0x7f77e0002240, uri=...) at /usr/src/debug/kdelibs-4.8.1/nepomuk/core/resourcedata.cpp:265 #19
[Bug 296013] Sporadic segfaults of KMail2
https://bugs.kde.org/show_bug.cgi?id=296013 Christian Reiner f...@christian-reiner.info changed: What|Removed |Added Component|general |mail Version|unspecified |4.8.x -- 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 295657] New: Random crashes independent from specific action
https://bugs.kde.org/show_bug.cgi?id=295657 Bug ID: 295657 Severity: crash Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Random crashes independent from specific action Classification: Unclassified OS: Linux Reporter: f...@christian-reiner.info Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 Created attachment 69445 -- https://bugs.kde.org/attachment.cgi?id=69445action=edit kcrash backtrace I experience random crashes in Kmail2. The crashes started after upgrading to KDE-4.8 and still happen under KDE-4.8.1. There is no specific action I can relate to the crashes, they seem to be triggered by something in background, independent of user interaction. I would say KMail2 roughly crashes in average after about 5 minutes after being launched. Not exactly reproducable, but randomly again and again. -- 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 250573] New items placed wrong in list for currently opened feed
https://bugs.kde.org/show_bug.cgi?id=250573 Christian Reiner f...@christian-reiner.info changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME Summary|new items played wrong in |New items placed wrong in |list for currently opened |list for currently opened |feed|feed --- Comment #1 from Christian Reiner foss christian-reiner info 2011-12-12 16:08:51 --- I do not see this behaviour any more using KDE-4.7.4. -- 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 217867] Attribute template not saved in address ressource of type LDAP server
https://bugs.kde.org/show_bug.cgi?id=217867 --- Comment #1 from Christian Reiner foss christian-reiner info 2011-12-12 16:20:58 --- Nothing has changed in between, I see exactly the same behaviour in the current KDE-4.7.4. -- 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 283252] akonadi resource wizard does not show valid collections found on a caldav server when using the fetch button in a DAV groupware resource
https://bugs.kde.org/show_bug.cgi?id=283252 --- Comment #3 from Christian Reiner foss christian-reiner info 2011-10-04 06:32:24 --- Sorry not to mention this in the first place: I did successfully access the collections (calendars) using a standard web browser. I got valid results, calendards for the two existing users did show up. So I assume the calendars did exist whilst trying to access them usin akoadi. Also in my eyes this assumption is confirmed by the fact that according to the server log files akonadi was given valid return codes (207) for the specific collections upon request. This would not have been the case for non-existing collections. Removing the single entry does not remove the collection as being detected by akonadi. This indeed suggests that the collection did not exist before the creation of the test entry. Hm. I am certainly willing to provide more information upon request, but I will not start a huge debugging session myself, since I am busy in my own projects :-) -- 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 283252] New: akonadi resource wizard does not show valid collections found on a caldav server when using the fetch button in a DAV groupware resource
https://bugs.kde.org/show_bug.cgi?id=283252 Summary: akonadi resource wizard does not show valid collections found on a caldav server when using the fetch button in a DAV groupware resource Product: Akonadi Version: 4.7 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DAV Resource AssignedTo: kdepim-bugs@kde.org ReportedBy: f...@christian-reiner.info Version: 4.7 (using KDE 4.7.1) OS:Linux I try to access an ownCloud server using the caldav protocol. The server works, the calendar resources are valid and usable in other clients. However I fail to finish configuring a DAV groupware resource because no collections are offered when accessing the server. Without these the wizzard cannot save the configuration (which makes sense). The same wizzards succeeds to access a carddav collection on the same server. I tried to connect to two other owncloud instances and got the same result. A contacted a few other users and we confirmed that their akonadi succeeded in using the same caldav resources. My conclusion: - the server is working fine - if serves valid and usable caldav resources - akonadi in version 4.7.1 is normally able to use these = this bug _might_ be a problem of the opensuse rpm I am using, though this is not sure. It might as well be a kde bug if my version is slightly older or younger than the versions other users use (using other distros) Reproducible: Always Steps to Reproduce: define a new DAV resource (or use an existing one) and add a url to a caldav server. Actual Results: The fetch button triggers the connection, the server logs show the requests and results as expected (401 followed by a 207 for each attempt). However no collections are offered afterwards, though these exist and are usable by other clients. Interesting detail: the same wizzard works for the carddav protocol using the same server. Expected Results: The collections to be found, recognized and offered. -- 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 283252] akonadi resource wizard does not show valid collections found on a caldav server when using the fetch button in a DAV groupware resource
https://bugs.kde.org/show_bug.cgi?id=283252 --- Comment #1 from Christian Reiner foss christian-reiner info 2011-10-03 15:30:14 --- Ok, solved the issue (in a way)... I realized that the wizzard does not offer any collection, if there is no entry in the calendar. The moment I made a test entry the collection showed up. I still dont see that calendar in korganizer, but that is another story. I dont want to set this entry to fixed, since this still is an issue in my eyes, though less important. It still is an issue since the calendar does exist, even if it is empty. Also, now all three available calendars are shown as collections though only one received a test entry. This is a little confusing :-) -- 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 193514] Crash when activating plugin
https://bugs.kde.org/show_bug.cgi?id=193514 --- Comment #53 from Christian Reiner reiner imageware de 2009-12-08 09:05:31 --- To comment #52: Why do you think it's random ? I tested again, the bug still exists in kde-4.3.4, behaves exactly as written in Comment #9. That means it is clearly reproduceable. -- 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 217867] New: Attribute template not saved in address ressource of type LDAP server
https://bugs.kde.org/show_bug.cgi?id=217867 Summary: Attribute template not saved in address ressource of type LDAP server Product: kaddressbook Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rei...@imageware.de CC: to...@kde.org Version:(using KDE 4.3.4) OS:Linux Installed from:openSUSE RPMs In a configured (and working) address ressource of type LDAP it is not possible to change the attribute template (Configuration = Edit Attributes = Template). Instead of being saved the selection is always back the the first entry (Kolab) whenever you open the configuration dialogue. -- 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 189759] New: printing message directly from the composer prints headers, but an empty body
https://bugs.kde.org/show_bug.cgi?id=189759 Summary: printing message directly from the composer prints headers, but an empty body Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rei...@imageware.de Version:(using KDE 4.2.2) Installed from:SuSE RPMs Printing a message directly from the compose shows headers all right, but the body is always empty. This can be reproduced for a single message several times in a row and for each message that is composed. The printout is ok if the message has been stored to the drafts folder once or has been sent and is selected again from the sent messages folder. -- 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
