[Bug 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #21 from Marc Schiffbauer mschiff gentoo org 2011-10-28 11:14:23 --- (In reply to comment #20) Fixed reload config for manual order (fixed in 4.7.4/master) I guess you are still working on it? Then thanks for the update. I just compiled current 4.7 branch again, but the issue is still there. To me it seems that the problem is: It is not possible to drag a folder and then drop it between two other folders to rearrange it. You just can move folders into other folders. Now what happened to me while testing a minute ago is: I wanted to rearrange the INBOX and accidentally dropped it into the Drafts folder. When kmail tried to sync this change (IMAP) the server will have refused that change because moving a root folder into one of its children is not really a good idea ;) Now kmail (or akonadi?) lost all locally cached mails and just has started to redownload everything... this will last some hours now. -- 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 285010] New: kmail2 randomly tells me that a shortcut is ambigous
https://bugs.kde.org/show_bug.cgi?id=285010 Summary: kmail2 randomly tells me that a shortcut is ambigous Product: kmail2 Version: 4.7 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: msch...@gentoo.org Version: 4.7 (using Devel) OS:Linux Some shortcuts I use (F5 for folder update, Y for mark message as read, Shift-Y for mark all messages as read) work most of the time. But sometimes, kmail2 tells me that it did not take the action because the shortcut is ambiguous. When I check that as suggested by that message using Settings - Configure shortcuts I c just can see that everything is it should be. I tried re-assigning the shortcut, quit kmail, restart it: This fixes it mpst of the times I was not able yet to clearly reproduce either to trigger the bug nor to fix it. But there is definitely something weird going on with shortcut handling. I am using current 4.7 branch, compiled an hour ago or so. Reproducible: Sometimes Steps to Reproduce: It seems this is not bound to special shortcuts, but you may try it with the examples I mentioned above. Expected Results: It should work as expected. -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org --- Comment #19 from Marc Schiffbauer mschiff gentoo org 2011-10-26 21:01:29 --- Please vote for the bug. Its really annoying... Confirmed on current 4.7 branch -- 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 281832] New: kmail does not handle charsets for mail body when replying to a decrypted mail properly
https://bugs.kde.org/show_bug.cgi?id=281832 Summary: kmail does not handle charsets for mail body when replying to a decrypted mail properly Product: kmail2 Version: 4.7 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: msch...@gentoo.org Version: 4.7 (using KDE 4.7.1) OS:Linux When kmail decrypts a mail the display of the mail body is shown correctly. But when hit the reply button, the quoted mail body text has garbage characters for non-ascii characters (german umlauts for example). Looks like utf8 text is shown with charset set to latin1 or something like that. This lookes exactly like a bug that has been in kmail2 for regular unencrypted mail as well some time ago. Reproducible: Always Steps to Reproduce: - Have a encrypted mail in your mailbox - Have some non english text in that mail (german with umlauts in my case) - Let kmail decrypt and display that message - Hit reply button to open mail editor with quoted mail text Actual Results: Das Ganze sollten wir mit logischen Kriterien vollständig testen. Expected Results: Das Ganze sollten wir mit logischen Kriterien vollständig testen. What might help to debug this: If I select some text in the mail body before replying only that text will be quoted and that text will have everythign allright then. So, just reply with no text selected: Whole text is quoted with wrong encoding And selecting whole text, then reply: Whole text is quoted and looks fine -- 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 271826] kmail does not handle message encoding properly on replies (base64 encoded multipart message)
https://bugs.kde.org/show_bug.cgi?id=271826 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO | --- Comment #4 from Marc Schiffbauer marc links2linux de 2011-06-30 16:26:38 --- Mail sent on 17.05.2011 23:16 -- 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 276735] New: shotrcut (+) to jump to next unread message does not work
https://bugs.kde.org/show_bug.cgi?id=276735 Summary: shotrcut (+) to jump to next unread message does not work Product: kmail2 Version: 2.0.95 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 2.0.95 (using Devel) OS:Linux When reading mail, there is a shortcut to jump to the next unread message: Th plus (*) key. But it does not work. Reproducible: Always Steps to Reproduce: Have unread mails in a mailbox, press + Actual Results: nothing happens Expected Results: Next unread mail should get focussed -- 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 276735] shotrcut (+) to jump to next unread message does not work
https://bugs.kde.org/show_bug.cgi?id=276735 --- Comment #1 from Marc Schiffbauer marc links2linux de 2011-06-29 17:16:07 --- Correction: Reproducible: Sometimes After rebooting it is working this time. So it seems its not so easy to reproduce. -- 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 271826] kmail does not handle message encoding properly on replies (base64 encoded multipart message)
https://bugs.kde.org/show_bug.cgi?id=271826 --- Comment #2 from Marc Schiffbauer marc links2linux de 2011-05-10 00:49:11 --- I just noticed that saving a message to a file (.mbox) seems to be broken, too: The saved file is empty... I saved the message using mutt then. But when I open the mail saved file in kmail I cannot reply to it (button disabled) I may sent you that mail via PM if you pretend to delete it afterwards. -Marc -- 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 272242] New: kmail crash while trying to save an attachment
https://bugs.kde.org/show_bug.cgi?id=272242 Summary: kmail crash while trying to save an attachment Product: kmail2 Version: 2.0.95 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application: kmail (2.0.95) KDE Platform Version: 4.6.3 (4.6.3) (Compiled from sources) Qt Version: 4.7.2 Operating System: Linux 2.6.38-gentoo-r3 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I got a amil with attachment. Then I clicken onto the attachement to save or open it. The dialog appeared and after clicking open kmail crashed -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fb64986c780 (LWP 22195))] Thread 4 (Thread 0x7fb62cd8a700 (LWP 22202)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fb63b6c34a4 in scavengerThread (context=0x7fb63bee5f20) at wtf/FastMalloc.cpp:2378 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7fb63bee5f20) at wtf/FastMalloc.cpp:1497 #3 0x7fb644a93e1c in start_thread () from /lib64/libpthread.so.0 #4 0x7fb646c286fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7fb629d6e700 (LWP 28431)): #0 0x7fb646c1df83 in poll () from /lib64/libc.so.6 #1 0x7fb63f21d89d in g_main_context_poll (context=0x747cd90, block=1, dispatch=1, self=value optimized out) at gmain.c:3404 #2 g_main_context_iterate (context=0x747cd90, block=1, dispatch=1, self=value optimized out) at gmain.c:3086 #3 0x7fb63f21ddcd in g_main_context_iteration (context=0x747cd90, may_block=1) at gmain.c:3154 #4 0x7fb647594ed6 in QEventDispatcherGlib::processEvents (this=0x5338280, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fb647569322 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fb647569564 in QEventLoop::exec (this=0x7fb629d6ddc0, flags=...) at kernel/qeventloop.cpp:201 #7 0x7fb64747f6a4 in QThread::exec (this=value optimized out) at thread/qthread.cpp:492 #8 0x7fb64754af08 in QInotifyFileSystemWatcherEngine::run (this=0x74b3e40) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7fb647481ef5 in QThreadPrivate::start (arg=0x74b3e40) at thread/qthread_unix.cpp:320 #10 0x7fb644a93e1c in start_thread () from /lib64/libpthread.so.0 #11 0x7fb646c286fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7fb6281bc700 (LWP 28436)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fb62827c6e0 in LoopRequest (data=0x785cae0) at playlist/thread.c:539 #2 Thread (data=0x785cae0) at playlist/thread.c:586 #3 0x7fb644a93e1c in start_thread () from /lib64/libpthread.so.0 #4 0x7fb646c286fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fb64986c780 (LWP 22195)): [KCrash Handler] #6 __strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp.S:260 #7 0x7fb646c26756 in tfind () from /lib64/libc.so.6 #8 0x7fb6282daf81 in Lookup (obj=value optimized out, psz_name=0x7fb628537a00 vmem-chroma) at misc/variables.c:188 #9 0x7fb6282dbc91 in var_SetChecked (p_this=value optimized out, psz_name=0x7fb628537a00 vmem-chroma, expected_type=value optimized out, val=...) at misc/variables.c:756 #10 0x7fb628533327 in var_SetString (mp=value optimized out, chroma=value optimized out, width=320, height=240, pitch=1280) at ../include/vlc_variables.h:261 #11 libvlc_video_set_format (mp=value optimized out, chroma=value optimized out, width=320, height=240, pitch=1280) at control/media_player.c:797 #12 0x7fb62876e4b2 in Phonon::VLC::VideoWidget::videoWidgetSizeChanged (this=0x7fb6240064e0, width=320, height=240) at /var/tmp/portage/media-libs/phonon-vlc-/work/phonon-vlc-/vlc/videowidget.cpp:364 #13 0x7fb62874acb2 in Phonon::VLC::VideoWidget::qt_metacall (this=0x7fb6240064e0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fb5ec00a800) at /var/tmp/portage/media-libs/phonon-vlc-/work/phonon-vlc-_build/vlc/moc_videowidget.cpp:95 #14 0x7fb64757e13a in QObject::event (this=0x7fb6240064e0, e=value optimized out) at kernel/qobject.cpp:1217 #15 0x7fb647ab6edd in QWidget::event (this=0x7fb6240064e0, event=0x7fb5ec005f00) at kernel/qwidget.cpp:8718 #16 0x7fb647a65c54 in QApplicationPrivate::notify_helper (this=0xfb3a50, receiver=0x7fb6240064e0, e=0x7fb5ec005f00) at kernel/qapplication.cpp:4462 #17 0x7fb647a6a7da in QApplication::notify (this=value optimized out, receiver=0x7fb6240064e0, e=0x7fb5ec005f00) at kernel/qapplication.cpp:4341 #18 0x7fb64929bc16 in KApplication::notify
[Bug 272242] kmail crash while trying to save an attachment
https://bugs.kde.org/show_bug.cgi?id=272242 --- Comment #1 from Marc Schiffbauer marc links2linux de 2011-05-02 14:40:53 --- A little correction: The crash actually happened while clicking a custom shortcut in the save-dialog. And it is reproducable. -- 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 271826] New: kmail does not handle message encoding properly on replies (base64 encoded multipart message)
https://bugs.kde.org/show_bug.cgi?id=271826 Summary: kmail does not handle message encoding properly on replies (base64 encoded multipart message) Product: kmail2 Version: Git (master) Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: Git (master) (using KDE 4.6.2) OS:Linux I just received a multipart mail with following headers: Content-Type: multipart/alternative; boundary=_000_2E0B97FC886742438D4972827280027E32DA419325MAILSERVHwwhl_ And then with multiparts: --_000_2E0B97FC886742438D4972827280027E32DA419325MAILSERVHwwhl_ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 And: --_000_2E0B97FC886742438D4972827280027E32DA419325MAILSERVHwwhl_ Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 When I hit reply, I get garbage instead of german umlauts in the quoted text of the message body: Am Wednesday, 27. April 2011, 09:30:28 schrieben Sie: Marc, Beitrag könnt ihr auf das Konto leisten. Gruà und bis Samstag. Reproducible: Always Steps to Reproduce: 1. Have a multipart, base64 encoded utf8 message in your inbox 2. Hit reply Actual Results: Garbage instead of correct utf8 encoded characters Expected Results: Correct utf8 characters -- 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 271827] New: kontact2 forgets custom key bindings
https://bugs.kde.org/show_bug.cgi?id=271827 Summary: kontact2 forgets custom key bindings Product: kontact Version: GIT (master) Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: GIT (master) (using KDE 4.6.2) OS:Linux You can configure custom key bindings for kmail2 for example. After switching to korganizer and back to kmail, all keybindings are gone. Reproducible: Always Steps to Reproduce: 1. Define shortcut for kmail in kontact (Mark mail read - Y) 2. verify that it works 3. Switch to korganizer within kontact 4. Switch back to kmail 5. Verify again: It does not work anymore -- 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 233671] Only syncs one of several google calendars connected to the same account
https://bugs.kde.org/show_bug.cgi?id=233671 --- Comment #11 from Marc Schiffbauer marc links2linux de 2011-04-09 18:14:57 --- (In reply to comment #10) Unless google makes their implementation of caldav standard compliant, it will never work correctly and reliably with caldav clients. But this is a google calender plugin, not a generic caldav plugin, right? It does not work in Thunderbird (unless you use the gdata plugin) nor does it in the various kde caldav/groupdav clients/akonadi resources. But gcaldaemon [1] for example works very well. I am using it since some years now as a workaround until some part of KDE will be able to sync wit google calendars. (google - gcaldaemon - local ics files - kde) YOU WILL LOSE DATA! Did not happen a single time to me. google doed not correctly support filters and they know pretty well, which makes me think that they are not really interested in it. What kind of filters are you talking about? -Marc [1] http://gcaldaemon.sourceforge.net/ -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 233671] Only syncs one of several google calendars connected to the same account
https://bugs.kde.org/show_bug.cgi?id=233671 --- Comment #13 from Marc Schiffbauer marc links2linux de 2011-04-10 00:30:15 --- (In reply to comment #12) My previous comment #10 was related to the quoted comment #9 about calDAV. I see. Please note that there are two ways of connecting to google calendars: 1) via gdata akonadi resource Has exactly the restriction as described in this whole thread: It can only sunc with the primary calendar, not with secondary ones. This is due to the design of the gadata resource and could relatively easily changed by changing the login method, as done in Mozilla Thunderbird gdata plugin. This sounds promising. Then I would be very happy if this would be done. Are there patches around somewhere already? -Marc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 233671] Only syncs one of several google calendars connected to the same account
https://bugs.kde.org/show_bug.cgi?id=233671 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added CC||m...@links2linux.de --- Comment #8 from Marc Schiffbauer marc links2linux de 2011-04-08 10:18:45 --- Will this be fixed before 4.6 release of kdepim? Would really be awesome to have google calendar sync working in akonadi! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 265190] New: akonadi keeps unlimited number of backups for ical files
https://bugs.kde.org/show_bug.cgi?id=265190 Summary: akonadi keeps unlimited number of backups for ical files Product: Akonadi Version: 1.5.0 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 1.5.0 (using Devel) OS:Linux I have configured four ical Ressources in akonadi. Those four ressources now have 4300 backup files which is a little too much. (in $HOME/.kde4/share/apps/akonadi_ical_resource_*) An ical resource should not create thousends of backup files! Please limit the number of backups to prevent disk bloat. Thanks Reproducible: Always -- 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 265242] New: crash while syncing online IMAP account
https://bugs.kde.org/show_bug.cgi?id=265242 Summary: crash while syncing online IMAP account Product: kmail2 Version: 2.0.89 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application: kmail (2.0.89) KDE Platform Version: 4.6.00 (4.6.0) (Compiled from sources) Qt Version: 4.7.1 Operating System: Linux 2.6.37-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I just had added my second online IMAP account and it started to sync. Then I tried to collapse the first account in the folder view -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fc2aa8f0780 (LWP 3722))] Thread 2 (Thread 0x7fc28f255700 (LWP 3727)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fc29c7d18ed in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fc29c7d19f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fc2a5b04e1c in start_thread () from /lib/libpthread.so.0 #4 0x7fc2a7c8fe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fc2aa8f0780 (LWP 3722)): [KCrash Handler] #6 QCoreApplication::postEvent (receiver=0x5a44b80, event=0x6f138f0, priority=0) at kernel/qcoreapplication.cpp:1133 #7 0x7fc2a1b63c6d in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x6e2e7e0, instance=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6./work/kdepim-common-libs-4.6./libkdepim/agentprogressmonitor.cpp:86 #8 0x7fc2a1b63d4a in KPIM::AgentProgressMonitor::qt_metacall (this=0x757dc20, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffd0dfe7d0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.6./work/kdepim-common-libs-4.6._build/libkdepim/agentprogressmonitor.moc:78 #9 0x7fc2a85d624f in QMetaObject::activate (sender=0x223a490, m=value optimized out, local_signal_index=value optimized out, argv=0x6f138e0) at kernel/qobject.cpp:3272 #10 0x7fc2a40e5795 in Akonadi::AgentManager::instanceStatusChanged (this=value optimized out, _t1=value optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.6./work/kdepimlibs-4.6._build/akonadi/agentmanager.moc:177 #11 0x7fc2a40e9f51 in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged (this=0x223a6f0, identifier=value optimized out, status=0, msg=...) at /var/tmp/portage/kde-base/kdepimlibs-4.6./work/kdepimlibs-4.6./akonadi/agentmanager.cpp:129 #12 0x7fc2a40ec32e in Akonadi::AgentManager::qt_metacall (this=0x223a490, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffd0dfe970) at /var/tmp/portage/kde-base/kdepimlibs-4.6./work/kdepimlibs-4.6._build/akonadi/agentmanager.moc:131 #13 0x7fc2a85d624f in QMetaObject::activate (sender=0x249bf40, m=value optimized out, local_signal_index=value optimized out, argv=0x6f138e0) at kernel/qobject.cpp:3272 #14 0x7fc2a42077db in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged (this=value optimized out, _t1=value optimized out, _t2=0, _t3=value optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.6./work/kdepimlibs-4.6._build/akonadi/agentmanagerinterface.moc:285 #15 0x7fc2a4207c95 in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall (this=0x249bf40, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x7fffd0dff150) at /var/tmp/portage/kde-base/kdepimlibs-4.6./work/kdepimlibs-4.6._build/akonadi/agentmanagerinterface.moc:167 #16 0x7fc2a5d41919 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=..., slotIdx=value optimized out) at qdbusintegrator.cpp:919 #17 0x7fc2a5d4c18f in QDBusCallDeliveryEvent::placeMetaCall (this=0x10043, object=0x6f138f0) at qdbusintegrator_p.h:103 #18 0x7fc2a85d02ee in QObject::event (this=0x249bf40, e=0x5a44b80) at kernel/qobject.cpp:1211 #19 0x7fc2a8ab74ac in QApplicationPrivate::notify_helper (this=0x23b47e0, receiver=0x249bf40, e=0x790d920) at kernel/qapplication.cpp:4445 #20 0x7fc2a8abc8ed in QApplication::notify (this=0x7fffd0dffe60, receiver=0x249bf40, e=0x790d920) at kernel/qapplication.cpp:4324 #21 0x7fc2aa31ffe6 in KApplication::notify (this=0x7fffd0dffe60, receiver=0x249bf40, event=0x790d920) at /var/tmp/portage/kde-base/kdelibs-4.6./work/kdelibs-4.6./kdeui/kernel/kapplication.cpp:311 #22 0x7fc2a85be5eb in QCoreApplication::notifyInternal (this=0x7fffd0dffe60, receiver=0x249bf40, event=0x790d920) at kernel/qcoreapplication.cpp:732 #23 0x7fc2a85c1571 in sendEvent (receiver=0x0,
[Bug 163071] Crash when manipulating or deleting messages from inbox [KMail::FolderJob::msgList, KMAcctImap::ignoreJobsForMessage, KMMoveCommand::execute, KMCommand::slotPostTransfer]
https://bugs.kde.org/show_bug.cgi?id=163071 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added CC|m...@links2linux.de | -- 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 260962] New: Opening an attachement with the predefined Application does not work
https://bugs.kde.org/show_bug.cgi?id=260962 Summary: Opening an attachement with the predefined Application does not work Product: kmail2 Version: unspecified Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: unspecified (using Devel) OS:Linux When clicking on an attachement (.pps file in this case) a dialog is shown with following options: [Save As ...] [Open with 'OpenOffice.org Impress'] [Open With ...] [Cancel] The second Button [Open with 'OpenOffice.org Impress'] does not work. Nothing happens. This used to work in kmail1 and for example clicking [Open With...] and typing 'ooimpress' works too. So I assume it is broken. If the config was wrong (Wrong path to app or something) kmail2 should show an error message or something. But really nothing happens. Reproducible: Always -- 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 [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added CC|m...@links2linux.de | -- 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 258936] Keep original charset option breaks with non ascii characters
https://bugs.kde.org/show_bug.cgi?id=258936 --- Comment #15 from Marc Schiffbauer marc links2linux de 2010-12-21 13:37:37 --- Fix confirmed. Thanks! -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 --- Comment #11 from Marc Schiffbauer marc links2linux de 2010-12-20 13:40:08 --- What exactly did you do to test? Maybe some setting in kmail will cause this? Which locale/language/encoding settings do you use? I have: Menu Settings - configure kmail - E-Mail-Editor - Tab: Charset us-ascii iso-8859-1 utf-8 (locale) utf-8 Menu View - Set encoding - Auto In Email-Editor: Menu Options - Encoding - Default Any elde that might be relevant? Did you really try to reply to that mail and not just display it? Thanks Marc -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 --- Comment #12 from Marc Schiffbauer marc links2linux de 2010-12-20 13:43:59 --- Update: Try to enable following setting: Menu Settings - configure kmail - E-Mail-Editor - Tab: Charset [X] Keep original charset when replying or forwarding (if possible) I had this enabled. When I disable that setting it works as expected. So the (if possible) seems to be broken! -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #6 from Marc Schiffbauer marc links2linux de 2010-12-19 15:53:52 --- After upgrading kdepimlibs again it seems to be fixed now! Thx. -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED | --- Comment #7 from Marc Schiffbauer marc links2linux de 2010-12-19 16:34:29 --- OK, and now on another Mail it did NOT work anymore. So it seems to depend on the message and will not occur on all messages containing non-ascii chars. But the issue is definitely not fixed in current svn (r1207742) Hm, how can re-open the bug? -Marc -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 --- Comment #9 from Marc Schiffbauer marc links2linux de 2010-12-20 03:06:49 --- Created an attachment (id=55090) -- (http://bugs.kde.org/attachment.cgi?id=55090) Example mail inmbox format -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 --- Comment #5 from Marc Schiffbauer marc links2linux de 2010-12-18 17:58:28 --- (In reply to comment #4) I cannot reproduce this. Please reopen if you can using a version greater then svn r1205247. What did you try? For it does not work. MAy some kmail2 setting cause that? I have beta2 and recent svn kdepim running here (apart from that kmail does not build today... but did some days ago) Why are you referring to r1205247? -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO | --- Comment #3 from Marc Schiffbauer marc links2linux de 2010-12-15 13:56:35 --- (In reply to comment #1) Hej Marc, is the mail a multipart message? Ciao, Tobias Please see comment #2 - bug status changed back to UNCONFIRMED (as I am not allowed to set it to NEW) -- 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 258936] kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 --- Comment #2 from Marc Schiffbauer marc links2linux de 2010-12-14 02:15:48 --- Hey Tobias, it does not matter. It happens to plain text messages (plain/text) as well as to multipart messages (text/plain, text/html) for example -- 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 258806] Settings - Configure Kmail - Misc - Mark selected message as read after
https://bugs.kde.org/show_bug.cgi?id=258806 --- Comment #4 from Marc Schiffbauer marc links2linux de 2010-12-14 02:44:20 --- I can confirm that its fixed now, thanks! -- 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 258936] New: kmail2 mangles non ascii character in composer (quoted text on reply)
https://bugs.kde.org/show_bug.cgi?id=258936 Summary: kmail2 mangles non ascii character in composer (quoted text on reply) Product: kmail2 Version: unspecified Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Created an attachment (id=54176) -- (http://bugs.kde.org/attachment.cgi?id=54176) Screenshot showing both: correct display while viewing and wrong display while editing mail Version: unspecified (using Devel) OS:Linux When viewing a message all non-ascii characters look ok. When hitting reply, they will be mangle as can be seen in the attached screenshot. Reproducible: Always Steps to Reproduce: * Sent a mail including non-ascii charcaters like üöä to yourself * Hit reply on that message, see quoted text Actual Results: non-ascii chars will get mangled Expected Results: Correct character display Please see attached screenshot -- 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 258806] New: Settings - Configure Kmail - Misc - Mark selected message as read after
https://bugs.kde.org/show_bug.cgi?id=258806 Summary: Settings - Configure Kmail - Misc - Mark selected message as read after Product: kmail2 Version: 2.0.89 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 2.0.89 (using KDE 4.5.80) OS:Linux The setting described in $summary does now allow a message to NOT be marked as read if selected at all. I disabled that checkbox but a message is marked as read immediately after selecting it in the message list. Enabling the setting with 5 secs for example works though. I only want to mark messages as read after hitting the configured shortcut. Reproducible: Always Steps to Reproduce: * Have the setting diabled. * Select a message in the message list Actual Results: * It will be marked as read immediately Expected Results: * It will NOT be marked as read. -- 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 258806] Settings - Configure Kmail - Misc - Mark selected message as read after
https://bugs.kde.org/show_bug.cgi?id=258806 --- Comment #1 from Marc Schiffbauer marc links2linux de 2010-12-04 17:07:09 --- Typo in first sentence, must be: The setting described in $summary does NOT allow ... -- 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 229398] New: crash after deleting imap account from settings
https://bugs.kde.org/show_bug.cgi?id=229398 Summary: crash after deleting imap account from settings Product: kontact Version: 4.4.1 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application: kontact (4.4.1) KDE Platform Version: 4.4.1 (KDE 4.4.1) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.33-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: This crash occured while kmail was fetching mail from an Cyrus-IMAP account (not dimap!) and then deleting that account from the settings. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Traceback (most recent call last): File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py, line 9, in module from gobject import register File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module import gdb.backtrace ImportError: No module named backtrace [KCrash Handler] #5 0x7ffed0612fa3 in KMMessage::transferInProgress (this=0x5bafa40) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/kmmessage.cpp:271 #6 0x7ffed07f30f3 in KMail::ImapJob::slotGetMessageResult (this=0x5bb14b0, job=0x5bb95b0) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/imapjob.cpp:374 #7 0x7ffed07f31d7 in KMail::ImapJob::qt_metacall (this=0x5bb14b0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffaf6bf720) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1_build/kmail/imapjob.moc:88 #8 0x7ffee6e5901f in QMetaObject::activate (sender=0x5bb95b0, m=value optimized out, local_signal_index=value optimized out, argv=0x7fffaf6bf720) at kernel/qobject.cpp:3285 #9 0x7ffee7ebe419 in KJob::result (this=0x5bb95b0, _t1=0x5bb95b0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1_build/kdecore/kjob.moc:194 #10 0x7ffee7ebe650 in KJob::emitResult (this=0x5bb95b0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdecore/jobs/kjob.cpp:312 #11 0x7ffee5472d91 in KIO::SimpleJob::slotFinished (this=0x5bb95b0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kio/kio/job.cpp:486 #12 0x7ffee5473420 in KIO::TransferJob::slotFinished (this=0x5bb95b0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kio/kio/job.cpp:1058 #13 0x7ffee547a480 in KIO::TransferJob::qt_metacall (this=0x5bb95b0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffaf6bfae0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1_build/kio/jobclasses.moc:367 #14 0x7ffee6e5901f in QMetaObject::activate (sender=0x1a698b0, m=value optimized out, local_signal_index=value optimized out, argv=0x7fffaf6bf720) at kernel/qobject.cpp:3285 #15 0x7ffee54eb4c5 in KIO::SlaveInterface::dispatch (this=0x1a698b0, _cmd=104, rawdata=...) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kio/kio/slaveinterface.cpp:175 #16 0x7ffee54ebeaa in KIO::SlaveInterface::dispatch (this=0x1a698b0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kio/kio/slaveinterface.cpp:91 #17 0x7ffee54e26a6 in KIO::Slave::gotInput (this=0x1a698b0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kio/kio/slave.cpp:324 #18 0x7ffee54e2efe in KIO::Slave::qt_metacall (this=0x1a698b0, _c=QMetaObject::InvokeMetaMethod, _id=235035648, _a=0x7fffaf6bff00) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1_build/kio/slave.moc:82 #19 0x7ffee6e5901f in QMetaObject::activate (sender=0x14f5bf0, m=value optimized out, local_signal_index=value optimized out, argv=0x7fffaf6bf720) at kernel/qobject.cpp:3285 #20 0x7ffee54550bb in KIO::ConnectionPrivate::dequeue (this=0x1a6ccb0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kio/kio/connection.cpp:82 #21 0x7ffee5455cf8 in KIO::Connection::qt_metacall (this=0x14f5bf0, _c=QMetaObject::InvokeMetaMethod, _id=235035648, _a=0xab1b340) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1_build/kio/connection.moc:79 #22 0x7ffee6e55f79 in QObject::event (this=0x14f5bf0, e=0x2a06d60) at kernel/qobject.cpp:1240 #23 0x7ffee731693c in QApplicationPrivate::notify_helper (this=0xe09f30, receiver=0x14f5bf0, e=0x2a06d60) at kernel/qapplication.cpp:4300 #24 0x7ffee731cf8b in QApplication::notify (this=0x7fffaf6c09d0, receiver=0x14f5bf0, e=0x2a06d60) at kernel/qapplication.cpp:4183 #25 0x7ffee83ce2c2 in KApplication::notify (this=0x7fffaf6c09d0, receiver=0x14f5bf0, event=0x2a06d60) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/kernel/kapplication.cpp:302 #26 0x7ffee6e4632b in QCoreApplication::notifyInternal (this=0x7fffaf6c09d0, receiver=0x14f5bf0, event=0x2a06d60) at
[Bug 229419] New: crash while browsing IMAP mails
https://bugs.kde.org/show_bug.cgi?id=229419 Summary: crash while browsing IMAP mails Product: kmail Version: 1.13.1 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application: kmail (1.13.1) KDE Platform Version: 4.4.1 (KDE 4.4.1) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.33-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: this crash happened whlie selection a mail from the message list on an online IMAP folder. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Traceback (most recent call last): File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py, line 9, in module from gobject import register File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module import gdb.backtrace ImportError: No module named backtrace [KCrash Handler] #5 0x7fb0a9ae67b0 in QTreeWidgetItem::addChild (this=0x63323c0, child=0x11766710) at itemviews/qtreewidget.cpp:1882 #6 0x7fb0a9ae6bb3 in QTreeWidgetItem (this=0x11766710, parent=0x63323c0, type=value optimized out) at itemviews/qtreewidget.cpp:1428 #7 0x7fb0aaa6a37f in KMMimePartTreeItem (this=0x63323c0, parent=0x11766710, node=0x168c5b0, description=..., mimetype=..., encoding=..., size=0, revertOrder=false) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/kmmimeparttree.cpp:378 #8 0x7fb0aaa907a2 in partNode::fillMimePartTree (this=0x168c5b0, parentItem=0x63323c0, mimePartTree=0x0, labelDescr=value optimized out, labelCntType=value optimized out, labelEncoding=value optimized out, size=0, revertOrder=97) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/partNode.cpp:549 #9 0x7fb0aaa854df in KMail::ObjectTreeParser::insertAndParseNewChildNode (this=0x7fff33807720, startNode=..., content=value optimized out, cntDesc=value optimized out, append=false, addToTextualContent=false) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/objecttreeparser.cpp:232 #10 0x7fb0aaa876b4 in KMail::ObjectTreeParser::processMessageRfc822Subtype (this=0x7fff33807720, node=0x18fd8a80) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/objecttreeparser.cpp:1582 #11 0x7fb0aaa84d5a in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff33807720, node=0x18fd8a80) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/objecttreeparser.cpp:318 #12 0x7fb0aaa84e4f in KMail::ObjectTreeParser::stdChildHandling (this=0x7fff33807a00, child=0xeacb380) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/objecttreeparser.cpp:1278 #13 0x7fb0aaa850f8 in KMail::ObjectTreeParser::processMultiPartMixedSubtype (this=0x63323c0, node=value optimized out) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/objecttreeparser.cpp:1291 #14 0x7fb0aaa84d5a in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff33807a00, node=0x2690a410) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/objecttreeparser.cpp:318 #15 0x7fb0aa99558e in KMReaderWin::parseMsg (this=0xb80b10, aMsg=0x703b3f0) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/kmreaderwin.cpp:1612 #16 0x7fb0aa98dc68 in KMReaderWin::displayMessage (this=0xb80b10) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/kmreaderwin.cpp:1536 #17 0x7fb0aa98dd5e in KMReaderWin::updateReaderWin (this=0xb80b10) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/kmreaderwin.cpp:1479 #18 0x7fb0aa98f8c0 in KMReaderWin::update (this=0xb80b10, observable=value optimized out) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/kmreaderwin.cpp:904 #19 0x7fb0aaaeebbb in KMail::ISubject::notify (this=0x703b4c0) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/isubject.cpp:33 #20 0x7fb0aa8fc921 in KMMessage::updateBodyPart (this=0x703b3f0, partSpecifier=) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/kmmessage.cpp:3185 #21 0x7fb0aaad7159 in KMail::ImapJob::slotGetMessageResult (this=0x5d03950, job=value optimized out) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1/kmail/imapjob.cpp:435 #22 0x7fb0aaad71d7 in KMail::ImapJob::qt_metacall (this=0x5d03950, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff338083d0) at /var/tmp/portage/kde-base/kmail-4.4.1/work/kmail-4.4.1_build/kmail/imapjob.moc:88 #23 0x7fb0aa19901f in QMetaObject::activate (sender=0x18a704c0, m=value optimized out, local_signal_index=value optimized out, argv=0x43a06e01) at kernel/qobject.cpp:3285 #24 0x7fb0ab20c419 in KJob::result (this=0x7fff33807060, _t1=0x18a704c0) at
[Bug 229423] New: kmail 1.13.1: Online IMAP almost unusable in this version (I did not check other versions)
https://bugs.kde.org/show_bug.cgi?id=229423 Summary: kmail 1.13.1: Online IMAP almost unusable in this version (I did not check other versions) Product: kmail Version: 1.13.1 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 1.13.1 (using KDE 4.4.1) OS:Linux Installed from:Gentoo Packages Hi, I really love kmail being my favorite mail-client for some years now with a dimap-account. Now I have another account which I only want to view like a REAL IMAP account (no offline cache). But this feature seems to be almost unusable in kmail in the current version: IMAP-Server: Cyrus-IMAP 2.2.13 Client: Core2 Duo CPU, 3GB RAM Internet-Connection: 100MBit DOWNstream / 10MBit UPstream Mailbox: ~6500 Messages in INBOX, plus about 25 subfolders (~35000 msg in total) Using mutt: After deleting the header cache, downloading all headers lasts about 2 seconds for INBOX (at startup of mutt). Memory usage: ~14M Using Thunderbird: Getting all headers after creating the account in TB lasts about 5 seconds, after that I am instantly able to read any mail by clicking on it while TB is syncing the Mailbox in background (it does not distinguish between Online and Offline IMAP). Memory usage: ~75M Background syncing the whole mailbox finished in about 15 minutes. Using kmail 1.13.1: Kmail startup, no online IMAP account yet. Memory usage: ~54M After creating the Online IMAP account and selecting its INBOX, this is what happens: (I have the column enabled that shows the number of mails being in a mailbox) * The counter of all messages in the iNBOX starts to increase and finally reaches ~6500 after about 15 seconds * I see a white message screen and after another ~50 seconds kmail displays the message list (while this was happening one CPU core was on 100% and memory usage now is: ~400M (!!) and increasing * now kmail starts a background transfer, as it seems for all mails in that mailbox. WHY? and while the message count is now *DEcreasing* slowly, the consumed memory is dramatically INcreasing (and I have a high CPU load of about 70%). * after 1 minute (15:47): I can select some header line in the message list, but it won't display in the message view * after 3 minutes: the message count has decreased to 5000. Mem usage now: ~800M * after 5 minutes: still no message in the message view (I did not select another one) * after 10 minutes: msg count: 3900, mem usage: 1020M * after 23 minutes: msg count: 1600, mem usage: 1500M * after 30 minutes: msg count: 800, mem usage: 1720M * (starting to close some other applications like akregator or knotes as my machine starts swapping) * after 36 minutes: msg count: 0, mem usage 1920M * now the message list is really empty again. * message list stays empty, background processing tells me that it now is UPLOADING messages to my account? * WTF??? is now eating my whole mailbox? I just wanted to READ mails nothing else... * looking with my webmail account, the message count the in the mailbox is increasing quickly * 40 minutes later: - CPU usage is sown again. - mem usage: still 1880M (!) - message list is shown again - clicking on an item in the list makes the message appear in 0.5 to 2 seconds * after clicking about 4-6 message kmail crashed (reported here https://bugs.kde.org/show_bug.cgi?id=229419) * after the restart, kmail behaves more normal: Seems like the index on disk was still ok after the crash. Messages are shown more quickly now. Almost as I would it expect it or like mutt or Thunderbird did immediately. * Looking at the local disk, the index directory for that imap account is 9.7M in size. * looking at my webmail, my mailbox seems to be to normal. So the main question is: WTF is kmail doing with all the mails in the mailbox after fetching the headers in an ONLINE IMAP account? What is it doing all the time when it is eating all that memory and CPU ressources for about 1.5 hours? Another note: It seems, that if I use that imap account from other clients too long without using kmail, the whole procedure will start again. -- 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 229423] kmail 1.13.1: Online IMAP almost unusable in this version (I did not check other versions)
https://bugs.kde.org/show_bug.cgi?id=229423 --- Comment #2 from Marc Schiffbauer marc links2linux de 2010-03-04 20:29:47 --- Thanks Thomas, after setting every filter to not being used with Online IMAP it works as expected. If this is known to cause such problems, why is this not the default setting? Another thing: What would be nice is a setting per Mail-Account where you can set if filters should be applied at all or not. This way I would have had to set only one switch in the IMAP account instead of touching every single filter (which will be a real PITA if there are al lot of them) And what about the mem usage? Is this really expected? Thx -Marc -- 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 225451] New: kmail: printing of html mails broken
https://bugs.kde.org/show_bug.cgi?id=225451 Summary: kmail: printing of html mails broken Product: kmail Version: 1.13.0 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 1.13.0 (using KDE 4.4.0) OS:Linux Installed from:Gentoo Packages Printing of html mails in kmail is somewhat broken. Printing works in general, but the printed result is unusable. Some elements are being printed, but there is free space of about a half page between a picture and text for example. And pretty much of the text is not printed at all. I guess this may be related to konqueror not being to print webpages: Bug #197824 I wil try to attach that email to 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
[Bug 225451] kmail: printing of html mails broken
https://bugs.kde.org/show_bug.cgi?id=225451 --- Comment #1 from Marc Schiffbauer marc links2linux de 2010-02-04 01:46:57 --- Created an attachment (id=40517) -- (http://bugs.kde.org/attachment.cgi?id=40517) Test-HTML-Mail with images This is a test mail saved via the Save as.. thingy in kmail. Seems I have hit the next bug in kmail: When loading this mail, it looks different from the original (no HTML view anymore??) So this mail may be inappropriate for testing :-( I will create a screenshot now... -- 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 225451] kmail: printing of html mails broken
https://bugs.kde.org/show_bug.cgi?id=225451 --- Comment #2 from Marc Schiffbauer marc links2linux de 2010-02-04 01:55:37 --- Created an attachment (id=40518) -- (http://bugs.kde.org/attachment.cgi?id=40518) Screenshot of Mail This is a screenshot of the mail (the top image is an external reference) -- 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 225452] New: kmail crash after saving mail to disk
https://bugs.kde.org/show_bug.cgi?id=225452 Summary: kmail crash after saving mail to disk Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application: kontact (4.4 rc2) KDE Platform Version: 4.3.98 (KDE 4.3.98 (KDE 4.4 RC3)) (Compiled from sources) Qt Version: 4.6.1 Operating System: Linux 2.6.32-gentoo-r3 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: steps to reproduce: 1. doubleclick a mail so it opens in a separate window (HTML mail in my case, dunno if it MUST be a HTML mail) 2. File - Save as..., save the mail to a file 3. Close the mail window 4. select another mail in the message list 5 . kaboom The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Traceback (most recent call last): File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py, line 9, in module from gobject import register File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module import gdb.backtrace ImportError: No module named backtrace [KCrash Handler] #5 KMail::MessageListView::Widget::getSelectionStats (this=0x147be10, selectedSernums=..., selectedVisibleSernums=value optimized out, allSelectedBelongToSameThread=value optimized out, includeCollapsedChildren=value optimized out) at /var/tmp/portage/kde-base/kmail-4.3.98/work/kmail-4.3.98/kmail/messagelistview/widget.cpp:594 #6 0x7ffb16a498ee in KMMainWidget::updateMessageActions (this=0xe01ad0) at /var/tmp/portage/kde-base/kmail-4.3.98/work/kmail-4.3.98/kmail/kmmainwidget.cpp:4226 #7 0x7ffb16a6009d in KMMainWidget::qt_metacall (this=0xe01ad0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff317f3820) at /var/tmp/portage/kde-base/kmail-4.3.98/work/kmail-4.3.98_build/kmail/kmmainwidget.moc:375 #8 0x7ffb2d62552f in QMetaObject::activate (sender=0x11f95f0, m=value optimized out, local_signal_index=value optimized out, argv=0x0) at kernel/qobject.cpp:3267 #9 0x7ffb2d6221a3 in QObject::event (this=0x11f95f0, e=0xcb3) at kernel/qobject.cpp:1204 #10 0x7ffb2dae25bc in QApplicationPrivate::notify_helper (this=0xa87f80, receiver=0x11f95f0, e=0x7fff317f3fe0) at kernel/qapplication.cpp:4298 #11 0x7ffb2dae9b80 in QApplication::notify (this=0x7fff317f4340, receiver=value optimized out, e=0x7fff317f3fe0) at kernel/qapplication.cpp:3702 #12 0x7ffb2eb89876 in KApplication::notify (this=0x7fff317f4340, receiver=0x11f95f0, event=0x7fff317f3fe0) at /var/tmp/portage/kde-base/kdelibs-4.3.98/work/kdelibs-4.3.98/kdeui/kernel/kapplication.cpp:302 #13 0x7ffb2d61284b in QCoreApplication::notifyInternal (this=0x7fff317f4340, receiver=0x11f95f0, event=0x7fff317f3fe0) at kernel/qcoreapplication.cpp:704 #14 0x7ffb2d63f072 in QCoreApplication::sendEvent (this=0xa96410) at kernel/qcoreapplication.h:215 #15 QTimerInfoList::activateTimers (this=0xa96410) at kernel/qeventdispatcher_unix.cpp:603 #16 0x7ffb2d63bf38 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #17 idleTimerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:231 #18 0x7ffb25f594cd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7ffb25f5ce88 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #20 0x7ffb25f5cfb0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7ffb2d63bc03 in QEventDispatcherGlib::processEvents (this=0xa5a6a0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:412 #22 0x7ffb2db7f64e in QGuiEventDispatcherGlib::processEvents (this=0x13be5a0, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #23 0x7ffb2d6111a2 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #24 0x7ffb2d611574 in QEventLoop::exec (this=0x7fff317f4280, flags=) at kernel/qeventloop.cpp:201 #25 0x7ffb2d61525b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #26 0x0040412d in main (argc=value optimized out, argv=value optimized out) at /var/tmp/portage/kde-base/kontact-4.3.98/work/kontact-4.3.98/kontact/src/main.cpp:221 Possible duplicates by query: bug 223084, bug 219129, bug 218748, bug 218693, bug 217361. Reported using DrKonqi -- 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 222829] New: kontact crashed while starting
https://bugs.kde.org/show_bug.cgi?id=222829 Summary: kontact crashed while starting Product: kontact Version: 4.4 rc1 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application: kontact (4.4 rc1) KDE Platform Version: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)) (Compiled from sources) Qt Version: 4.6.0 Operating System: Linux 2.6.32-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: this crash happened right after startup, I do not know if it was already trying to check for new mail as I did not look onto the screen between clicking kontact icon and seeing the crash reporter -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Traceback (most recent call last): File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.3-gdb.py, line 9, in module from gobject import register File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module import gdb.backtrace ImportError: No module named backtrace [Current thread is 1 (Thread 0x7fa6820e9750 (LWP 26068))] Thread 3 (Thread 0x7fa661f15910 (LWP 11876)): #0 0x7fa67b0d827d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fa65d8120ee in metronom_sync_loop () from /usr/lib64/libxine.so.1 #2 0x7fa67b0d3644 in start_thread () from /lib/libpthread.so.0 #3 0x7fa67f30ed9d in clone () from /lib/libc.so.6 #4 0x in ?? () Thread 2 (Thread 0x7fa65409c910 (LWP 11905)): #0 0x7fa67b0d5d10 in pthread_mutex_lock () from /lib/libpthread.so.0 #1 0x7fa67836354f in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7fa678363a81 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #3 0x7fa678363fb0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fa67fa3a4c6 in QEventDispatcherGlib::processEvents (this=0x2ca36b0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:409 #5 0x7fa67fa0f982 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #6 0x7fa67fa0fd54 in QEventLoop::exec (this=0x7fa65409bfe0, flags=) at kernel/qeventloop.cpp:201 #7 0x7fa67f91c799 in QThread::exec (this=value optimized out) at thread/qthread.cpp:487 #8 0x7fa65da6b170 in ?? () from /usr/lib64/kde4/plugins/phonon_backend/phonon_xine.so #9 0x7fa67f91f1d5 in QThreadPrivate::start (arg=0x30dea90) at thread/qthread_unix.cpp:244 #10 0x7fa67b0d3644 in start_thread () from /lib/libpthread.so.0 #11 0x7fa67f30ed9d in clone () from /lib/libc.so.6 #12 0x in ?? () Thread 1 (Thread 0x7fa6820e9750 (LWP 26068)): [KCrash Handler] #5 0x in ?? () #6 0x7fa681d18723 in Kontact::MainWindow::activateInitialPluginModule (this=value optimized out) at /var/tmp/portage/kde-base/kontact-4.3.90/work/kontact-4.3.90/kontact/src/mainwindow.cpp:290 #7 0x0040495a in KontactApp::newInstance (this=0x7a7dd7a0) at /var/tmp/portage/kde-base/kontact-4.3.90/work/kontact-4.3.90/kontact/src/main.cpp:150 #8 0x7fa680f88f46 in KUniqueApplicationAdaptor::newInstance (this=0x6c89b0, asn_id=value optimized out, args=...) at /var/tmp/portage/kde-base/kdelibs-4.3.90/work/kdelibs-4.3.90/kdeui/kernel/kuniqueapplication.cpp:459 #9 0x7fa680f89586 in KUniqueApplicationAdaptor::qt_metacall (this=0x6c89b0, _c=QMetaObject::InvokeMetaMethod, _id=2144465392, _a=0x7a7dc7e0) at /var/tmp/portage/kde-base/kdelibs-4.3.90/work/kdelibs-4.3.90_build/kdeui/kuniqueapplication_p.moc:81 #10 0x7fa67db463bc in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=..., metaTypes=value optimized out, slotIdx=value optimized out) at qdbusintegrator.cpp:904 #11 0x7fa67db46fff in QDBusConnectionPrivate::activateCall (this=0x62c1f0, object=0x6c89b0, flags=337, msg=...) at qdbusintegrator.cpp:816 #12 0x7fa67db4780e in QDBusConnectionPrivate::activateObject (this=0x62c1f0, node=..., msg=..., pathStartPos=value optimized out) at qdbusintegrator.cpp:1368 #13 0x7fa67db47a98 in QDBusActivateObjectEvent::placeMetaCall (this=0x23bd710) at qdbusintegrator.cpp:1481 #14 0x7fa67fa20bf9 in QObject::event (this=0x7a7dd7a0, e=0x23bd710) at kernel/qobject.cpp:1252 #15 0x7fa67fee2b05 in QApplication::event (this=0x7a7dd7a0, e=0x23bd710) at kernel/qapplication.cpp:2344 #16 0x7fa67fee053c in QApplicationPrivate::notify_helper (this=0x63e210, receiver=0x7a7dd7a0, e=0x23bd710) at kernel/qapplication.cpp:4242 #17 0x7fa67fee8d7a in QApplication::notify (this=0x7a7dd7a0, receiver=value optimized out, e=0x23bd710) at kernel/qapplication.cpp:4125 #18 0x7fa680f81c46 in KApplication::notify (this=0x7a7dd7a0, receiver=0x7a7dd7a0,
[Bug 218912] New: Kontact crash when trying to print a mail [QAction::d_func, QAction::setChecked, KMPrintCommand::execute]
https://bugs.kde.org/show_bug.cgi?id=218912 Summary: Kontact crash when trying to print a mail [QAction::d_func, QAction::setChecked, KMPrintCommand::execute] Product: kontact Version: 4.4 pre Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application: kontact (4.4 pre) KDE Platform Version: 4.3.80 (KDE 4.3.80 (KDE 4.4 Beta1)) (Compiled from sources) Qt Version: 4.6.0 Operating System: Linux 2.6.32-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Trying to print a mail from kontact/kmail produces a crash. Gwenview for example is able to print, although because PyKDE does not build in 4.3.80 I still have pykde4-4.3.4 and printer-applet-4.3.4 as well as system-config-printer-kde-4.3.4 installed on this system. I dunno if this is related somehow. The crash can be reproduced everytime. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Traceback (most recent call last): File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.2-gdb.py, line 9, in module from gobject import register File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module import gdb.backtrace ImportError: No module named backtrace [KCrash Handler] #5 QAction::d_func (this=0x0, b=true) at kernel/qaction.h:67 #6 QAction::setChecked (this=0x0, b=true) at kernel/qaction.cpp:1044 #7 0x7f7a867ea3a0 in KMPrintCommand::execute (this=0x1e7d780) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:1645 #8 0x7f7a867ed03a in KMCommand::slotPostTransfer (this=0x1e7d780, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:290 #9 0x7f7a867f65b3 in KMCommand::qt_metacall (this=0x1e7d780, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffe5906670) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/kmcommands.moc:93 #10 0x7f7a9d43dc73 in QMetaObject::activate (sender=0x1e7d780, m=value optimized out, local_signal_index=value optimized out, argv=0x206d8a0) at kernel/qobject.cpp:3286 #11 0x7f7a867e7c5e in KMCommand::messagesTransfered (this=0x0, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/kmcommands.moc:108 #12 0x7f7a867fbe68 in KMCommand::transferSelectedMsgs (this=0x1e7d780) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:388 #13 0x7f7a867fc088 in KMCommand::slotStart (this=0x1e7d780) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:282 #14 0x7f7a867f6596 in KMCommand::qt_metacall (this=0x1e7d780, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffe59068a0) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/kmcommands.moc:92 #15 0x7f7a9d43dc73 in QMetaObject::activate (sender=0x7d0080, m=value optimized out, local_signal_index=value optimized out, argv=0x206d8a0) at kernel/qobject.cpp:3286 #16 0x7f7a9d44550f in QSingleShotTimer::timerEvent (this=0x7d0080) at kernel/qtimer.cpp:308 #17 0x7f7a9d43a913 in QObject::event (this=0x7d0080, e=0x1) at kernel/qobject.cpp:1216 #18 0x7f7a9c8e853c in QApplicationPrivate::notify_helper (this=0x63ad70, receiver=0x7d0080, e=0x7fffe5907000) at kernel/qapplication.cpp:4242 #19 0x7f7a9c8f0d7a in QApplication::notify (this=0x7fffe5907360, receiver=value optimized out, e=0x7fffe5907000) at kernel/qapplication.cpp:4125 #20 0x7f7a9de19446 in KApplication::notify (this=0x7fffe5907360, receiver=0x7d0080, event=0x7fffe5907000) at /var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdeui/kernel/kapplication.cpp:302 #21 0x7f7a9d42b02b in QCoreApplication::notifyInternal (this=0x7fffe5907360, receiver=0x7d0080, event=0x7fffe5907000) at kernel/qcoreapplication.cpp:704 #22 0x7f7a9d4578e2 in QCoreApplication::sendEvent (this=0x64a190) at kernel/qcoreapplication.h:215 #23 QTimerInfoList::activateTimers (this=0x64a190) at kernel/qeventdispatcher_unix.cpp:603 #24 0x7f7a9d4547a8 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #25 idleTimerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:231 #26 0x7f7a94ff44bd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0x7f7a94ff7e78 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #28 0x7f7a94ff7fa0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0x7f7a9d454473 in QEventDispatcherGlib::processEvents (this=0x60bef0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:407 #30 0x7f7a9c984b3e in QGuiEventDispatcherGlib::processEvents (this=0x0,
[Bug 212190] New: The crash happened when I tried to move some mails from one folder to another (within same dimap sccount)
https://bugs.kde.org/show_bug.cgi?id=212190 Summary: The crash happened when I tried to move some mails from one folder to another (within same dimap sccount) Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.31-gentoo-r4 x86_64 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f5becf63750 (LWP 24007))] Thread 3 (Thread 0x7f5bd1aec910 (LWP 26118)): #0 0x7f5be6cb34fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f5bcdb04f1e in metronom_sync_loop () from /usr/lib64/libxine.so.1 #2 0x7f5be6caf2e7 in start_thread () from /lib/libpthread.so.0 #3 0x7f5bea7115ad in clone () from /lib/libc.so.6 #4 0x in ?? () Thread 2 (Thread 0x7f5bc47b3910 (LWP 26146)): #0 0xff60017b in ?? () #1 0x7f5bc47b2ca0 in ?? () #2 0x7fff2d084782 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7f5becf63750 (LWP 24007)): [KCrash Handler] #5 QTreeModel::index (this=0x12cfa10, item=0x4ac4e90, column=0) at itemviews/qtreewidget.cpp:240 #6 0x7f5bebbae379 in QTreeWidgetPrivate::index (this=0x106f5c0, item=0x4ac4e90) at ../../include/QtGui/private/../../../src/gui/itemviews/qtreewidget_p.h:225 #7 QTreeWidget::visualItemRect (this=0x106f5c0, item=0x4ac4e90) at itemviews/qtreewidget.cpp:2848 #8 0x7f5bd5ccca19 in KMail::FolderView::paintEvent (this=0x106f5c0, e=value optimized out) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/folderview.cpp:2145 #9 0x7f5beb71fe1b in QWidget::event (this=0x106f5c0, event=0x7fff2d065cb0) at kernel/qwidget.cpp:7692 #10 0x7f5beba30936 in QFrame::event (this=0x106f5c0, e=0x7fff2d065cb0) at widgets/qframe.cpp:559 #11 0x7f5bebb4696b in QAbstractItemView::viewportEvent (this=0x106f5c0, event=0x7fff2d065cb0) at itemviews/qabstractitemview.cpp:1476 #12 0x7f5bebb7cf10 in QTreeView::viewportEvent (this=0x106f5c0, event=0x7fff2d065cb0) at itemviews/qtreeview.cpp:1266 #13 0x7f5beadd6c86 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=value optimized out, receiver=0x148d4b0, event=0x7fff2d065cb0) at kernel/qcoreapplication.cpp:726 #14 0x7f5beb6d22ec in QApplicationPrivate::notify_helper (this=0x63fc90, receiver=0x148d4b0, e=0x7fff2d065cb0) at kernel/qapplication.cpp:4061 #15 0x7f5beb6d7bc8 in QApplication::notify (this=0x7fff2d0699a0, receiver=0x148d4b0, e=0x7fff2d065cb0) at kernel/qapplication.cpp:4030 #16 0x7f5bec21b296 in KApplication::notify (this=0x7fff2d0699a0, receiver=0x148d4b0, event=0x7fff2d065cb0) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302 #17 0x7f5beadd78fb in QCoreApplication::notifyInternal (this=0x7fff2d0699a0, receiver=0x148d4b0, event=0x7fff2d065cb0) at kernel/qcoreapplication.cpp:606 #18 0x7f5beb7216a9 in QCoreApplication::sendSpontaneousEvent (this=0x106fae0, pdev=0x748b38, rgn=..., offset=value optimized out, flags=value optimized out, sharedPainter=value optimized out, backingStore=0x71f510) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #19 QWidgetPrivate::drawWidget (this=0x106fae0, pdev=0x748b38, rgn=..., offset=value optimized out, flags=value optimized out, sharedPainter=value optimized out, backingStore=0x71f510) at kernel/qwidget.cpp:5084 #20 0x7f5beb878f45 in QWidgetBackingStore::sync (this=0x71f510) at painting/qbackingstore.cpp:1264 #21 0x7f5beb714142 in QWidgetPrivate::syncBackingStore (this=0x71f1f0) at kernel/qwidget.cpp:1603 #22 0x7f5beb71fcf8 in QWidget::event (this=0x71f060, event=0x278aff0) at kernel/qwidget.cpp:7832 #23 0x7f5beba4859b in QMainWindow::event (this=0x71f060, event=0x278aff0) at widgets/qmainwindow.cpp:1399 #24 0x7f5bec326373 in KXmlGuiWindow::event (this=0x7fff2d0650a0, ev=0x12cfa10) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kdeui/xmlgui/kxmlguiwindow.cpp:131 #25 0x7f5beb6d231c in QApplicationPrivate::notify_helper (this=0x63fc90, receiver=0x71f060, e=0x278aff0) at kernel/qapplication.cpp:4065 #26 0x7f5beb6d7bc8 in QApplication::notify (this=0x7fff2d0699a0, receiver=0x71f060, e=0x278aff0) at kernel/qapplication.cpp:4030 #27 0x7f5bec21b296 in KApplication::notify (this=0x7fff2d0699a0, receiver=0x71f060, event=0x278aff0) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r3/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302 #28 0x7f5beadd78fb in QCoreApplication::notifyInternal (this=0x7fff2d0699a0,
[Bug 211067] New: kontact still crashes when losing network connection (maybe dup of #191589)
https://bugs.kde.org/show_bug.cgi?id=211067 Summary: kontact still crashes when losing network connection (maybe dup of #191589) Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.31-gentoo-r3 x86_64 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 KIO::Slave::deref (this=0x1831470) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kio/kio/slave.cpp:242 #6 0x7f9ce0253899 in KIO::Slave::gotInput (this=0x1831470) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kio/kio/slave.cpp:335 #7 0x7f9ce02559ac in KIO::Slave::qt_metacall (this=0x1831470, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff39ee85d0) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2_build/kio/slave.moc:76 #8 0x7f9ce1d11fc4 in QMetaObject::activate (sender=value optimized out, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x24fc650) at kernel/qobject.cpp:3101 #9 0x7f9ce016f0b7 in KIO::ConnectionPrivate::dequeue (this=0xf59860) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kio/kio/connection.cpp:82 #10 0x7f9ce016f1dd in KIO::Connection::qt_metacall (this=0x1a7d770, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x2834a30) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2_build/kio/connection.moc:73 #11 0x7f9ce1d0eb99 in QObject::event (this=0x1a7d770, e=0x18f7da0) at kernel/qobject.cpp:1099 #12 0x7f9ce25fb31c in QApplicationPrivate::notify_helper (this=0x63fb90, receiver=0x1a7d770, e=0x18f7da0) at kernel/qapplication.cpp:4065 #13 0x7f9ce2600bc8 in QApplication::notify (this=0x7fff39ee8fb0, receiver=0x1a7d770, e=0x18f7da0) at kernel/qapplication.cpp:4030 #14 0x7f9ce31442b6 in KApplication::notify (this=0x7fff39ee8fb0, receiver=0x1a7d770, event=0x18f7da0) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302 #15 0x7f9ce1d008fb in QCoreApplication::notifyInternal (this=0x7fff39ee8fb0, receiver=0x1a7d770, event=0x18f7da0) at kernel/qcoreapplication.cpp:606 #16 0x7f9ce1d00f4f in QCoreApplication::sendEvent (receiver=0x0, event_type=value optimized out, data=0x60a860) at kernel/qcoreapplication.h:213 #17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value optimized out, data=0x60a860) at kernel/qcoreapplication.cpp:1244 #18 0x7f9ce1d25363 in QCoreApplication::sendPostedEvents (s=value optimized out) at kernel/qcoreapplication.h:218 #19 postEventSourceDispatch (s=value optimized out) at kernel/qeventdispatcher_glib.cpp:210 #20 0x7f9cdb27c4b9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #21 0x7f9cdb27faf8 in ?? () from /usr/lib/libglib-2.0.so.0 #22 0x7f9cdb27fcac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #23 0x7f9ce1d24fe6 in QEventDispatcherGlib::processEvents (this=0x60a490, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:328 #24 0x7f9ce26805de in QGuiEventDispatcherGlib::processEvents (this=0x1831470, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #25 0x7f9ce1cff322 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #26 0x7f9ce1cff4bd in QEventLoop::exec (this=0x7fff39ee8ef0, flags=) at kernel/qeventloop.cpp:197 #27 0x7f9ce1d012a9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #28 0x004041ad in main (argc=value optimized out, argv=value optimized out) at /var/tmp/portage/kde-base/kontact-4.3.2/work/kontact-4.3.2/kontact/src/main.cpp:218 Reported using DrKonqi -- 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 185446] replacements for template date/time values not localized on reply
https://bugs.kde.org/show_bug.cgi?id=185446 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Marc Schiffbauer marc links2linux de 2009-10-11 23:25:09 --- I cannot reproduce this here on 4.3.2. So its fixed. Thanks! Closing 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
[Bug 201779] New: crash while kontact is down- and uploading emails in the background through a very slow link
https://bugs.kde.org/show_bug.cgi?id=201779 Summary: crash while kontact is down- and uploading emails in the background through a very slow link Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Application that crashed: kontact Version of the application: 4.3.0 rc3 KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) Qt Version: 4.5.2 Operating System: Linux 2.6.30-gentoo-r2 x86_64 What I was doing when the application crashed: I am currently sitting in the train. Online via a slow GPRS link. Kontact was syncing mails (dimap) in the background (kontact window open, but no focus - I was reading news in akkregator (not embedded in kontact) when this crash happened -- Backtrace: Application: Kontact (kontact), signal: Aborted [KCrash Handler] #5 0x7f7f92b1e645 in raise () from /lib/libc.so.6 #6 0x7f7f92b1fb63 in abort () from /lib/libc.so.6 #7 0x7f7f931a7b75 in qt_message_output () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f7f931a7c90 in qFatal () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f7f7e4f2c17 in KMail::MessageProperty::forget (msgBase=0x1a000e0) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/messageproperty.cpp:180 #10 0x7f7f7e53c8da in ~KMMsgBase (this=0x4694) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/kmmsgbase.cpp:128 #11 0x7f7f7e42c673 in ~KMMessage (this=0x1a000e0) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/kmmessage.cpp:227 #12 0x7f7f7e53d321 in KMMsgList::clear (this=0xecb378, doDelete=true, syncDict=false) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/kmmsglist.cpp:37 #13 0x7f7f7e58a09d in KMFolderMaildir::reallyDoClose (this=0xecb300) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/kmfoldermaildir.cpp:203 #14 0x7f7f7e570763 in KMFolderCachedImap::resetSyncState (this=0xecb300) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/kmfoldercachedimap.cpp:2598 #15 0x7f7f7e555d53 in KMAcctCachedImap::killAllJobs (this=value optimized out, disconnectSlave=value optimized out) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/kmacctcachedimap.cpp:110 #16 0x7f7f7e546b8f in KMail::ImapAccountBase::handleError (this=0x62dba0, errorCode=149, errorm...@0x7fff348f1380, job=0x1847910, conte...@0x7fff348f1580, abortSync=false) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/imapaccountbase.cpp:1022 #17 0x7f7f7e548eb0 in KMail::ImapAccountBase::handleJobError (this=0x62dba0, job=0x1847910, conte...@0x7fff348f1580, abortSync=false) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/imapaccountbase.cpp:374 #18 0x7f7f7e54943d in KMail::ImapAccountBase::handlePutError (this=0x62dba0, job=0x1847910, jd=value optimized out, folder=0xed9650) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/imapaccountbase.cpp:966 #19 0x7f7f7e64cf5e in KMail::CachedImapJob::slotPutMessageResult (this=0x1a5fc10, job=0x1847910) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98/kmail/cachedimapjob.cpp:483 #20 0x7f7f7e64e864 in KMail::CachedImapJob::qt_metacall (this=0x1a5fc10, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff348f17b0) at /var/tmp/portage/kde-base/kmail-4.2.98/work/kmail-4.2.98_build/kmail/cachedimapjob.moc:108 #21 0x7f7f93294dfd in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7f7f936464e2 in KJob::result (this=0x4694, _t1=0x1847910) at /var/tmp/portage/kde-base/kdelibs-4.2.98/work/kdelibs-4.2.98_build/kdecore/kjob.moc:188 #23 0x7f7f936468e3 in KJob::emitResult (this=0x1847910) at /var/tmp/portage/kde-base/kdelibs-4.2.98/work/kdelibs-4.2.98/kdecore/jobs/kjob.cpp:304 #24 0x7f7f91646d6a in KIO::SimpleJob::slotFinished (this=0x1847910) at /var/tmp/portage/kde-base/kdelibs-4.2.98/work/kdelibs-4.2.98/kio/kio/job.cpp:477 #25 0x7f7f9164718b in KIO::TransferJob::slotFinished (this=0x1847910) at /var/tmp/portage/kde-base/kdelibs-4.2.98/work/kdelibs-4.2.98/kio/kio/job.cpp:948 #26 0x7f7f91644e77 in KIO::SimpleJob::slotError (this=0x1847910, err=149, errorte...@0x7fff348f1e30) at /var/tmp/portage/kde-base/kdelibs-4.2.98/work/kdelibs-4.2.98/kio/kio/job.cpp:489 #27 0x7f7f916467f4 in KIO::SimpleJob::qt_metacall (this=0x1847910, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff348f1c70) at /var/tmp/portage/kde-base/kdelibs-4.2.98/work/kdelibs-4.2.98_build/kio/jobclasses.moc:158 #28 0x7f7f9164d205 in KIO::TransferJob::qt_metacall (this=0x4694, _c=18068, _id=6, _a=0x) at /var/tmp/portage/kde-base/kdelibs-4.2.98/work/kdelibs-4.2.98_build/kio/jobclasses.moc:331
[Bug 199358] kontact crash after kmail connection failure
https://bugs.kde.org/show_bug.cgi?id=199358 --- Comment #3 from Marc Schiffbauer marc links2linux de 2009-07-14 11:36:08 --- Kaboom! Here is the BT: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 0 (LWP 32219)] Thread 3 (Thread 0x7f07d6409910 (LWP 32236)): #0 0x7f07f0c949c2 in select () from /lib/libc.so.6 #1 0x7f07f13434e2 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f07f128ba14 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7f07ed3de2e7 in start_thread () from /lib/libpthread.so.0 #4 0x7f07f0c9b5ad in clone () from /lib/libc.so.6 #5 0x in ?? () Thread 2 (Thread 0x7f07d5944910 (LWP 22154)): #0 0x7f07ed3e2279 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f07f128c799 in QWaitCondition::wait () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f07e9e90084 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #3 0x7f07f128ba14 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f07ed3de2e7 in start_thread () from /lib/libpthread.so.0 #5 0x7f07f0c9b5ad in clone () from /lib/libc.so.6 #6 0x in ?? () Thread 1 (Thread 0x7f07f34ed750 (LWP 32219)): [KCrash Handler] #5 KIO::Slave::deref (this=0x20e7a90) at /var/tmp/portage/kde-base/kdelibs-4.2.96/work/kdelibs-4.2.96/kio/kio/slave.cpp:242 #6 0x7f07ef7bc7b6 in KIO::Slave::gotInput (this=0x20e7a90) at /var/tmp/portage/kde-base/kdelibs-4.2.96/work/kdelibs-4.2.96/kio/kio/slave.cpp:335 #7 0x7f07ef7bd898 in KIO::Slave::qt_metacall (this=0x20e7a90, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff6e5e75c0) at /var/tmp/portage/kde-base/kdelibs-4.2.96/work/kdelibs-4.2.96_build/kio/slave.moc:76 #8 0x7f07f1371dfd in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f07ef70296b in KIO::ConnectionPrivate::dequeue (this=0x20ea830) at /var/tmp/portage/kde-base/kdelibs-4.2.96/work/kdelibs-4.2.96/kio/kio/connection.cpp:82 #10 0x7f07ef7036fa in KIO::Connection::qt_metacall (this=0x20eaff0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x19ab1f0) at /var/tmp/portage/kde-base/kdelibs-4.2.96/work/kdelibs-4.2.96_build/kio/connection.moc:73 #11 0x7f07f136e991 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4 #12 0x7f07f1c36c2d in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #13 0x7f07f1c3e65a in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #14 0x7f07f2771a41 in KApplication::notify (this=0x7fff6e5e8000, receiver=0x20eaff0, event=0x2729930) at /var/tmp/portage/kde-base/kdelibs-4.2.96/work/kdelibs-4.2.96/kdeui/kernel/kapplication.cpp:302 #15 0x7f07f135fcfb in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #16 0x7f07f136063e in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/qt4/libQtCore.so.4 #17 0x7f07f1385203 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #18 0x7f07eadb2dd9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7f07eadb6528 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #20 0x7f07eadb66ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7f07f1384e9f in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7f07f1cbd0cf in ?? () from /usr/lib64/qt4/libQtGui.so.4 #23 0x7f07f135e6a2 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7f07f135e83c in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #25 0x7f07f13608dc in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #26 0x00403f05 in main (argc=1, argv=0x7fff6e5e8518) at /var/tmp/portage/kde-base/kontact-4.2.96/work/kontact-4.2.96/kontact/src/main.cpp:218 -- 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 199358] kontact crash after kmail connection failure
https://bugs.kde.org/show_bug.cgi?id=199358 --- Comment #2 from Marc Schiffbauer marc links2linux de 2009-07-13 14:39:04 --- Waiting for the next crash it seems it is not so reproducable than I thought it is... As soon as it happens again I will post the backtrace. -- 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 199358] New: kontact crash after kmail connection failure
https://bugs.kde.org/show_bug.cgi?id=199358 Summary: kontact crash after kmail connection failure Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 4.2.95 (using Devel) OS:Linux Installed from:Compiled sources Whenever kmail within kontact tries to fetch mail (dimap) and the connection fails, a dialog pops up telling the user about the connection failure. After clicking ok then, kontact crashes This is reproducable here. -- 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 163071] Crash when deleting messages from inbox
https://bugs.kde.org/show_bug.cgi?id=163071 --- Comment #43 from Marc Schiffbauer marc links2linux de 2009-07-02 14:43:03 --- Ok, fixed for me on 4.2.95 -- 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 163071] Crash when deleting messages from inbox
https://bugs.kde.org/show_bug.cgi?id=163071 --- Comment #42 from Marc Schiffbauer marc links2linux de 2009-06-30 14:06:11 --- If this is really a duplicate of #198302, then its NOT fixed in 4.2.91 ... -- 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 198301] New: mail view part of main window not updated after deleting a mail from the list
https://bugs.kde.org/show_bug.cgi?id=198301 Summary: mail view part of main window not updated after deleting a mail from the list Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 4.2.91 (using Devel) OS:Linux Installed from:Compiled sources Hi, I just noticed that if I am viewing a mail, in the mail view part of kmails main window (within kontact) and I hit the del button to delete that message: * the mail is being removed from the list * cursor/focus is advanced to the next mail * BUT view part still shows deleted mail I then have to switch to anothe rmail and back to view the next mail after the deleted 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 198302] New: kmail crashes when deleting mails from online IMAP account
https://bugs.kde.org/show_bug.cgi?id=198302 Summary: kmail crashes when deleting mails from online IMAP account Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@links2linux.de Version: 4.2.91 (using Devel) OS:Linux Installed from:Compiled sources This crash seems to be timing related, but I can reproduce it like that: * have an IMAP account with some mails (at least 100 or so) * place focus in the list view (above mail view part) * have the simple list view (old threading style by date, no grouping by month or something) * now mark many mails by using shift-cursordown, hold down the button for 3 seconds so the cursor runs * then hit del-button quickly before kmail can update the mail view with the current mail - kaboom! Application: Kontact (kontact), signal: Segmentation fault [Current thread is 0 (LWP 17284)] Thread 2 (Thread 0x7f11ad444910 (LWP 17286)): #0 0x7f11c21114fd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f11c5efe777 in QWaitCondition::wait () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f11c5ef5959 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7f11c5efda19 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f11c210d2e7 in start_thread () from /lib/libpthread.so.0 #5 0x7f11c590d38d in clone () from /lib/libc.so.6 #6 0x in ?? () Thread 1 (Thread 0x7f11c818d750 (LWP 17284)): [KCrash Handler] #5 0x7f11b1603b4b in ?? () from /usr/lib64/libkmailprivate.so.4 #6 0x7f11b14a7ad5 in ?? () from /usr/lib64/libkmailprivate.so.4 #7 0x7f11b15c55ff in KMMoveCommand::execute () from /usr/lib64/libkmailprivate.so.4 #8 0x7f11b15ab442 in KMCommand::slotPostTransfer () from /usr/lib64/libkmailprivate.so.4 #9 0x7f11b15b50de in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #10 0x7f11b15c7295 in KMMoveCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #11 0x7f11c5fe3e3d in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #12 0x7f11b15a868e in KMCommand::messagesTransfered () from /usr/lib64/libkmailprivate.so.4 #13 0x7f11b15c4048 in KMCommand::transferSelectedMsgs () from /usr/lib64/libkmailprivate.so.4 #14 0x7f11b15c4276 in KMCommand::slotStart () from /usr/lib64/libkmailprivate.so.4 #15 0x7f11b15b50f2 in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #16 0x7f11b15c7295 in KMMoveCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #17 0x7f11c5fe3e3d in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #18 0x7f11c5fea2ef in ?? () from /usr/lib64/qt4/libQtCore.so.4 #19 0x7f11c5fe04e3 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4 #20 0x7f11c68c588d in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #21 0x7f11c68ce28a in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #22 0x7f11c744385b in KApplication::notify () from /usr/lib64/libkdeui.so.5 #23 0x7f11c5fd1a1b in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7f11c5ff9e9e in ?? () from /usr/lib64/qt4/libQtCore.so.4 #25 0x7f11c5ff6f5d in ?? () from /usr/lib64/qt4/libQtCore.so.4 #26 0x7f11bfae1e29 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0x7f11bfae5498 in ?? () from /usr/lib/libglib-2.0.so.0 #28 0x7f11bfae565c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0x7f11c5ff6ebf in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #30 0x7f11c694bc8f in ?? () from /usr/lib64/qt4/libQtGui.so.4 #31 0x7f11c5fd03d2 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #32 0x7f11c5fd0565 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #33 0x7f11c5fd25fc in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #34 0x004049f9 in _start () -- 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 170352] custom font in message list ignored by date column
https://bugs.kde.org/show_bug.cgi?id=170352 Marc Schiffbauer m...@links2linux.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED -- 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 72308] Delayed update after switching sender/receiver
http://bugs.kde.org/show_bug.cgi?id=72308 Marc Schiffbauer marc links2linux de changed: What|Removed |Added CC||m...@links2linux.de --- Comment #4 from Marc Schiffbauer marc links2linux de 2009-01-30 12:04:42 --- This bug is present in kmail 1.11.0 (in KDE 4.2 final) Please re-open this bug. -- Configure bugmail: http://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 170352] New: custom font in message list ignored by date column
http://bugs.kde.org/show_bug.cgi?id=170352 Summary: custom font in message list ignored by date column Product: kmail Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using KDE 4.1.1) OS:Linux Installed from:Ubuntu Packages Settings a custom font for the message list works for all columns except the date column. And the localization of the date does not work, too (I have a german environment and the date is presented in english form) See http://linuxcc.de/kde-bugs/kontact/shot18.png -- Configure bugmail: http://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
