[kmail2] [Bug 484478] Cannot open configure kmail
https://bugs.kde.org/show_bug.cgi?id=484478 --- Comment #1 from ray --- It works for me i don't recall i fixed it some how adding fonts or maybe just fixed. Probably report for close :) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484478] New: Cannot open configure kmail
https://bugs.kde.org/show_bug.cgi?id=484478 Bug ID: 484478 Summary: Cannot open configure kmail Classification: Applications Product: kmail2 Version: 6.0.1 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: r...@deepmail.cc Target Milestone: --- Cannot open configure kmail... from settings. After click kmail freeze. The only clue is this from terminal OpenType support missing for "Noto Sans", script 9 OpenType support missing for "Noto Sans", script 10 OpenType support missing for "FreeSerif", script 10 probably all my system fonts OpenType support missing for " some font ", script 10 and at end OpenType support missing for "", script 10 and this line is forever just OpenType support missing for "", script 10 OpenType support missing for "", script 10 OpenType support missing for "", script 10 OpenType support missing for "", script 10 OpenType support missing for "", script 10 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483475] ugly scaling or rendering
https://bugs.kde.org/show_bug.cgi?id=483475 --- Comment #3 from ray --- Created attachment 167118 --> https://bugs.kde.org/attachment.cgi?id=167118=edit better sample -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483475] ugly scaling or rendering
https://bugs.kde.org/show_bug.cgi?id=483475 --- Comment #2 from ray --- Created attachment 167117 --> https://bugs.kde.org/attachment.cgi?id=167117=edit akregator -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483475] ugly scaling or rendering
https://bugs.kde.org/show_bug.cgi?id=483475 --- Comment #1 from ray --- Same problem with akregator -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483475] New: ugly scaling or rendering
https://bugs.kde.org/show_bug.cgi?id=483475 Bug ID: 483475 Summary: ugly scaling or rendering Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: r...@deepmail.cc Target Milestone: --- Created attachment 167115 --> https://bugs.kde.org/attachment.cgi?id=167115=edit screen Since plasma 6 (wayland) kmail having ugly scaling or rendering on mail content view or edit. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #48 from Ray --- believe it or not, but as I mentioned - upgrading networkmanager (from lunar) is a valid workaround. I've done this on several machines by now, other people who tried didn't restart networkmanager or their machines or something else. But probably we should mention this on a developer channel, but I didn't dare to do that. What do you think? It looks like we've found a workaround. Installing network-manager from lunar repository does the trick Here you can read why this works: https://discuss.kde.org/t/on-kde-neon-kmail-and-whole-akonadi-stays-offline-after-suspend-or-when-reestablishing-a-network-connection/1425/5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #45 from Ray --- are you sure you restarted networkmanager and kde pim after installing lunars networkmanager? I've tested in on 2 machines, and it's woking since then. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #39 from Ray --- It looks like we've found a workaround. Installing network-manager from lunar repository does the trick Here you can read why this works: https://discuss.kde.org/t/on-kde-neon-kmail-and-whole-akonadi-stays-offline-after-suspend-or-when-reestablishing-a-network-connection/1425/5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #38 from Ray --- Trying KDE Discuss first: https://discuss.kde.org/t/on-kde-neon-kmail-and-whole-akonadi-stays-offline-after-suspend-or-when-reestablishing-a-network-connection/1425 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #37 from Ray --- how about trying the matrix developer-channel? - I know, it's not a support channel, but it looks like no dev is watching this thread -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #34 from Ray --- bug is still killing my nerves on 5.27.5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #25 from Ray --- I was on suspend a couple of times, and akonadi/kmail is still working. Is this just a coicidence? Operating System: KDE neon 5.27.4 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #20 from Ray --- (In reply to Ray from comment #19) > Seems to be resolved?! I don't know what did it though > i'm on 5.27.3 (22.03.) > can someone confirm? sorry - somehow it worked once, but doesn't anymore. Don't know why. I changed network connections very often today, maybe it has something to do with that -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #19 from Ray --- Seems to be resolved?! I don't know what did it though i'm on 5.27.3 (22.03.) can someone confirm? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #16 from Ray --- nmcli connection up id "SSID" DOES create /org/freedesktop/NetworkManager/ActiveConnection/ - but following a different number. Akonadi was looking for /org/freedesktop/NetworkManager/ActiveConnection/4 but nmcli connection up id "SSID" created /org/freedesktop/NetworkManager/ActiveConnection/6 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #15 from Ray --- org.freedesktop.NetworkManager.sleep-wake no It's supposed to be that way - "put NetworkManager to sleep or wake it up (should only be used by system power management" But probably system power management doesn't set this state? Going offline (networkmanager) and online again makes akonadi and kmail think networkmanager is offline too -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #14 from Ray --- nmcli general permissions PERMISSIONVALUE org.freedesktop.NetworkManager.checkpoint-rollbackauth org.freedesktop.NetworkManager.enable-disable-connectivity-check yes org.freedesktop.NetworkManager.enable-disable-network yes org.freedesktop.NetworkManager.enable-disable-statistics yes org.freedesktop.NetworkManager.enable-disable-wifiyes org.freedesktop.NetworkManager.enable-disable-wimax yes org.freedesktop.NetworkManager.enable-disable-wwanyes org.freedesktop.NetworkManager.network-controlyes org.freedesktop.NetworkManager.reload auth org.freedesktop.NetworkManager.settings.modify.global-dns auth org.freedesktop.NetworkManager.settings.modify.hostname auth org.freedesktop.NetworkManager.settings.modify.ownyes org.freedesktop.NetworkManager.settings.modify.system yes org.freedesktop.NetworkManager.sleep-wake no org.freedesktop.NetworkManager.wifi.scan yes org.freedesktop.NetworkManager.wifi.share.openyes org.freedesktop.NetworkManager.wifi.share.protected yes maybe that's the problem??? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #9 from Ray --- (In reply to Ray from comment #7) > Same here, closing kontact/kmail and akonadictl restart brings it back > online. > > "Object does not exist at path > “/org/freedesktop/NetworkManager/ActiveConnection/" > > Has anybody tried a KDE Neon fresh install (not upgraded to stable from Beta > or RC state)? same with fresh installed KDE Neon -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #8 from Ray --- Does this give us a hint maybe? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010576 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #7 from Ray --- Same here, closing kontact/kmail and akonadictl restart brings it back online. "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/" Has anybody tried a KDE Neon fresh install (not upgraded to stable from Beta or RC state)? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 Ray changed: What|Removed |Added CC||tab...@mailbox.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 354406] KMail -> Tools -> Find messages does not work (always zero hits)
https://bugs.kde.org/show_bug.cgi?id=354406 ray <r...@eng-int.co.uk> changed: What|Removed |Added CC||r...@eng-int.co.uk --- Comment #4 from ray <r...@eng-int.co.uk> --- Also with openSUSE-Tumbleweed-20160921 KMail Version 5.3.0 (QtWebEngine) Using: KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 298399] 'Customize accounts order' randomly fails if folders are sorted manually
https://bugs.kde.org/show_bug.cgi?id=298399 Mario Ray Mahardhika leledumbo_c...@yahoo.co.id changed: What|Removed |Added CC||leledumbo_c...@yahoo.co.id --- Comment #10 from Mario Ray Mahardhika leledumbo_c...@yahoo.co.id --- I just encounter this issue. It happens after mariadb upgrade that forces me to delete ~/.local/share/akonadi so that kmail will recreate the folder and its contents again. I only have 3 accounts in KMail so it's easily spotted. I add a screenshot to the attachment list. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 298399] 'Customize accounts order' randomly fails if folders are sorted manually
https://bugs.kde.org/show_bug.cgi?id=298399 --- Comment #11 from Mario Ray Mahardhika leledumbo_c...@yahoo.co.id --- Created attachment 87934 -- https://bugs.kde.org/attachment.cgi?id=87934action=edit Inconsistent account order -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 335415] New: segfault when replying to mail
https://bugs.kde.org/show_bug.cgi?id=335415 Bug ID: 335415 Summary: segfault when replying to mail Classification: Unclassified Product: kmail2 Version: 4.13 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sebastien-...@orniz.org Application: kmail (4.13) KDE Platform Version: 4.13.0 Qt Version: 4.8.6 Operating System: Linux 3.13.0-26-generic x86_64 Distribution: Ubuntu 14.04 LTS -- Information about the crash: When doing a reply to a mail (in this attached case a reply to all), KDE segfaults. When relaunching it, compose window is open, without my signature. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fb075766800 (LWP 455))] Thread 5 (Thread 0x7fb04bd64700 (LWP 467)): #0 0x7fb06ab56f52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb06ab570ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb0734627be in QEventDispatcherGlib::processEvents (this=0x7fb0440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #3 0x7fb0734340af in QEventLoop::processEvents (this=this@entry=0x7fb04bd63da0, flags=...) at kernel/qeventloop.cpp:149 #4 0x7fb0734343a5 in QEventLoop::exec (this=this@entry=0x7fb04bd63da0, flags=...) at kernel/qeventloop.cpp:204 #5 0x7fb073330c5f in QThread::exec (this=this@entry=0x1676ea0) at thread/qthread.cpp:537 #6 0x7fb073415823 in QInotifyFileSystemWatcherEngine::run (this=0x1676ea0) at io/qfilesystemwatcher_inotify.cpp:265 #7 0x7fb0732f in QThreadPrivate::start (arg=0x1676ea0) at thread/qthread_unix.cpp:349 #8 0x7fb070394182 in start_thread (arg=0x7fb04bd64700) at pthread_create.c:312 #9 0x7fb072ad330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7fb0488d1700 (LWP 490)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb06707581d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb067075859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb070394182 in start_thread (arg=0x7fb0488d1700) at pthread_create.c:312 #4 0x7fb072ad330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fb00366e700 (LWP 494)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb066db620d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb0670a4fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb070394182 in start_thread (arg=0x7fb00366e700) at pthread_create.c:312 #4 0x7fb072ad330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fb002a6d700 (LWP 497)): #0 0x7fb06ab9862d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb06ab98989 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb06ab56699 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb06ab56f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb06ab570ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb0734627be in QEventDispatcherGlib::processEvents (this=0x7faff40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7fb0734340af in QEventLoop::processEvents (this=this@entry=0x7fb002a6cde0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fb0734343a5 in QEventLoop::exec (this=this@entry=0x7fb002a6cde0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fb073330c5f in QThread::exec (this=optimized out) at thread/qthread.cpp:537 #9 0x7fb0732f in QThreadPrivate::start (arg=0x1fed960) at thread/qthread_unix.cpp:349 #10 0x7fb070394182 in start_thread (arg=0x7fb002a6d700) at pthread_create.c:312 #11 0x7fb072ad330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fb075766800 (LWP 455)): [KCrash Handler] #6 0x7fb073bbb523 in QTextLayout::position (this=this@entry=0x9b8bfc0) at text/qtextlayout.cpp:876 #7 0x7fb073bf9277 in QTextDocumentLayoutPrivate::layoutBlock (this=this@entry=0x99cbde0, bl=..., blockPosition=blockPosition@entry=1864, blockFormat=..., layoutStruct=layoutStruct@entry=0x7fff5b76a340, layoutFrom=layoutFrom@entry=190, layoutTo=layoutTo@entry=191, previousBlockFormat=previousBlockFormat@entry=0x7fff5b76a0a0) at text/qtextdocumentlayout.cpp:2572 #8 0x7fb073c01603 in QTextDocumentLayoutPrivate::layoutFlow (this=this@entry=0x99cbde0, it=..., layoutStruct=layoutStruct@entry=0x7fff5b76a340,
[kmail2] [Bug 332897] [regression] cannot send to distribution list
https://bugs.kde.org/show_bug.cgi?id=332897 --- Comment #5 from ray-ven gor...@gmail.com --- nope... Not on 4.13. I can send to its members (select people in the list and send works), but not to the list itself but maybe it's supposed to work this way? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 332897] [regression] cannot send to distribution list
https://bugs.kde.org/show_bug.cgi?id=332897 --- Comment #3 from ray-ven gor...@gmail.com --- awesome - I'll keep you up to date when packages arrive in proposed -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 332897] New: [regression] cannot send to distribution list
https://bugs.kde.org/show_bug.cgi?id=332897 Bug ID: 332897 Summary: [regression] cannot send to distribution list Classification: Unclassified Product: kmail2 Version: 4.12.97 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: gor...@gmail.com if I pick a distribution list for sending, kmail replies cannot send to list@hostname Reproducible: Always Steps to Reproduce: 1. type in email adresses in kmail to field 2. click save as list 3. create new email and set to to new distribution list Actual Results: emails aren't being sent Expected Results: sending mail to all recipients of my distribution list was closed in https://bugs.kde.org/show_bug.cgi?id=223034 now open again -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 332345] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=332345 ray-ven gor...@gmail.com changed: What|Removed |Added CC||gor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 332345] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=332345 --- Comment #2 from ray-ven gor...@gmail.com --- Created attachment 85642 -- https://bugs.kde.org/attachment.cgi?id=85642action=edit New crash information added by DrKonqi kontact (4.12.3) on KDE Platform 4.12.90 using Qt 4.8.6 - What I was doing when the application crashed: I started Kontact (after restart, nothing else started) -- Backtrace (Reduced): #6 0x7faa79467992 in QObject::connect (sender=0x7faa13df46f8 vtable for KMailPlugin+24, signal=signal@entry=0x7faa7b3cd44e 2destroyed(), receiver=receiver@entry=0x2472a30, method=method@entry=0x7faa7b3cd43d 1partDestroyed(), type=type@entry=Qt::AutoConnection) at kernel/qobject.cpp:2546 #7 0x7faa7b3cadc6 in connect (atype=Qt::AutoConnection, amember=0x7faa7b3cd43d 1partDestroyed(), asignal=0x7faa7b3cd44e 2destroyed(), asender=optimized out, this=0x2472a30) at /usr/include/qt4/QtCore/qobject.h:339 #8 KontactInterface::Plugin::part (this=0x2472a30) at ../../kontactinterface/plugin.cpp:195 #9 0x7faa7af923a1 in Kontact::MainWindow::selectPlugin (this=0x21a3ec0, plugin=0x2472a30) at ../../../kontact/src/mainwindow.cpp:815 #10 0x7faa7af9000c in Kontact::MainWindow::loadSettings (this=this@entry=0x21a3ec0) at ../../../kontact/src/mainwindow.cpp:984 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 332053] New: kmail: sending via gmail without sent folder set returns item query returns empty result set
https://bugs.kde.org/show_bug.cgi?id=332053 Bug ID: 332053 Summary: kmail: sending via gmail without sent folder set returns item query returns empty result set Classification: Unclassified Product: kmail2 Version: 4.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gor...@gmail.com I've multiple identidies (only in kmail :-D ), I'm using gmail (google). Google fills the sent folder on it's own, and sent mails cannot be moved to sent folder after sending, so i uncheck folder for sent mails in the identities dialog. Now when sending mail, kmail says it wont send: mail not sent item query returns empty result set Unfortunately kmail sent the mail, and it is shown in googles sent folder. This is a fully new userprofile with freshly set up akonadi. Have this problem quite a while now. Reproducible: Always Steps to Reproduce: 1. Use gmail 2. uncheck sent mail in identity 3. send mail Actual Results: annoying failure messages Expected Results: mail sent successfully -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 327779] redirect overwrites To:
https://bugs.kde.org/show_bug.cgi?id=327779 --- Comment #4 from Sébastien Le Ray sebastien-...@orniz.org --- Created attachment 85444 -- https://bugs.kde.org/attachment.cgi?id=85444action=edit Attempt to fix (untested) Hi I've just been hit by this bug too… Looking at the source it seems that MessageComposer::MessageFactory::createRedirect intentionaly add the to header as a copy of the Resent-To (l.536) without any reason (because X-KMail-Recipients will be used at transport level so it'll get ignored). I've no time to set up a dev environment on my box right now but I guess attached patch should fix it, it handle the To header the same way other headers are handled. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 327779] redirect overwrites To:
https://bugs.kde.org/show_bug.cgi?id=327779 Sébastien Le Ray sebastien-...@orniz.org changed: What|Removed |Added Attachment #85444|0 |1 is obsolete|| --- Comment #5 from Sébastien Le Ray sebastien-...@orniz.org --- Created attachment 85445 -- https://bugs.kde.org/attachment.cgi?id=85445action=edit Unified diff patch Sorry, missed the -u on previous one -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 327779] redirect overwrites To:
https://bugs.kde.org/show_bug.cgi?id=327779 Sébastien Le Ray sebastien-...@orniz.org changed: What|Removed |Added Attachment #85445|0 |1 is obsolete|| --- Comment #7 from Sébastien Le Ray sebastien-...@orniz.org --- Created attachment 85461 -- https://bugs.kde.org/attachment.cgi?id=85461action=edit Final version (tested) I took time to set up an environment and looked deeper at the sources spec… It seems that the way it handles redirects does not respect the spec. The Cc and Bcc are added to Resent-(B)Cc headers which is not what the spec says. Here is a more complete and correct patch. First it avoids the double To: header introduced in the previous one, ensure to clean up any Resent-* headers and modifies akonadisender to handle Resent-(To|Cc|Bcc) properly (even if Kmail doesn't use the last two headers). The X-Kmail-Recipients is then useless in createRedirect. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323018] New: gmail replies it won't save my sent mail: f...@bar.com: save failed, server replied: A000*** BAD could not parse command
https://bugs.kde.org/show_bug.cgi?id=323018 Bug ID: 323018 Summary: gmail replies it won't save my sent mail: f...@bar.com: save failed, server replied: A000*** BAD could not parse command Classification: Unclassified Product: kmail2 Version: 4.11 rc1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: gor...@gmail.com I'm using disconnected imap. Sent-folder is set up correctly. I red in another forum that this is a google issue with imap handling. Reproducible: Always Steps to Reproduce: 1. send a mail via gmail 2. 3. Actual Results: it looks like the mail IS saved despite it says it's not Expected Results: no error message Happend with 4.10 too. -- 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
[akregator] [Bug 317421] New: If Akregator has opened many Tabs and refreshes lists on startup, some WWAN connections break
https://bugs.kde.org/show_bug.cgi?id=317421 Bug ID: 317421 Summary: If Akregator has opened many Tabs and refreshes lists on startup, some WWAN connections break Classification: Unclassified Product: akregator Version: 4.10.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gor...@gmail.com Well, not sure if this is a wish or kind of a bug, but it seems (tested with different devices) that opening akregator, with having saved many tabs in it, breaks some internetconnections due tue many connections. It won't happen with landline connections, but is totally reproducable while having a wwan connection. Of course, this is a provider thing, but could it be, that akregator is kind of aggressive in building up connections? hope this helps somehow -- 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
[akregator] [Bug 317421] If Akregator has opened many Tabs and refreshes lists on startup, some WWAN connections break
https://bugs.kde.org/show_bug.cgi?id=317421 ray-ven gor...@gmail.com changed: What|Removed |Added Platform|Other |Ubuntu Packages Latest Commit||an -- 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 311910] New: kontact segfaults on exit
https://bugs.kde.org/show_bug.cgi?id=311910 Bug ID: 311910 Severity: crash Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact segfaults on exit Classification: Unclassified OS: Linux Reporter: gor...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.3 Operating System: Linux 3.5.0-19-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: Just closing kontact - happens even after fresh restart. Happens every time The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f78d086a7c0 (LWP 23195))] Thread 4 (Thread 0x7f78c8adc700 (LWP 23196)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f78e1de1b2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f78e1de1c39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f78dd32be9a in start_thread (arg=0x7f78c8adc700) at pthread_create.c:308 #4 0x7f78e2b0ccbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f78c81db700 (LWP 23197)): #0 0x7f78e2b01303 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f78dce5cd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78dce5cea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78e3281c16 in QEventDispatcherGlib::processEvents (this=0x7f78c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f78e32522bf in QEventLoop::processEvents (this=this@entry=0x7f78c81dadc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f78e3252548 in QEventLoop::exec (this=0x7f78c81dadc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f78e3153b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f78e3156aec in QThreadPrivate::start (arg=0x227d620) at thread/qthread_unix.cpp:338 #8 0x7f78dd32be9a in start_thread (arg=0x7f78c81db700) at pthread_create.c:308 #9 0x7f78e2b0ccbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7f787a86b700 (LWP 23200)): #0 0x7f78e2b01303 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f78dce5cd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78dce5cea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78e3281c16 in QEventDispatcherGlib::processEvents (this=0x7f78740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f78e32522bf in QEventLoop::processEvents (this=this@entry=0x7f787a86ad90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f78e3252548 in QEventLoop::exec (this=0x7f787a86ad90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f78e3153b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f78e32329af in QInotifyFileSystemWatcherEngine::run (this=0x28f5530) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f78e3156aec in QThreadPrivate::start (arg=0x28f5530) at thread/qthread_unix.cpp:338 #9 0x7f78dd32be9a in start_thread (arg=0x7f787a86b700) at pthread_create.c:308 #10 0x7f78e2b0ccbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f78d086a7c0 (LWP 23195)): [KCrash Handler] #6 0x0001 in ?? () #7 0x0040337e in qDeleteAllQListKMainWindow*::const_iterator (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322 #8 qDeleteAllQListKMainWindow* (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330 #9 main (argc=1, argv=0x7fff505e1218) at ../../../kontact/src/main.cpp:220 This bug may be a duplicate of or related to bug 288141. Possible duplicates by query: bug 307373, bug 307140, bug 305591, bug 304826, bug 300135. Reported using DrKonqi -- 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 289097] error Unable to fetch item from backend when entering IMAP folder
https://bugs.kde.org/show_bug.cgi?id=289097 --- Comment #54 from ray-ven gor...@gmail.com --- I had this problem just when starting kontact or starting the korganizer module in kontact. It was totaly gone after i moved from webdav calendar and contacts to the designated google calender akonadi-plugin. -- 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 196977] Knotes: Positions of notes are not remembered
https://bugs.kde.org/show_bug.cgi?id=196977 --- Comment #5 from Ray codemon...@interthingy.net --- Okay, first boot on my home machine and I can confirm that the problem is still happening with 4.8.5. I left 4 notes open when I shut-down, with different content, colors, shapes and sizes. Content and colors were the same on the new boot but sizes and positions were shuffled around. -- 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 196977] Knotes: Positions of notes are not remembered
https://bugs.kde.org/show_bug.cgi?id=196977 --- Comment #4 from Ray codemon...@interthingy.net --- I forgot to mention earlier: my laptop is running KDE 4.6.5 My home system is running KNotes 4.8.5 on KDE 4.8.5 (Fedora 16). Again, I'm not certain if the problem is happening on my home system. I do have a bunch of closed notes and when I opened them all a moment ago they all seemed to have the correct size/position. I will try leaving a few open over the next few days and report back if I see the problem happening. Thanks, ~ray -- 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 196977] Knotes: Positions of notes are not remembered
https://bugs.kde.org/show_bug.cgi?id=196977 --- Comment #3 from Ray codemon...@interthingy.net --- (In reply to comment #2) Ray: which version of knotes do you use? My work laptop is running 3.9 (Fedora 15) and I do still have this problem there. I will check my home system later and let you know the version. However, I'm not 100% certain that the problem occurs there -- this issue may have been fixed since 3.9/F15 ? -- 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 289097] error Unable to fetch item from backend when entering IMAP folder
https://bugs.kde.org/show_bug.cgi?id=289097 --- Comment #43 from ray-ven gor...@gmail.com --- I think this has to do with CALDAV. I'm importing google contacts and calendar via caldav - afaik this is often a cause of Unable to fetch item from backend -- 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 293883] GroupDav addressbook from egroupware cancels with Unbekannter Fehler. (Unable to fetch item from backend)
https://bugs.kde.org/show_bug.cgi?id=293883 ray-ven gor...@gmail.com changed: What|Removed |Added CC||gor...@gmail.com --- Comment #8 from ray-ven gor...@gmail.com --- Same in Kubuntu (Precise and oneiric) with KDE 4.7-4.9 Beta2 and at my girlfriend's laptop with her profile. I don't know it it's the plasma-desktop itself (because the errormessage is sometimes related to plasma sometimes to kde), so I'm not really able to give usefull information. I've set up a CalDav with multiple calendars, a google contacts ressource and a few IMAPs and akonadi notes. From 4.7 to 4.8 I deleted all my akonadi stuff and set it up again - error still occours. There are about 3 of these Unable to fetch item from backend on startup of KDE, and about 5 when starting Kontact, about 3 again when clicking on calendar in Kontact. This is killing my nerves What about just let plasma-notifications handle Unable to fetch item from backend instead of popups which have to be confirmed. The message itself doesn't help much anyway, because it doesn't tell me from which backend (ressource) the item can't be fetched. I think this is somehow network-connection related, because with no active connection kalendar goes totally crazy with these messages and sometimes if the connection breaks while using kontact the amount of messages (in the notification-widget this time) is almost endless. I doubt it but hope this delivers somebody useful information. Ray -- 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 289097] error Unable to fetch item from backend when entering IMAP folder
https://bugs.kde.org/show_bug.cgi?id=289097 ray-ven gor...@gmail.com changed: What|Removed |Added CC||gor...@gmail.com --- Comment #37 from ray-ven gor...@gmail.com --- wrote the same at: https://bugs.kde.org/show_bug.cgi?id=293883#c8 Same in Kubuntu (Precise and oneiric) with KDE 4.7-4.9 Beta2 and at my girlfriend's laptop with her profile. I don't know it it's the plasma-desktop itself (because the errormessage is sometimes related to plasma sometimes to kde), so I'm not really able to give usefull information. I've set up a CalDav with multiple calendars, a google contacts ressource and a few IMAPs and akonadi notes. From 4.7 to 4.8 I deleted all my akonadi stuff and set it up again - error still occours. There are about 3 of these Unable to fetch item from backend on startup of KDE, and about 5 when starting Kontact, about 3 again when clicking on calendar in Kontact. This is killing my nerves What about just let plasma-notifications handle Unable to fetch item from backend instead of popups which have to be confirmed. The message itself doesn't help much anyway, because it doesn't tell me from which backend (ressource) the item can't be fetched. I think this is somehow network-connection related, because with no active connection kalendar goes totally crazy with these messages and sometimes if the connection breaks while using kontact the amount of messages (in the notification-widget this time) is almost endless. I doubt it but hope this delivers somebody useful information. Ray -- 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 196977] Knotes: Positions of notes are not remembered
https://bugs.kde.org/show_bug.cgi?id=196977 Ray codemon...@interthingy.net changed: What|Removed |Added CC||codemon...@interthingy.net --- Comment #1 from Ray codemonkey interthingy net 2012-03-01 21:43:13 --- Same problem here. I wanted to note (no pun intended :) that KNotes seems to be remembering the size and position of at least some windows but confusing their content. On login, some note windows will appear in the size and position that I left them in but the window will contain the wrong note text (swapped with another window). I've also noticed that often two notes will restore to the exact same size and position as each other, such that one completely obscures the other (only one had that size and position when I logged out; the other was different). Curiously, this seems to happen to only two notes every time regardless of how many total there are. -- 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 282548] New: Add Singapore
https://bugs.kde.org/show_bug.cgi?id=282548 Summary: Add Singapore Product: kdepimlibs Version: 4.7 Platform: Archlinux Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: kholidays AssignedTo: jl...@kde.org ReportedBy: sc...@archlinux.org CC: kdepim-bugs@kde.org Created an attachment (id=63854) -- (http://bugs.kde.org/attachment.cgi?id=63854) Proposed libkholidays plan2 file for Singapore Version: 4.7 (using KDE 4.7.1) OS:Linux All national holidays (holidays for everyone) in Singapore are considered Public Holidays, including religious ones. Students of Primary and Secondary levels enjoy School Holidays that include term/semester breaks. These holidays are not for the working public, or students of tertiary level and beyond (who do have term/semester breaks). Cultural observences are not holidays, but are marked on the calender. A few (usually just one to two but may be more in some years) of the public holidays do not have a fixed recurring date and depend on external factors. The government marks unconfirmed dates officially (that are printed as such) and issues updates or confirmation through the media at a later time. This may apply to non-holiday observences as well. Holidays that fall on a Sunday will roll over to a holiday on the next Monday. Both the days are marked on the calender, so I am unsure if this translates perfectly to shift to monday if sunday. I have attached a plan(2) file but it should not be committed verbatim. The syntax is not well-documented and there are different styles among the distributed files, for eg. minus 2 vs. minus 2 days, shift to monday if sunday vs. $someconditional. I am also unsure what weekend on $someday means over simply $someday. I wanted to add in the term/semester breaks for schools, but was not confident that the plus $days syntax would be correct. The primary sources for the year of 2011: http://www.mom.gov.sg/employment-practices/employment-rights-conditions/leave-and-holiday/Pages/PublicHolidays2011.aspx http://www.moe.gov.sg/schools/terms-and-holidays/ There are iCalender, XML and HTML files offered, so it would be good if in the future libkholidays could parse one or more of such formats. Reproducible: Didn't try Steps to Reproduce: N.A Actual Results: N.A Expected Results: N.A N.A -- 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 228047] New: Kontact (Korganizer) crashes when using timeline view
https://bugs.kde.org/show_bug.cgi?id=228047 Summary: Kontact (Korganizer) crashes when using timeline view Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: extravag...@gmx.de Application: kontact (4.4) KDE Platform Version: 4.4.00 (KDE 4.4.0) Qt Version: 4.6.1 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 -- Information about the crash: Kontact crashes when klickin on blue bar in Timeline view. (In German: Zeitleiste) 4 Calenders are Active -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x001dc7cb in __dynamic_cast () from /usr/lib/libstdc++.so.6 #7 0x0593b8d3 in KOTimelineView::itemMoved (this=0xa281e48, item=0x1) at ../../korganizer/views/timelineview/kotimelineview.cpp:343 #8 0x0593bfbf in KOTimelineView::qt_metacall (this=0xa281e48, _c=QMetaObject::InvokeMetaMethod, _id=71, _a=0xbfc24c48) at ./kotimelineview.moc:86 #9 0x00ffbf6a in QMetaObject::metacall (object=0xa281e48, cl=179415649, idx=71, argv=0xbfc24c48) at kernel/qmetaobject.cpp:237 #10 0x0100a705 in QMetaObject::activate (sender=0xaac3418, m=0x5a30cbc, local_signal_index=19, argv=0xbfc24c48) at kernel/qobject.cpp:3275 #11 0x058880c3 in KDGanttView::gvItemMoved (this=0xaac3418, _t1=0xab1aa50) at ./KDGanttView.moc:666 #12 0x058bface in KDGanttCanvasView::contentsMouseReleaseEvent (this=0xaab7fd8, e=0xbfc24cf0) at ../../kdgantt1/KDGanttViewSubwidgets.cpp:4155 #13 0x0265baa8 in Q3ScrollView::viewportMouseReleaseEvent (this=0xaab7fd8, e=0xbfc25270) at widgets/q3scrollview.cpp:1763 #14 0x0265d678 in Q3ScrollView::eventFilter (this=0xaab7fd8, obj=0xaab6b70, e=0xbfc25270) at widgets/q3scrollview.cpp:1481 #15 0x00ff5f9a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x858acd0, receiver=0xaab6b70, event=0xbfc25270) at kernel/qcoreapplication.cpp:819 #16 0x01242259 in QApplicationPrivate::notify_helper (this=0x858acd0, receiver=0xaab6b70, e=0xbfc25270) at kernel/qapplication.cpp:4294 #17 0x01249877 in QApplication::notify (this=0xbfc25b24, receiver=0xaab6b70, e=0xbfc25270) at kernel/qapplication.cpp:3863 #18 0x0084b1fa in KApplication::notify (this=0xbfc25b24, receiver=0xaab6b70, event=0xbfc25270) at ../../kdeui/kernel/kapplication.cpp:302 #19 0x00ff6cfb in QCoreApplication::notifyInternal (this=0xbfc25b24, receiver=0xaab6b70, event=0xbfc25270) at kernel/qcoreapplication.cpp:704 #20 0x012487cf in QCoreApplication::sendEvent (receiver=0xaab6b70, event=0xbfc25270, alienWidget=0xaab6b70, nativeWidget=0x858b900, buttonDown=0x1b83058, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #21 QApplicationPrivate::sendMouseEvent (receiver=0xaab6b70, event=0xbfc25270, alienWidget=0xaab6b70, nativeWidget=0x858b900, buttonDown=0x1b83058, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2963 #22 0x012d3618 in QETWidget::translateMouseEvent (this=0x858b900, event=0xbfc2578c) at kernel/qapplication_x11.cpp:4368 #23 0x012d2af1 in QApplication::x11ProcessEvent (this=0xbfc25b24, event=0xbfc2578c) at kernel/qapplication_x11.cpp:3379 #24 0x0130195a in x11EventSourceDispatch (s=0x8593b68, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #25 0x02048e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #26 0x0204c730 in ?? () from /lib/libglib-2.0.so.0 #27 0x0204c863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #28 0x010228e5 in QEventDispatcherGlib::processEvents (this=0x85690e8, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #29 0x01301485 in QGuiEventDispatcherGlib::processEvents (this=0x85690e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #30 0x00ff5319 in QEventLoop::processEvents (this=0xbfc25a84, flags=) at kernel/qeventloop.cpp:149 #31 0x00ff576a in QEventLoop::exec (this=0xbfc25a84, flags=...) at kernel/qeventloop.cpp:201 #32 0x00ff995f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #33 0x01242317 in QApplication::exec () at kernel/qapplication.cpp:3577 #34 0x0804b4c2 in main (argc=1, argv=0xbfc25d44) at ../../../kontact/src/main.cpp:224 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 217814] KMail is not honouring the LC_COLLATE setting when sorting folder list
https://bugs.kde.org/show_bug.cgi?id=217814 ray r...@eng-int.co.uk changed: What|Removed |Added CC||r...@eng-int.co.uk --- Comment #1 from ray rayH eng-int co uk 2010-01-11 09:05:53 --- This behaviour has been maintained throughout KDE4 I tried to report this in bug 199244, but it was dismissed as a duplicate of a KDE2 bug 38039 marked as WONTFIX. -- 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 218930] New: Kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=218930 Summary: Kontact crashes on restart Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: extravag...@gmx.de Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.2 Operating System: Linux 2.6.31-17-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Kontact crashes, when i close it, and start it again in the same session -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x007a01fc in QString (this=0x9271dd0) at /usr/include/qt4/QtCore/qstring.h:711 #7 Kontact::Plugin::identifier (this=0x9271dd0) at ../../kontactinterfaces/plugin.cpp:97 #8 0x0063650e in Kontact::MainWindow::activatePluginModule (this=0x9061878) at ../../../kontact/src/mainwindow.cpp:303 #9 0x006365c4 in Kontact::MainWindow::setActivePluginModule (this=0x9061878, module=...) at ../../../kontact/src/mainwindow.cpp:281 #10 0x0804bd0f in KontactApp::newInstance (this=0xbff04c84) at ../../../kontact/src/main.cpp:147 #11 0x00982930 in KUniqueApplicationAdaptor::newInstance (this=0x9122290, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459 #12 0x00983042 in KUniqueApplicationAdaptor::qt_metacall (this=0x9122290, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff042ac) at ./kuniqueapplication_p.moc:75 #13 0x00df77b4 in QDBusConnectionPrivate::deliverCall (this=0x9047c90, object=0x9122290, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:891 #14 0x00df89c5 in QDBusConnectionPrivate::activateCall (this=0x9047c90, object=0x9122290, flags=337, msg=...) at qdbusintegrator.cpp:803 #15 0x00df9234 in QDBusConnectionPrivate::activateObject (this=0x9047c90, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1347 #16 0x00df94da in QDBusActivateObjectEvent::placeMetaCall (this=0xa8e2d40) at qdbusintegrator.cpp:1464 #17 0x00ca85fe in QObject::event (this=0xbff04c84, e=0xa8e2d40) at kernel/qobject.cpp: #18 0x00c97ffb in QCoreApplication::event (this=0xbff04c84, e=0xa8e2d40) at kernel/qcoreapplication.cpp:1434 #19 0x010139a6 in QApplication::event (this=0xbff04c84, e=0xa8e2d40) at kernel/qapplication.cpp:2317 #20 0x0100df54 in QApplicationPrivate::notify_helper (this=0x904f2e0, receiver=0xbff04c84, e=0xa8e2d40) at kernel/qapplication.cpp:4056 #21 0x0101567c in QApplication::notify (this=0xbff04c84, receiver=0xbff04c84, e=0xa8e2d40) at kernel/qapplication.cpp:3603 #22 0x0097b1aa in KApplication::notify (this=0xbff04c84, receiver=0xbff04c84, event=0xa8e2d40) at ../../kdeui/kernel/kapplication.cpp:302 #23 0x00c986cb in QCoreApplication::notifyInternal (this=0xbff04c84, receiver=0xbff04c84, event=0xa8e2d40) at kernel/qcoreapplication.cpp:610 #24 0x00c992b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x902f820) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x902f820) at kernel/qcoreapplication.cpp:1247 #26 0x00c9947d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #27 0x00cc33ff in QCoreApplication::sendPostedEvents (s=0x9051b18) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #28 postEventSourceDispatch (s=0x9051b18) at kernel/qeventdispatcher_glib.cpp:210 #29 0x035e3e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #30 0x035e7730 in ?? () from /lib/libglib-2.0.so.0 #31 0x035e7863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #32 0x00cc302c in QEventDispatcherGlib::processEvents (this=0x902f9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #33 0x010aebe5 in QGuiEventDispatcherGlib::processEvents (this=0x902f9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #34 0x00c96c79 in QEventLoop::processEvents (this=0xbff04be4, flags=) at kernel/qeventloop.cpp:149 #35 0x00c970ca in QEventLoop::exec (this=0xbff04be4, flags=...) at kernel/qeventloop.cpp:201 #36 0x00c9953f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #37 0x0100ddd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #38 0x0804b4e6 in main (argc=1, argv=0xbff04ea4) at ../../../kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 213323 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 216401] New: kmail imap random crash move email between folders
https://bugs.kde.org/show_bug.cgi?id=216401 Summary: kmail imap random crash move email between folders Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@mail.com Application that crashed: kmail Version of the application: 1.12.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-14-generic x86_64 Distribution: Ubuntu 9.10 -- Backtrace: Application: KMail (kmail), signal: Segmentation fault The current source language is auto; currently c. [KCrash Handler] #5 0x7f4a4afbb6d6 in KMail::ISubject::notify (this=0x36546b0) at ../../kmail/isubject.cpp:30 #6 0x7f4a4aca6eec in KMMessage::updateBodyPart (this=0x36545e0, partSpecifier=) at ../../kmail/kmmessage.cpp:3235 #7 0x7f4a4af8fbca in KMail::ImapJob::slotGetMessageResult (this=0x3862b80, job=value optimized out) at ../../kmail/imapjob.cpp:435 #8 0x7f4a4af9404b in KMail::ImapJob::qt_metacall (this=0x3862b80, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffb15ec450) at ./imapjob.moc:82 #9 0x7f4a499d0ddc in QMetaObject::activate (sender=0x2aa6210, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x2) at kernel/qobject.cpp:3113 #10 0x7f4a4b659af2 in KJob::result (this=0x28c6e88, _t1=0x2aa6210) at ./kjob.moc:188 #11 0x7f4a4b659e6f in KJob::emitResult (this=0x2aa6210) at ../../kdecore/jobs/kjob.cpp:304 #12 0x7f4a43779d93 in KIO::SimpleJob::slotFinished (this=0x2aa6210) at ../../kio/kio/job.cpp:477 #13 0x7f4a4377a253 in KIO::TransferJob::slotFinished (this=0x2aa6210) at ../../kio/kio/job.cpp:948 #14 0x7f4a43778b61 in KIO::TransferJob::qt_metacall (this=0x2aa6210, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffb15ec870) at ./jobclasses.moc:343 #15 0x7f4a499d0ddc in QMetaObject::activate (sender=0x31096a0, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x2) at kernel/qobject.cpp:3113 #16 0x7f4a4383aa81 in KIO::SlaveInterface::dispatch (this=0x31096a0, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #17 0x7f4a43837333 in KIO::SlaveInterface::dispatch (this=0x31096a0) at ../../kio/kio/slaveinterface.cpp:91 #18 0x7f4a4382a14d in KIO::Slave::gotInput (this=0x31096a0) at ../../kio/kio/slave.cpp:322 #19 0x7f4a4382c26c in KIO::Slave::qt_metacall (this=0x31096a0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffb15ecc30) at ./slave.moc:76 #20 0x7f4a499d0ddc in QMetaObject::activate (sender=0x310aba0, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x2) at kernel/qobject.cpp:3113 #21 0x7f4a43746f57 in KIO::ConnectionPrivate::dequeue (this=0x310ab70) at ../../kio/kio/connection.cpp:82 #22 0x7f4a4374707d in KIO::Connection::qt_metacall (this=0x310aba0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x2fefd50) at ./connection.moc:73 #23 0x7f4a499cb0f9 in QObject::event (this=0x310aba0, e=0x34a1760) at kernel/qobject.cpp: #24 0x7f4a49e4eefc in QApplicationPrivate::notify_helper (this=0x227aee0, receiver=0x310aba0, e=0x34a1760) at kernel/qapplication.cpp:4056 #25 0x7f4a49e561ce in QApplication::notify (this=0x7fffb15ed700, receiver=0x310aba0, e=0x34a1760) at kernel/qapplication.cpp:4021 #26 0x7f4a4bc11ab6 in KApplication::notify (this=0x7fffb15ed700, receiver=0x310aba0, event=0x34a1760) at ../../kdeui/kernel/kapplication.cpp:302 #27 0x7f4a499bbc2c in QCoreApplication::notifyInternal (this=0x7fffb15ed700, receiver=0x310aba0, event=0x34a1760) at kernel/qcoreapplication.cpp:610 #28 0x7f4a499bc80a in QCoreApplication::sendEvent (receiver=0x0, event_type=value optimized out, data=0x2241d00) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value optimized out, data=0x2241d00) at kernel/qcoreapplication.cpp:1247 #30 0x7f4a499e4533 in QCoreApplication::sendPostedEvents (s=value optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #31 postEventSourceDispatch (s=value optimized out) at kernel/qeventdispatcher_glib.cpp:210 #32 0x7f4a40c54bbe in g_main_dispatch (context=0x2277120) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:1960 #33 IA__g_main_context_dispatch (context=0x2277120) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2513 #34 0x7f4a40c58588 in g_main_context_iterate (context=0x2277120, block=value optimized out, dispatch=value optimized out, self=value optimized out) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2591 #35 0x7f4a40c586b0 in IA__g_main_context_iteration (context=0x2277120, may_block=1) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2654 #36
[Bug 213323] New: Kontact crashes on shutdown / Kontact crashes on restart (KDE 4.3.3)
https://bugs.kde.org/show_bug.cgi?id=213323 Summary: Kontact crashes on shutdown / Kontact crashes on restart (KDE 4.3.3) Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: extravag...@gmx.de Application that crashed: kontact Version of the application: 4.3.3 KDE Version: 4.3.3 (KDE 4.3.3) Qt Version: 4.5.2 Operating System: Linux 2.6.31-14-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Oh well, same Problem with 4.3.3 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x004b41fc in QString (this=0x8806e98) at /usr/include/qt4/QtCore/qstring.h:711 #7 Kontact::Plugin::identifier (this=0x8806e98) at ../../kontactinterfaces/plugin.cpp:97 #8 0x00c6450e in Kontact::MainWindow::activatePluginModule (this=0x8587430) at ../../../kontact/src/mainwindow.cpp:303 #9 0x00c645c4 in Kontact::MainWindow::setActivePluginModule (this=0x8587430, module=...) at ../../../kontact/src/mainwindow.cpp:281 #10 0x0804bd0f in KontactApp::newInstance (this=0xbfb5c364) at ../../../kontact/src/main.cpp:147 #11 0x002ea8d0 in KUniqueApplicationAdaptor::newInstance (this=0x865bf28, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459 #12 0x002eafe2 in KUniqueApplicationAdaptor::qt_metacall (this=0x865bf28, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb5b98c) at ./kuniqueapplication_p.moc:75 #13 0x00ba77b4 in QDBusConnectionPrivate::deliverCall (this=0x856ac90, object=0x865bf28, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:891 #14 0x00ba89c5 in QDBusConnectionPrivate::activateCall (this=0x856ac90, object=0x865bf28, flags=337, msg=...) at qdbusintegrator.cpp:803 #15 0x00ba9234 in QDBusConnectionPrivate::activateObject (this=0x856ac90, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1347 #16 0x00ba94da in QDBusActivateObjectEvent::placeMetaCall (this=0x943b618) at qdbusintegrator.cpp:1464 #17 0x02eb85fe in QObject::event (this=0xbfb5c364, e=0x943b618) at kernel/qobject.cpp: #18 0x02ea7ffb in QCoreApplication::event (this=0xbfb5c364, e=0x943b618) at kernel/qcoreapplication.cpp:1434 #19 0x00da39a6 in QApplication::event (this=0xbfb5c364, e=0x943b618) at kernel/qapplication.cpp:2317 #20 0x00d9df54 in QApplicationPrivate::notify_helper (this=0x8572938, receiver=0xbfb5c364, e=0x943b618) at kernel/qapplication.cpp:4056 #21 0x00da567c in QApplication::notify (this=0xbfb5c364, receiver=0xbfb5c364, e=0x943b618) at kernel/qapplication.cpp:3603 #22 0x002e314a in KApplication::notify (this=0xbfb5c364, receiver=0xbfb5c364, event=0x943b618) at ../../kdeui/kernel/kapplication.cpp:302 #23 0x02ea86cb in QCoreApplication::notifyInternal (this=0xbfb5c364, receiver=0xbfb5c364, event=0x943b618) at kernel/qcoreapplication.cpp:610 #24 0x02ea92b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8552820) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8552820) at kernel/qcoreapplication.cpp:1247 #26 0x02ea947d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #27 0x02ed33ff in QCoreApplication::sendPostedEvents (s=0x8583f18) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #28 postEventSourceDispatch (s=0x8583f18) at kernel/qeventdispatcher_glib.cpp:210 #29 0x03478e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #30 0x0347c720 in ?? () from /lib/libglib-2.0.so.0 #31 0x0347c853 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #32 0x02ed302c in QEventDispatcherGlib::processEvents (this=0x85529f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #33 0x00e3ebe5 in QGuiEventDispatcherGlib::processEvents (this=0x85529f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #34 0x02ea6c79 in QEventLoop::processEvents (this=0xbfb5c2c4, flags=) at kernel/qeventloop.cpp:149 #35 0x02ea70ca in QEventLoop::exec (this=0xbfb5c2c4, flags=...) at kernel/qeventloop.cpp:201 #36 0x02ea953f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #37 0x00d9ddd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #38 0x0804b4e6 in main (argc=1, argv=0xbfb5c584) at ../../../kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 212937 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 212385] Kontact doesn't quit correctly / Kontact crashes on start
https://bugs.kde.org/show_bug.cgi?id=212385 --- Comment #2 from Ray Ven extravagant gmx de 2009-10-31 17:25:20 --- It seems I could solve this issue here. Kadressbook has had an Akonadi-Resource wich points to my Adressbookfile. As I changed this at KDE-Resources in Systemsettings to file-Resource pointing to the same file. This had to effects: - Kontact doesn't need 20minutes to start anymore, - Kontact closes and starts without segfault Hope this helps a bit. Contact me for further info -- 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 202846] New: Kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=202846
Summary: Kontact crashes on restart
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: extravag...@gmx.de
Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-14-generic i686
Distribution: Ubuntu 9.04
What I was doing when the application crashed:
Happens when I close kontact and start it again
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6 0xb780802c in Kontact::Plugin::identifier (this=0x9536888) at
/usr/include/qt4/QtCore/qstring.h:711
#7 0xb7821ff9 in Kontact::MainWindow::activatePluginModule (this=0x924e368) at
/build/buildd/kdepim-4.3.0/kontact/src/mainwindow.cpp:303
#8 0xb78220a4 in Kontact::MainWindow::setActivePluginModule (this=0x924e368,
modu...@0xbfe97a04) at
/build/buildd/kdepim-4.3.0/kontact/src/mainwindow.cpp:281
#9 0x0804ac57 in KontactApp::newInstance (this=0xbfe98568) at
/build/buildd/kdepim-4.3.0/kontact/src/main.cpp:147
#10 0xb6cbfc36 in KUniqueApplicationAdaptor::newInstance (this=0x92afc98,
asn_...@0xa27b6c8, ar...@0xa0cc980) at
/build/buildd/kde4libs-4.3.0/kdeui/kernel/kuniqueapplication.cpp:459
#11 0xb6cbfcde in KUniqueApplicationAdaptor::qt_metacall (this=0x92afc98,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfe97c58)
at
/build/buildd/kde4libs-4.3.0/obj-i486-linux-gnu/kdeui/kuniqueapplication_p.moc:75
#12 0xb5d15e5a in QDBusConnectionPrivate::deliverCall (this=0x9232f40,
object=0x92afc98, m...@0xa30bc88, metatyp...@0xa0d5504, slotIdx=4) at
qdbusintegrator.cpp:891
#13 0xb5d17179 in QDBusConnectionPrivate::activateCall (this=0x9232f40,
object=0x92afc98, flags=337, m...@0xa30bc88) at qdbusintegrator.cpp:803
#14 0xb5d175e1 in QDBusConnectionPrivate::activateObject (this=0x9232f40,
no...@0xa30bc74, m...@0xa30bc88, pathStartPos=16) at qdbusintegrator.cpp:1370
#15 0xb5d17ada in QDBusActivateObjectEvent::placeMetaCall (this=0xa30bc48) at
qdbusintegrator.cpp:1464
#16 0xb5c0e3b0 in QObject::event (this=0xbfe98568, e=0xa30bc48) at
kernel/qobject.cpp:
#17 0xb5bfd56b in QCoreApplication::event (this=0xbfe98568, e=0xa30bc48) at
kernel/qcoreapplication.cpp:1434
#18 0xb60c4679 in QApplication::event (this=0xbfe98568, e=0xa30bc48) at
kernel/qapplication.cpp:2317
#19 0xb60bed3c in QApplicationPrivate::notify_helper (this=0x923f028,
receiver=0xbfe98568, e=0xa30bc48) at kernel/qapplication.cpp:4056
#20 0xb60c703e in QApplication::notify (this=0xbfe98568, receiver=0xbfe98568,
e=0xa30bc48) at kernel/qapplication.cpp:3603
#21 0xb6cb85cd in KApplication::notify (this=0xbfe98568, receiver=0xbfe98568,
event=0xa30bc48) at
/build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#22 0xb5bfdbcb in QCoreApplication::notifyInternal (this=0xbfe98568,
receiver=0xbfe98568, event=0xa30bc48) at kernel/qcoreapplication.cpp:610
#23 0xb5bfe825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0,
event_type=0, data=0x921b440) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 0xb5bfea1d in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1140
#25 0xb5c296af in postEventSourceDispatch (s=0x92410a8) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#26 0xb4ccfb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb4cd30eb in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb4cd3268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb5c292f8 in QEventDispatcherGlib::processEvents (this=0x921b028, flags={i
= -1075215304}) at kernel/qeventdispatcher_glib.cpp:327
#30 0xb6160a75 in QGuiEventDispatcherGlib::processEvents (this=0x921b028,
flags={i = -1075215256}) at kernel/qguieventdispatcher_glib.cpp:202
#31 0xb5bfc1fa in QEventLoop::processEvents (this=0xbfe984e0, flags={i =
-1075215192}) at kernel/qeventloop.cpp:149
#32 0xb5bfc642 in QEventLoop::exec (this=0xbfe984e0, flags={i = -1075215128})
at kernel/qeventloop.cpp:201
#33 0xb5bfeae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#34 0xb60bebb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#35 0x0804bfef in main (argc=1, argv=0xbfe98864) at
/build/buildd/kdepim-4.3.0/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 200053] New: kopete crashes on exit
https://bugs.kde.org/show_bug.cgi?id=200053 Summary: kopete crashes on exit Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: extravag...@gmx.de Application that crashed: kontact Version of the application: 4.3.0 rc2 KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Qt Version: 4.5.1 Operating System: Linux 2.6.28-13-generic i686 Distribution: Ubuntu 9.04 -- Backtrace: Application: Kontact (kontact), signal: Aborted [KCrash Handler] #6 0xb80a8430 in __kernel_vsyscall () #7 0xb59686d0 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb596a098 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb5c0a1e5 in qt_message_output (msgType=QtFatalMsg, buf=0xadc0a10 Fatal Error: Accessed global static 'StaticControl *s_instance()' after destruction. Defined at /build/buildd/kdepimlibs-4.2.96/akonadi/control.cpp:120) at global/qglobal.cpp:2017 #10 0xb5c0a2d1 in qFatal (msg=0xac756cd8 Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d) at global/qglobal.cpp:2216 #11 0xac6eb5ec in Akonadi::Control::start () at /build/buildd/kdepimlibs-4.2.96/akonadi/control.cpp:120 #12 0xac7de34b in ?? () from /usr/lib/kde4/kabc_akonadi.so #13 0xac7b9360 in ?? () from /usr/lib/kde4/kabc_akonadi.so #14 0xb72eab90 in KRES::Resource::open (this=0x9a9f190) at /build/buildd/kdepimlibs-4.2.96/kresources/resource.cpp:122 #15 0xb735bc14 in KABC::StdAddressBook::Private::init (this=0x9d10d28, asynchronous=false) at /build/buildd/kdepimlibs-4.2.96/kabc/stdaddressbook.cpp:151 #16 0xb735d362 in KABC::StdAddressBook::self (asynchronous=false) at /build/buildd/kdepimlibs-4.2.96/kabc/stdaddressbook.cpp:92 #17 0xb735d432 in KABC::StdAddressBook::self () at /build/buildd/kdepimlibs-4.2.96/kabc/stdaddressbook.cpp:81 #18 0xac595a5d in KOPrefs::instance () at /build/buildd/kdepim-4.2.96/korganizer/koprefs.cpp:99 #19 0xac3b3b0f in FreeBusyManager::slotPerhapsUploadFB (this=0xa6913a0) at /build/buildd/kdepim-4.2.96/korganizer/freebusymanager.cpp:157 #20 0xac3b6c0b in FreeBusyManager::qt_metacall (this=0xa6913a0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbffc59b8) at /build/buildd/kdepim-4.2.96/obj-i486-linux-gnu/korganizer/freebusymanager.moc:147 #21 0xb5d1ca58 in QMetaObject::activate (sender=0xa8ed5d8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3120 #22 0xb5d1d6e2 in QMetaObject::activate (sender=0xa8ed5d8, m=0xb7487e2c, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194 #23 0xb73eea67 in KCal::Calendar::calendarChanged (this=0xa8ed5d8) at /build/buildd/kdepimlibs-4.2.96/obj-i486-linux-gnu/kcal/calendar.moc:86 #24 0xb73eead5 in KCal::Calendar::qt_metacall (this=0xa8ed5d8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbffc5b2c) at /build/buildd/kdepimlibs-4.2.96/obj-i486-linux-gnu/kcal/calendar.moc:73 #25 0xb74532fa in KCal::CalendarResources::qt_metacall (this=0xa8ed5d8, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbffc5b2c) at /build/buildd/kdepimlibs-4.2.96/obj-i486-linux-gnu/kcal/calendarresources.moc:76 #26 0xb5d1ca58 in QMetaObject::activate (sender=0xa913358, from_signal_index=4, to_signal_index=4, argv=0xbffc5b2c) at kernel/qobject.cpp:3120 #27 0xb5d1d6e2 in QMetaObject::activate (sender=0xa913358, m=0xb74887b4, local_signal_index=0, argv=0xbffc5b2c) at kernel/qobject.cpp:3194 #28 0xb7441213 in KCal::ResourceCalendar::resourceChanged (this=0xa913358, _t1=0xa913358) at /build/buildd/kdepimlibs-4.2.96/obj-i486-linux-gnu/kcal/resourcecalendar.moc:117 #29 0xac619fa8 in ?? () from /usr/lib/kde4/kcal_akonadi.so #30 0xac6356df in ?? () from /usr/lib/kde4/kcal_akonadi.so #31 0xac614a05 in ?? () from /usr/lib/kde4/kcal_akonadi.so #32 0xb72eaf97 in KRES::Resource::close (this=0xa913358) at /build/buildd/kdepimlibs-4.2.96/kresources/resource.cpp:141 #33 0xb7456dbd in KCal::CalendarResources::close (this=0xa8ed5d8) at /build/buildd/kdepimlibs-4.2.96/kcal/calendarresources.cpp:350 #34 0xb7457145 in ~CalendarResources (this=0xa8ed5d8) at /build/buildd/kdepimlibs-4.2.96/kcal/calendarresources.cpp:247 #35 0xb19970c4 in ~StdCalendar (this=0xa8ed5d8) at /build/buildd/kdepim-4.2.96/korganizer/stdcalendar.cpp:112 #36 0xb1998adf in K3StaticDeleterKOrg::StdCalendar::destructObject (this=0xb199b0d4) at /usr/include/k3staticdeleter.h:174 #37 0xb79b987a in K3StaticDeleterPrivate::deleteStaticDeleters () at /build/buildd/kde4libs-4.2.96/kde3support/kdecore/k3staticdeleter.cpp:56 #38 0xb5d06d1b in qt_call_post_routines () at kernel/qcoreapplication.cpp:163 #39 0xb61d0478 in ~QApplication (this=0xbffc5e98) at kernel/qapplication.cpp:970 #40 0xb6deb0be in ~KApplication (this=0xbffc5e98) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:904 #41 0xb6df1eb8 in ~KUniqueApplication (this=0xbffc5e98) at
[Bug 199796] New: kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=199796
Summary: kontact crashes on restart
Product: kontact
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: extravag...@gmx.de
Application that crashed: kontact
Version of the application: 4.3.0 rc1
KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1))
Qt Version: 4.5.1
Operating System: Linux 2.6.28-13-generic i686
Distribution: Ubuntu 9.04
What I was doing when the application crashed:
If I end Kontact the process still is present, if I start Kontact then it
crashes - another start lets Kontact show up
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6 0xb77e102c in Kontact::Plugin::identifier (this=0x8d9f438) at
/usr/include/qt4/QtCore/qstring.h:711
#7 0xb77faff9 in Kontact::MainWindow::activatePluginModule (this=0x8a45bb0) at
/build/buildd/kdepim-4.2.95a/kontact/src/mainwindow.cpp:303
#8 0xb77fb0a4 in Kontact::MainWindow::setActivePluginModule (this=0x8a45bb0,
modu...@0xbfd6d0b4) at
/build/buildd/kdepim-4.2.95a/kontact/src/mainwindow.cpp:281
#9 0x0804ac57 in KontactApp::newInstance (this=0xbfd6dc18) at
/build/buildd/kdepim-4.2.95a/kontact/src/main.cpp:147
#10 0xb6c99a66 in KUniqueApplicationAdaptor::newInstance (this=0x8a47370,
asn_...@0xa0482d8, ar...@0x8adb7c8) at
/build/buildd/kde4libs-4.2.95/kdeui/kernel/kuniqueapplication.cpp:454
#11 0xb6c99b0e in KUniqueApplicationAdaptor::qt_metacall (this=0x8a47370,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd6d308)
at
/build/buildd/kde4libs-4.2.95/obj-i486-linux-gnu/kdeui/kuniqueapplication_p.moc:75
#12 0xb5cc7e2a in QDBusConnectionPrivate::deliverCall (this=0x8a35e58,
object=0x8a47370, m...@0x9970458, metatyp...@0x8f67b8c, slotIdx=4) at
qdbusintegrator.cpp:891
#13 0xb5cc9149 in QDBusConnectionPrivate::activateCall (this=0x8a35e58,
object=0x8a47370, flags=337, m...@0x9970458) at qdbusintegrator.cpp:803
#14 0xb5cc95b1 in QDBusConnectionPrivate::activateObject (this=0x8a35e58,
no...@0x9970444, m...@0x9970458, pathStartPos=16) at qdbusintegrator.cpp:1375
#15 0xb5cc9aaa in QDBusActivateObjectEvent::placeMetaCall (this=0x9970418) at
qdbusintegrator.cpp:1469
#16 0xb5bc0150 in QObject::event (this=0xbfd6dc18, e=0x9970418) at
kernel/qobject.cpp:1118
#17 0xb5baf14b in QCoreApplication::event (this=0xbfd6dc18, e=0x9970418) at
kernel/qcoreapplication.cpp:1434
#18 0xb6073509 in QApplication::event (this=0xbfd6dc18, e=0x9970418) at
kernel/qapplication.cpp:2318
#19 0xb606dbcc in QApplicationPrivate::notify_helper (this=0x8a4f0d0,
receiver=0xbfd6dc18, e=0x9970418) at kernel/qapplication.cpp:4057
#20 0xb6075ede in QApplication::notify (this=0xbfd6dc18, receiver=0xbfd6dc18,
e=0x9970418) at kernel/qapplication.cpp:3604
#21 0xb6c923dd in KApplication::notify (this=0xbfd6dc18, receiver=0xbfd6dc18,
event=0x9970418) at
/build/buildd/kde4libs-4.2.95/kdeui/kernel/kapplication.cpp:302
#22 0xb5baf7ab in QCoreApplication::notifyInternal (this=0xbfd6dc18,
receiver=0xbfd6dc18, event=0x9970418) at kernel/qcoreapplication.cpp:610
#23 0xb5bb0405 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0,
event_type=0, data=0x8a1dc08) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 0xb5bb05fd in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1140
#25 0xb5bdb58f in postEventSourceDispatch (s=0x8a51488) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#26 0xb4c83b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb4c870eb in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb4c87268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb5bdb1d8 in QEventDispatcherGlib::processEvents (this=0x8a4e478, flags={i
= -1076438296}) at kernel/qeventdispatcher_glib.cpp:324
#30 0xb610f765 in QGuiEventDispatcherGlib::processEvents (this=0x8a4e478,
flags={i = -1076438248}) at kernel/qguieventdispatcher_glib.cpp:202
#31 0xb5baddda in QEventLoop::processEvents (this=0xbfd6db90, flags={i =
-1076438184}) at kernel/qeventloop.cpp:149
#32 0xb5bae21a in QEventLoop::exec (this=0xbfd6db90, flags={i = -1076438120})
at kernel/qeventloop.cpp:200
#33 0xb5bb06c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#34 0xb606da47 in QApplication::exec () at kernel/qapplication.cpp:3526
#35 0x0804bfef in main (argc=1, argv=0xbfd6df14) at
/build/buildd/kdepim-4.2.95a/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 199244] New: no case-sensitive sorting in folder list
https://bugs.kde.org/show_bug.cgi?id=199244 Summary: no case-sensitive sorting in folder list Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: r...@eng-int.co.uk Version:(using KDE 4.2.90) OS:Linux Installed from:SuSE RPMs In the KDE 4 versions KMail has changed from a 'nix centric case-sensitive sorting of folders to a Microsoft centric case-insensitive sort order. This is very annoying for users used to using capitals to denote more important/higher ranking items. It is becoming more difficult to support KMail from KDE-3.5 in KDE-4. Please either revert to case-sensitive, or adopt the LC_COLLATE environment variable or provide an option as in the 3.5 Konqueror. -- 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 198921] New: Kontact (Akregator) crashes sometimes when clicking on Newstabs
https://bugs.kde.org/show_bug.cgi?id=198921 Summary: Kontact (Akregator) crashes sometimes when clicking on Newstabs Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: extravag...@gmx.de Application that crashed: kontact Version of the application: 4.3.0 rc1 KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) Qt Version: 4.5.1 Operating System: Linux 2.6.28-13-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: Sometimes Kontact crashes when clicking on tabs in Akregator. Does not happen with al tabs (debugging packages didn't want to install in via crashreport Assistant) -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 0 (LWP 4107)] Thread 2 (Thread 0xaa2e8b90 (LWP 4908)): #0 0xb7f97430 in __kernel_vsyscall () #1 0xb5100412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb5920344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb5b0358c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb5af8ac6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb5b0256e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb50fc4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb591149e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb4814b30 (LWP 4107)): [KCrash Handler] #6 0xaa3ef209 in ?? () from /usr/lib/kde4/akregatorpart.so #7 0xaa4177cb in ?? () from /usr/lib/kde4/akregatorpart.so #8 0xaa417cb4 in ?? () from /usr/lib/kde4/akregatorpart.so #9 0xaa4195db in ?? () from /usr/lib/kde4/akregatorpart.so #10 0xb5c0ca58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb5c0d6e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xaa3ef6e9 in ?? () from /usr/lib/kde4/akregatorpart.so #13 0xaa3ef972 in ?? () from /usr/lib/kde4/akregatorpart.so #14 0xaa3f0991 in ?? () from /usr/lib/kde4/akregatorpart.so #15 0xaa3f5b5a in ?? () from /usr/lib/kde4/akregatorpart.so #16 0xb5c0ca58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb5c0d6e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #18 0xb711a7a3 in KParts::Part::setWindowCaption () from /usr/lib/libkparts.so.4 #19 0xb711e11c in KParts::Part::qt_metacall () from /usr/lib/libkparts.so.4 #20 0xb711e19a in KParts::ReadOnlyPart::qt_metacall () from /usr/lib/libkparts.so.4 #21 0xa9a1c55a in ?? () from /usr/lib/kde4/gvpart.so #22 0xb5c0ca58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #23 0xb5c0d6e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xa98a2d53 in Gwenview::DocumentView::captionUpdateRequested () from /usr/lib/libgwenviewlib.so.4 #25 0xa98a66a5 in ?? () from /usr/lib/libgwenviewlib.so.4 #26 0xa98a4ffc in Gwenview::DocumentView::qt_metacall () from /usr/lib/libgwenviewlib.so.4 #27 0xb5c0ca58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #28 0xb5c0d6e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #29 0xa98a28df in Gwenview::AbstractDocumentViewAdapter::zoomChanged () from /usr/lib/libgwenviewlib.so.4 #30 0xa98a2a24 in Gwenview::AbstractDocumentViewAdapter::qt_metacall () from /usr/lib/libgwenviewlib.so.4 #31 0xa98a8e5a in Gwenview::ImageViewAdapter::qt_metacall () from /usr/lib/libgwenviewlib.so.4 #32 0xb5c0ca58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #33 0xb5c0d6e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #34 0xa98c0dbf in Gwenview::ImageView::zoomChanged () from /usr/lib/libgwenviewlib.so.4 #35 0xa98c2751 in Gwenview::ImageView::setZoom () from /usr/lib/libgwenviewlib.so.4 #36 0xa98c2a39 in Gwenview::ImageView::resizeEvent () from /usr/lib/libgwenviewlib.so.4 #37 0xb610b6d6 in QWidget::event () from /usr/lib/libQtGui.so.4 #38 0xb64e92c3 in QFrame::event () from /usr/lib/libQtGui.so.4 #39 0xb658933f in QAbstractScrollArea::viewportEvent () from /usr/lib/libQtGui.so.4 #40 0xb658b945 in ?? () from /usr/lib/libQtGui.so.4 #41 0xb5bf59ca in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4 #42 0xb60b4baa in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #43 0xb60bcfc2 in QApplication::notify () from /usr/lib/libQtGui.so.4 #44 0xb6cd93dd in KApplication::notify () from /usr/lib/libkdeui.so.5 #45 0xb5bf67ab in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #46 0xb6109fdc in QWidgetPrivate::sendPendingMoveAndResizeEvents () from /usr/lib/libQtGui.so.4 #47 0xb6110cd6 in QWidgetPrivate::show_helper () from /usr/lib/libQtGui.so.4 #48 0xb6111403 in QWidget::setVisible () from /usr/lib/libQtGui.so.4 #49 0xb6d8 in QWidgetPrivate::showChildren () from /usr/lib/libQtGui.so.4 #50 0xb6110d01 in QWidgetPrivate::show_helper () from
