[Bug 301995] Kmail crash on start
https://bugs.kde.org/show_bug.cgi?id=301995 --- Comment #1 from Giuseppe Vinci giuseppe.vi...@gmx.net --- I suppose, one or more of the following files causes the crash - but I don't know, which line(s): kmailsnippetrc, kmail.notifyrc, kmail.eventsrc In truth, I deleted the files above and I don't get any crash more -- 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 301979] attempt to paste a new contact into Kadressbook results in crash
https://bugs.kde.org/show_bug.cgi?id=301979 --- Comment #1 from Llewellyn llewellyn@mtnloaded.co.za --- Hello, I do not understand the email rcd from Christof Feck Just in case he wants to know what changed to cause the crash My PClinuxOS Full monty sytem was working fine untill I did update. First I became aware that Kmail crashed if I tried to save Email address from a rcd email. I made a bug report to KDE. In order to put together a working adresssbook I decided to cut and paste adress links into the Addressbook direct. Adress book crashed immeditaely on every attempt to paste. Hoping that updates would bring a fix for the problem I have run daily updates 14,15,16 june 2012 problem remains. Regards Llewellyn Lee -- 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 301625] kmail crashes during startup (segfault)
https://bugs.kde.org/show_bug.cgi?id=301625 Tamás Németh nt1...@gmail.com changed: What|Removed |Added CC||nt1...@gmail.com --- Comment #17 from Tamás Németh nt1...@gmail.com --- Works since today morning! -- 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 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #133 from Bellegarde Cédric gnu...@gmail.com --- KDE 4.9 beta2, bug always here... It works with a fresh account (no ~/.local/share/akonadi and no ~/.kde/share/apps/nepomuk)... But it fails as soon: - You change settings in akonadi (remove ressources, readd ressources, ...) - Clean nepomuk database, it get never indexed again -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #134 from Dimitrios Glentadakis dgl...@gmail.com --- Me too, when i deleted everything in my /home (akonadi folders, nepomuk...) it worked but only if i typed the whole name. After a couple hours it stopped working and now it works only the recent addresses but only if i type the address, if i type the name of the contact it dioes nt work (KDE 4.8.2) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 301625] kmail crashes during startup (segfault)
https://bugs.kde.org/show_bug.cgi?id=301625 --- Comment #18 from Tamás Németh nt1...@gmail.com --- (In reply to comment #17) Works since today morning! But after logging in and out, it started crashing again just like before. Unbeliveable :-( -- 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 302108] New: do not include folder name in taskbar entry of a message
https://bugs.kde.org/show_bug.cgi?id=302108 Bug ID: 302108 Severity: wishlist Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: do not include folder name in taskbar entry of a message Classification: Unclassified OS: Linux Reporter: silver.salo...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 At some point (version 4.8.3?) a separately opened message started to include its folder name in its taskbar entry. To me it's quite disturbing as I often mistake the entry as the main window of the KMail which has the same icon and similar taskbar text, if the message's box is not wide enough. And I do not really understand why this change was needed too. Reproducible: Always Steps to Reproduce: 1. Open a message from message list with double-click Actual Results: Message's separate taskbar entry's name includes its folder name at the start, eg. Myaccount/Inbox - . Expected Results: Message's separate taskbar entry's name does not include its folder name at the start, eg. Myaccount/Inbox - . The folder name could be included at the end in brackets though. If people have different wishes again, maybe it would make sense to create another option for this behavior? -- 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 301625] kmail crashes during startup (segfault)
https://bugs.kde.org/show_bug.cgi?id=301625 --- Comment #19 from Axel Braun axel.br...@gmx.de --- Created attachment 71905 -- https://bugs.kde.org/attachment.cgi?id=71905action=edit crashreport Can confirm that the upgrade to soprano 2.7.6 does not fix it -- 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 301625] kmail crashes during startup (segfault)
https://bugs.kde.org/show_bug.cgi?id=301625 --- Comment #20 from Ralph Moenchmeyer r...@anracon.de --- I then combined KDE 4.8.4 from Opensuse's KDE Release Factory with the soprano RPMs from the KDE Unstable Repository as suggested. It worked ! Kmail can be started again from the command line. ( However, the message kmail2(5266)/kdepimlibs (mailtransport): Could not access Outbox. remains. ) Some more details regarding the workaround: I use KDE 4.8.4 including Kontact/Kmail from Opensuse's Release Repository [http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1]. But I do not use the included version 2.7.6 of the RPMs for * libsoprano4 * soprano * soprano-backend-virtuoso * soprano-backend-redland These soprano versions lead to crashes and other problems with Kontact/Kmail 4.8.4. Instead I use version 2.6.56 for the soprano RPMs from the Opensuses's Unstable Repository [http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1]. This really helped and I do not get any crashes any more. -- 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 302116] New: KDE 4.8.4 Kubuntu 12.04
https://bugs.kde.org/show_bug.cgi?id=302116 Bug ID: 302116 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KDE 4.8.4 Kubuntu 12.04 Classification: Unclassified OS: Linux Reporter: manfred.1...@freenet.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-26-generic-pae i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: Moving one folder into another one at the same hierarchy level Before kmail finished this choose another folder to move into the same like before or any other folder at the same hierarchy level. immediate crash after the second one choosed to move. This happens every time. Starting kmail again shows everything was moved successfully The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb141f740 (LWP 19969))] Thread 3 (Thread 0xad485b40 (LWP 19976)): #0 0xb7701424 in __kernel_vsyscall () #1 0xb57f396b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0xb5e5b3dc in __pthread_cond_wait (cond=0xb3f32a30, mutex=0xb3f32a18) at forward.c:139 #3 0xb3801263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb380137f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb57efd4c in start_thread (arg=0xad485b40) at pthread_create.c:308 #6 0xb5e4dace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xacb5cb40 (LWP 19977)): #0 0xb42d5dcd in __GI_clock_gettime (clock_id=1, tp=0xacb5c008) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb60d2315 in do_gettime (frac=0xacb5c000, sec=0xacb5bff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb61bc226 in QTimerInfoList::updateCurrentTime (this=0xac202074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb61bc57a in QTimerInfoList::timerWait (this=0xac202074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb61bae23 in timerSourcePrepareHelper (src=optimized out, timeout=0xacb5c0ec) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb445c872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb445cfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb445d201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb61bb8e7 in QEventDispatcherGlib::processEvents (this=0xac200468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0xb618750d in QEventLoop::processEvents (this=0xacb5c270, flags=...) at kernel/qeventloop.cpp:149 #11 0xb61877a9 in QEventLoop::exec (this=0xacb5c270, flags=...) at kernel/qeventloop.cpp:204 #12 0xb607094c in QThread::exec (this=0x8fb6fd0) at thread/qthread.cpp:501 #13 0xb6070a3b in QThread::run (this=0x8fb6fd0) at thread/qthread.cpp:568 #14 0xb6073de0 in QThreadPrivate::start (arg=0x8fb6fd0) at thread/qthread_unix.cpp:298 #15 0xb57efd4c in start_thread (arg=0xacb5cb40) at pthread_create.c:308 #16 0xb5e4dace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb141f740 (LWP 19969)): [KCrash Handler] #7 QModelIndex (other=..., this=0xbf7fe2b0) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:65 #8 QSortFilterProxyModel::parent (this=0x8c56628, child=...) at itemviews/qsortfilterproxymodel.cpp:1659 #9 0xb743a708 in parent (this=0xbf7fe300) at /usr/include/qt4/QtCore/qabstractitemmodel.h:393 #10 KIdentityProxyModel::parent (this=0x8dc7838, child=...) at ../../kdeui/itemviews/kidentityproxymodel.cpp:358 #11 0xb743a708 in parent (this=0xbf7fe360) at /usr/include/qt4/QtCore/qabstractitemmodel.h:393 #12 KIdentityProxyModel::parent (this=0x8df1840, child=...) at ../../kdeui/itemviews/kidentityproxymodel.cpp:358 #13 0xb4b3ce03 in sibling (acolumn=optimized out, arow=optimized out, this=optimized out) at /usr/include/qt4/QtCore/qabstractitemmodel.h:396 #14 KPIM::StatisticsProxyModel::Private::sourceLayoutAboutToBeChanged (this=0x8e0fd70) at ../../libkdepim/statisticsproxymodel.cpp:214 #15 0xb4b3cf4b in KPIM::StatisticsProxyModel::qt_static_metacall (_o=0x8df1840, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbf7fe4e0) at ./statisticsproxymodel.moc:55 #16 0xb619f6b1 in QMetaObject::activate (sender=0x8df1840, m=0xb62e62b8, local_signal_index=3, argv=0x0) at kernel/qobject.cpp:3547 #17 0xb61f1335 in QAbstractItemModel::layoutAboutToBeChanged (this=0x8df1840) at .moc/release-shared/moc_qabstractitemmodel.cpp:183 #18 0xb743c866 in KIdentityProxyModelPrivate::_k_sourceLayoutAboutToBeChanged (this=0x8dfdc40) at
[Bug 301625] kmail crashes during startup (segfault)
https://bugs.kde.org/show_bug.cgi?id=301625 --- Comment #21 from Tamás Németh nt1...@gmail.com --- (In reply to comment #20) Instead I use version 2.6.56 for the soprano RPMs from the Opensuses's Unstable Repository [http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1]. Do you mean 2.7.56 from http://download.opensuse.org/repositories/KDE:/Unstable:/SC/openSUSE_12.1 ? -- 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 302116] KDE 4.8.4 Kubuntu 12.04
https://bugs.kde.org/show_bug.cgi?id=302116 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||adap...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu adap...@gmail.com --- *** This bug has been marked as a duplicate of bug 285622 *** -- 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 285622] drag and dro of many folders does not work
https://bugs.kde.org/show_bug.cgi?id=285622 Jekyll Wu adap...@gmail.com changed: What|Removed |Added CC||manfred.1...@freenet.de --- Comment #2 from Jekyll Wu adap...@gmail.com --- *** Bug 302116 has been marked as a duplicate of this bug. *** -- 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 302116] KDE 4.8.4 Kubuntu 12.04
https://bugs.kde.org/show_bug.cgi?id=302116 --- Comment #2 from Jekyll Wu adap...@gmail.com --- *** This bug has been marked as a duplicate of bug 295622 *** -- 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 295622] Select two folders then move them to another sub sub folders crash
https://bugs.kde.org/show_bug.cgi?id=295622 Jekyll Wu adap...@gmail.com changed: What|Removed |Added CC||manfred.1...@freenet.de --- Comment #20 from Jekyll Wu adap...@gmail.com --- *** Bug 302116 has been marked as a duplicate of this bug. *** -- 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 301713] KMail crashes after creating a new folder
https://bugs.kde.org/show_bug.cgi?id=301713 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||adap...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu adap...@gmail.com --- *** This bug has been marked as a duplicate of bug 298952 *** -- 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 298952] kmail is crashing while moving IMAP folders
https://bugs.kde.org/show_bug.cgi?id=298952 Jekyll Wu adap...@gmail.com changed: What|Removed |Added CC||igo...@gmail.com --- Comment #3 from Jekyll Wu adap...@gmail.com --- *** Bug 301713 has been marked as a duplicate of this bug. *** -- 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 301693] MKail crashes after moving a folder and trying to create another one.
https://bugs.kde.org/show_bug.cgi?id=301693 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||adap...@gmail.com Resolution|--- |DUPLICATE --- Comment #2 from Jekyll Wu adap...@gmail.com --- *** This bug has been marked as a duplicate of bug 298952 *** -- 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 298952] kmail is crashing while moving IMAP folders
https://bugs.kde.org/show_bug.cgi?id=298952 Jekyll Wu adap...@gmail.com changed: What|Removed |Added CC||la...@oisher.net --- Comment #4 from Jekyll Wu adap...@gmail.com --- *** Bug 301693 has been marked as a duplicate of this bug. *** -- 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 302124] New: Google calendar resource fails to parse token page
https://bugs.kde.org/show_bug.cgi?id=302124 Bug ID: 302124 Severity: major Version: 1.7.2 Priority: NOR CC: kdepim-bugs@kde.org Assignee: d...@progdan.cz Summary: Google calendar resource fails to parse token page Classification: Unclassified OS: Linux Reporter: k...@pi-xi.net Hardware: Other Status: UNCONFIRMED Component: Google Resource Product: Akonadi I opened akonadi server configuration page and added the google calendar module. after pressing authenticate and entering my google credentials on the login page and granting the akonadi resource access to my google account, the module simply says parsing token page failed. (I am using two stage authentication just for the info) The token parsing error happens also for all the other google resources in akonadi. the versions i'm using are: akonadi-google-calendar-0.2-12.20120301git41cd7c5.fc17.x86_64 akonadi-google-0.2-12.20120301git41cd7c5.fc17.x86_64 akonadi-google-contacts-0.2-12.20120301git41cd7c5.fc17.x86_64 akonadi-1.7.2-1.fc17.x86_64 akonadi-google-tasks-0.2-12.20120301git41cd7c5.fc17.x86_64 akonadi-google-debuginfo-0.2-12.20120301git41cd7c5.fc17.x86_64 kdepimlibs-akonadi-4.8.3-1.fc17.x86_64 Reproducible: Always Steps to Reproduce: 1. Try to authenticate a new google module 2. Get error after allowing access to google account Actual Results: Parse error Expected Results: Reliable access to the calendar, contacts and tasks -- 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 296561] kmail2 loses POP3 incoming mails
https://bugs.kde.org/show_bug.cgi?id=296561 --- Comment #5 from Christopher Heiny christopherhe...@gmail.com --- Still present in 4.8.3. -- 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 302124] Google calendar resource fails to parse token page
https://bugs.kde.org/show_bug.cgi?id=302124 Dan Vratil d...@progdan.cz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Component|Google Resource |General Version|1.7.2 |0.4.0 Resolution|--- |DUPLICATE Product|Akonadi |libkgapi --- Comment #1 from Dan Vratil d...@progdan.cz --- Thanks for reporting the issue. This problem has been fixed in LibKGAPI 0.4.1. Please wait for your distribution to update the resources. *** This bug has been marked as a duplicate of bug 301240 *** -- 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 301240] Parsing token page failed
https://bugs.kde.org/show_bug.cgi?id=301240 Dan Vratil d...@progdan.cz changed: What|Removed |Added CC||k...@pi-xi.net --- Comment #6 from Dan Vratil d...@progdan.cz --- *** Bug 302124 has been marked as a duplicate of this bug. *** -- 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 298267] crash when attempting to restart gmail imap connect
https://bugs.kde.org/show_bug.cgi?id=298267 Klaus Layer klaus.la...@gmx.de changed: What|Removed |Added CC||klaus.la...@gmx.de -- 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 298267] crash when attempting to restart gmail imap connect
https://bugs.kde.org/show_bug.cgi?id=298267 --- Comment #3 from Klaus Layer klaus.la...@gmx.de --- Created attachment 71914 -- https://bugs.kde.org/attachment.cgi?id=71914action=edit New crash information added by DrKonqi akonadi_imap_resource (4.8) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 - What I was doing when the application crashed: The application crashed on shutting down the system. -- Backtrace (Reduced): #7 0x7f9173e5f052 in ~Task (this=0x7fff9c9793a0, __in_chrg=optimized out) at ../../akonadi/resourcescheduler_p.h:64 #8 Akonadi::ResourceBase::cancelTask (this=0x26ce9e0) at ../../akonadi/resourcebase.cpp:792 #9 0x7f9173e5f1c9 in Akonadi::ResourceBase::cancelTask (this=0x26ce9e0, msg=...) at ../../akonadi/resourcebase.cpp:820 #10 0x0041d69b in ResourceState::cancelTask (this=0x2a65440, errorString=...) at ../../../resources/imap/resourcestate.cpp:389 #11 0x00444a71 in ResourceTask::cancelTask (this=0x2842810, errorString=...) at ../../../resources/imap/resourcetask.cpp:284 -- 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 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 Charles Figura charles.fig...@wartburg.edu changed: What|Removed |Added CC||charles.fig...@wartburg.edu -- 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 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 Mircea Sava ms...@gmx.com changed: What|Removed |Added CC|ms...@gmx.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
[Bug 301979] attempt to paste a new contact into Kadressbook results in crash
https://bugs.kde.org/show_bug.cgi?id=301979 --- Comment #2 from Llewellyn llewellyn@mtnloaded.co.za --- Hello, Problem is fixed by downloading and installing /shared-mime-info-0.90-1pclos2012.i586.rpm Regards Llewellyn Lee -- 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 286522] message tags sloppy to uselessness
https://bugs.kde.org/show_bug.cgi?id=286522 tprotopope...@gmail.com changed: What|Removed |Added CC||tprotopope...@gmail.com --- Comment #2 from tprotopope...@gmail.com --- I can confirm this. In the Settings/Configure/Appearance/Message Tags dialog only one tag shows up, and this is a tag from korganizer. None of the tags listed in the Filter by status box are there to be edited. -- 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 302137] New: Cannot save new message list theme from one session to another
https://bugs.kde.org/show_bug.cgi?id=302137 Bug ID: 302137 Severity: normal Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Cannot save new message list theme from one session to another Classification: Unclassified OS: Linux Reporter: tprotopope...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: message list Product: kmail2 After creating and applying a new message list theme in View-Message List-Theme-Configure the theme disappears after closing and restarting kmail2 (or kontact). This happens with a new theme created from scratch. The new theme is applied, but is not saved for the next session. Reproducible: Always Steps to Reproduce: 1. Go to View-Message List-Theme-Configure 2. Create a new theme 3. Apply the theme 4. Close then restart kmail/kontact. Actual Results: Message list theme has reverted to one of the preset themes (classic in my case). The new theme is gone from the list of themes in View-Message List-Theme. Expected Results: The new theme should still be in the list of themes and still be applied upon restarting kmail. In addition to not saving new themes kmail does not properly save and apply modifications to the preset themes. E.g. clone one of the preset themes, and then modify it (in my case try moving the columns around, so that sender comes before subject for example). Apply the theme - the column sort order is not applied. Go back to the configuration dialog and notice that the column positions were not saved. Moreover some columns do not become visible even if 'column properties' are set to 'visible by default'. I wanted to create custom theme as a workaround to not being able to modify the preset themes, or clones of them. Related to this seems to be that in the message list reordering the columns is not saved from session to session. So I can't just reorder the columns as I like and expect the changes to be there next time I start kmail. -- 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 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 Anthony RENOUX anthony.ren...@free.fr changed: What|Removed |Added CC||anthony.ren...@free.fr -- 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 302138] New: Crash after moving a NORMAL folder ( NO IMAP ) and creating a new subfolder of the moved normal folder
https://bugs.kde.org/show_bug.cgi?id=302138 Bug ID: 302138 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash after moving a NORMAL folder ( NO IMAP ) and creating a new subfolder of the moved normal folder Classification: Unclassified OS: Linux Reporter: patrick.cara...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.0-25-generic-pae i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: I created a Folder on the inbox ( by mistake ) I moved this folder to the root ( with a fault mention ??? ) I created a subfolder of the moved folder, and got a Crash -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb14b4740 (LWP 3705))] Thread 4 (Thread 0xae546b40 (LWP 3709)): #0 0xb7788424 in __kernel_vsyscall () #1 0xb588596b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb5eed3dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb3896263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb389637f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb5881d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0xb5edface in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xadc1db40 (LWP 3710)): #0 0xb5ecf130 in read () from /lib/i386-linux-gnu/libc.so.6 #1 0xb45306ae in read (__nbytes=16, __buf=0xadc1d0ac, __fd=optimized out) at /usr/include/i386-linux-gnu/bits/unistd.h:45 #2 g_wakeup_acknowledge (wakeup=0x95d8ae0) at /build/buildd/glib2.0-2.32.3/./glib/gwakeup.c:212 #3 0xb44f1bd2 in g_main_context_check (context=0xad3004e0, max_priority=2147483647, fds=0xad300df0, n_fds=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2980 #4 0xb44f2042 in g_main_context_iterate (dispatch=1, block=-1269826992, context=0xad3004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3143 #5 g_main_context_iterate (context=0xad3004e0, block=-1269826992, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #6 0xb44f2201 in g_main_context_iteration (context=0xad3004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #7 0xb624d8e7 in QEventDispatcherGlib::processEvents (this=0xad300468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #8 0xb621950d in QEventLoop::processEvents (this=0xadc1d270, flags=...) at kernel/qeventloop.cpp:149 #9 0xb62197a9 in QEventLoop::exec (this=0xadc1d270, flags=...) at kernel/qeventloop.cpp:204 #10 0xb610294c in QThread::exec (this=0x99d3df8) at thread/qthread.cpp:501 #11 0xb6102a3b in QThread::run (this=0x99d3df8) at thread/qthread.cpp:568 #12 0xb6105de0 in QThreadPrivate::start (arg=0x99d3df8) at thread/qthread_unix.cpp:298 #13 0xb5881d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #14 0xb5edface in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xac234b40 (LWP 3717)): #0 0xb7788424 in __kernel_vsyscall () #1 0xb5ed1380 in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0xb44ffa7b in g_poll (fds=0xab902278, nfds=1, timeout=-1) at /build/buildd/glib2.0-2.32.3/./glib/gpoll.c:132 #3 0xb44f20ae in g_main_context_poll (n_fds=1, fds=0xab902278, timeout=optimized out, context=0xab9004e0, priority=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3440 #4 g_main_context_iterate (dispatch=1, block=-1269826992, context=0xab9004e0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3141 #5 g_main_context_iterate (context=0xab9004e0, block=-1269826992, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #6 0xb44f2201 in g_main_context_iteration (context=0xab9004e0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #7 0xb624d8e7 in QEventDispatcherGlib::processEvents (this=0xab900468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #8 0xb621950d in QEventLoop::processEvents (this=0xac234240, flags=...) at kernel/qeventloop.cpp:149 #9 0xb62197a9 in QEventLoop::exec (this=0xac234240, flags=...) at kernel/qeventloop.cpp:204 #10 0xb610294c in QThread::exec (this=0x9d48de8) at thread/qthread.cpp:501 #11 0xb61f6b5d in QInotifyFileSystemWatcherEngine::run (this=0x9d48de8) at io/qfilesystemwatcher_inotify.cpp:248 #12 0xb6105de0 in QThreadPrivate::start (arg=0x9d48de8) at thread/qthread_unix.cpp:298 #13 0xb5881d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #14 0xb5edface in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb14b4740 (LWP 3705)): [KCrash Handler] #7 QModelIndex (other=...,
[Bug 218935] Cannot create subfolder in a root level in a Imap account
https://bugs.kde.org/show_bug.cgi?id=218935 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||chrig...@fastmail.fm Resolution|--- |DUPLICATE --- Comment #3 from Christian Mollekopf chrig...@fastmail.fm --- *** This bug has been marked as a duplicate of bug 292418 *** -- 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 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added CC||l...@alaxarxa.net --- Comment #13 from Christian Mollekopf chrig...@fastmail.fm --- *** Bug 218935 has been marked as a duplicate of this bug. *** -- 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 302139] New: ACLs of the root folder should be checked properly
https://bugs.kde.org/show_bug.cgi?id=302139 Bug ID: 302139 Severity: normal Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: ACLs of the root folder should be checked properly Classification: Unclassified OS: Linux Reporter: chrig...@fastmail.fm Hardware: Other Status: NEW Component: IMAP resource Product: Akonadi As response to 292418 the imap resource now allows creating folders for the root folder by default. Instead the proper flags (acl, noinferiors) should be checked as for all other folders. Reproducible: Always -- 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 302145] New: I cannot see a message without switch to html mode
https://bugs.kde.org/show_bug.cgi?id=302145 Bug ID: 302145 Severity: normal Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: I cannot see a message without switch to html mode Classification: Unclassified OS: Linux Reporter: dgl...@gmail.com Hardware: Mageia RPMs Status: UNCONFIRMED Component: general Product: kmail2 I received a message and firstly i thought that it has only one line (see screenshot). But i opened the message in the browser (gmail account) and i saw that the message has other lines that i could nt see in kmail. To see the content of the message i have to switch to html. I think that i have to be informed about that from kmail as it happens already in other messages in html format, where kmail suggests me to click in a link to see in html mode Reproducible: Sometimes Steps to Reproduce: It happened in a message that i received, i attach the source code of the message Actual Results: I dont see the content of the message in non html mode, kmail does nt propose me to see the message in html mode Expected Results: Show a link to click in order to see the message in html mode Some times i receive message in html format and kmail show them in a plain text mode, and some times with messages with html format kmail propose me a link to click ans see the message in a html format -- 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 302145] I cannot see a message without switch to html mode
https://bugs.kde.org/show_bug.cgi?id=302145 --- Comment #1 from Dimitrios Glentadakis dgl...@gmail.com --- Created attachment 71919 -- https://bugs.kde.org/attachment.cgi?id=71919action=edit Kmail shows only 1 line of the message -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 302145] I cannot see a message without switch to html mode
https://bugs.kde.org/show_bug.cgi?id=302145 --- Comment #2 from Dimitrios Glentadakis dgl...@gmail.com --- Created attachment 71920 -- https://bugs.kde.org/attachment.cgi?id=71920action=edit In the browser we see the message normaly -- 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 302145] I cannot see a message without switch to html mode
https://bugs.kde.org/show_bug.cgi?id=302145 --- Comment #3 from Dimitrios Glentadakis dgl...@gmail.com --- Created attachment 71921 -- https://bugs.kde.org/attachment.cgi?id=71921action=edit The source code of the message * I deleted some informations that was associated with my profile in this company and i wrote DELETED it their place. -- 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 302145] I cannot see a message without switch to html mode
https://bugs.kde.org/show_bug.cgi?id=302145 --- Comment #5 from Dimitrios Glentadakis dgl...@gmail.com --- Sorry but i wanted to delete a personal info in the attachement and when i saved it it made a new comment -- 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 302147] New: Kmail crash on startup
https://bugs.kde.org/show_bug.cgi?id=302147 Bug ID: 302147 Severity: normal Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crash on startup Classification: Unclassified OS: Linux Reporter: p...@kc.rr.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 The last two versions of kmail I've used always crash on startup. Current version is 4.8.4 release 511. The messages I get are as follows: *** QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kmail2(17002)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kmail2(17002)/kdepimlibs (mailtransport): Could not access Outbox. QObject: Cannot create children for a parent that is in a different thread. (Parent is Nepomuk::ResourceManager(0x90d580), parent's thread is QThread(0x60b7b0), current thread is QThread(0xb8b640) *** KMail got signal 11 (Exiting) *** Dead letters dumped. *** Application: kmail (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) release 511 Qt Version: 4.8.2 Operating System: Linux 3.3.4 x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: In detail, tell us what you were doing when the application crashed. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fa6cfd5b780 (LWP 17002))] Thread 5 (Thread 0x7fa6b14ad700 (LWP 17011)): #0 0x7fa6caebbe6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa6c155ac12 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7fa6c1ef91a0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7fa6c155ac49 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7fa6caeb7f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7fa6cd0ab10d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fa6b0b94700 (LWP 17012)): #0 0x7fa6caebb11f in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x7fa6c52b17a1 in g_mutex_unlock () from /opt/gnome/lib64/libglib-2.0.so.0 #2 0x7fa6c52767ea in g_main_context_iterate.isra.23 () from /opt/gnome/lib64/libglib-2.0.so.0 #3 0x7fa6c5276924 in g_main_context_iteration () from /opt/gnome/lib64/libglib-2.0.so.0 #4 0x7fa6ce709e36 in QEventDispatcherGlib::processEvents (this=0x7fa6ac0008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7fa6ce6d9842 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fa6ce6d9a97 in QEventLoop::exec (this=0x7fa6b0b93e00, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fa6ce5d95f7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7fa6ce5dc61b in QThreadPrivate::start (arg=0xc1a580) at thread/qthread_unix.cpp:307 #9 0x7fa6caeb7f05 in start_thread () from /lib64/libpthread.so.0 #10 0x7fa6cd0ab10d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fa66af1e700 (LWP 17018)): #0 0x7fa6caebc1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa6ce5dca8f in wait (time=3, this=0xc29b00) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0xc29a78, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fa6ce5cfe9f in QThreadPoolThread::run (this=0xb8b640) at concurrent/qthreadpool.cpp:141 #4 0x7fa6ce5dc61b in QThreadPrivate::start (arg=0xb8b640) at thread/qthread_unix.cpp:307 #5 0x7fa6caeb7f05 in start_thread () from /lib64/libpthread.so.0 #6 0x7fa6cd0ab10d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fa66a18d700 (LWP 17024)): #0 0x7fa6caebc1eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa6ce5dca8f in wait (time=3, this=0x1072cf0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x10768e8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fa6ce5cfe9f in QThreadPoolThread::run (this=0x1077510) at concurrent/qthreadpool.cpp:141 #4 0x7fa6ce5dc61b in QThreadPrivate::start (arg=0x1077510) at thread/qthread_unix.cpp:307 #5 0x7fa6caeb7f05 in start_thread () from /lib64/libpthread.so.0 #6 0x7fa6cd0ab10d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fa6cfd5b780 (LWP 17002)): [KCrash Handler] #6 0x7fa6cf1fcfff in ?? () from /usr/lib64/libkdecore.so.5 #7 0x7fa6ce5da5ed in QThreadStorageData::set (this=0x1125ec0, p=0xa33090) at thread/qthreadstorage.cpp:165 #8 0x7fa6cf1fbd77 in ?? () from /usr/lib64/libkdecore.so.5 #9 0x7fa6cf1fb2e2 in
[Bug 302148] New: Akonadi IMAP crashes after entering password
https://bugs.kde.org/show_bug.cgi?id=302148 Bug ID: 302148 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Akonadi IMAP crashes after entering password Classification: Unclassified OS: Linux Reporter: vojtech.zei...@opensuse.org Hardware: openSUSE RPMs Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.4 (4.8.4) release 511 Qt Version: 4.8.2 Operating System: Linux 3.1.10-1.9-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: Akonadi IMAP noticed some error when logging to IMAP server. One of proposed solutions was re-entering of password. I did not change the password, but I choose the possibility to enter it again. After entering the password, Akonadi IMAP crashed. -- Backtrace: Application: gmail-vojta.scz typu E-mailový IMAP server (akonadi_imap_resource), signal: Segmentation fault [KCrash Handler] #6 0x7f3d77675e90 in vtable for KPasswordDialog () from /usr/lib64/libkdeui.so.5 #7 0x7f3d79de1438 in QObject::connect (sender=0x82bda0, signal=0x469808 2stateChanged(KIMAP::Session::State,KIMAP::Session::State), receiver=0x86cc30, method=0x4697c0 1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State), type=Qt::AutoConnection) at kernel/qobject.cpp:2560 #8 0x004562eb in SessionPool::onPasswordRequestDone (this=0x86cc30, resultType=optimized out, password=...) at /usr/src/debug/kdepim-runtime-4.8.4/resources/imap/sessionpool.cpp:335 #9 0x00458087 in SessionPool::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at /usr/src/debug/kdepim-runtime-4.8.4/build/resources/imap/sessionpool.moc:94 #10 0x7f3d79ddfc41 in QMetaObject::activate (sender=0x86be20, m=optimized out, local_signal_index=optimized out, argv=0x7fffd351f4d0) at kernel/qobject.cpp:3556 #11 0x004436a1 in PasswordRequesterInterface::done (this=optimized out, _t1=0, _t2=optimized out) at /usr/src/debug/kdepim-runtime-4.8.4/build/resources/imap/passwordrequesterinterface.moc:118 #12 0x00422633 in SettingsPasswordRequester::onPasswordRequestCompleted (this=0x86be20, password=..., userRejected=false) at /usr/src/debug/kdepim-runtime-4.8.4/resources/imap/settingspasswordrequester.cpp:89 #13 0x7f3d79ddfc41 in QMetaObject::activate (sender=0x8708d0, m=optimized out, local_signal_index=optimized out, argv=0x7fffd351f670) at kernel/qobject.cpp:3556 #14 0x00420f71 in Settings::passwordRequestCompleted (this=optimized out, _t1=optimized out, _t2=false) at /usr/src/debug/kdepim-runtime-4.8.4/build/resources/imap/settings.moc:124 #15 0x0042153d in Settings::onDialogFinished (this=0x8708d0, result=optimized out) at /usr/src/debug/kdepim-runtime-4.8.4/resources/imap/settings.cpp:164 #16 0x00421743 in Settings::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at /usr/src/debug/kdepim-runtime-4.8.4/build/resources/imap/settings.moc:74 #17 0x7f3d79ddfc41 in QMetaObject::activate (sender=0x73d060, m=optimized out, local_signal_index=optimized out, argv=0x7fffd351f850) at kernel/qobject.cpp:3556 #18 0x7f3d7961b28e in QDialog::finished (this=optimized out, _t1=1) at .moc/release-shared/moc_qdialog.cpp:153 #19 0x7f3d7961b32a in QDialog::done (this=optimized out, r=1) at dialogs/qdialog.cpp:597 #20 0x7f3d771e2b69 in KPasswordDialog::KPasswordDialogPrivate::actuallyAccept (this=0x8ae6e0) at /usr/src/debug/kdelibs-4.8.4/kdeui/dialogs/kpassworddialog.cpp:404 #21 0x7f3d79de4e06 in QObject::event (this=0x73d060, e=optimized out) at kernel/qobject.cpp:1204 #22 0x7f3d7919f07b in QWidget::event (this=0x73d060, event=0x9cfb20) at kernel/qwidget.cpp:8830 #23 0x7f3d7914efe4 in notify_helper (e=0x9cfb20, receiver=0x73d060, this=0x6ab7a0) at kernel/qapplication.cpp:4551 #24 QApplicationPrivate::notify_helper (this=0x6ab7a0, receiver=0x73d060, e=0x9cfb20) at kernel/qapplication.cpp:4523 #25 0x7f3d79153db3 in QApplication::notify (this=0x7fffd35204e0, receiver=0x73d060, e=0x9cfb20) at kernel/qapplication.cpp:4412 #26 0x7f3d77267746 in KApplication::notify (this=0x7fffd35204e0, receiver=0x73d060, event=0x9cfb20) at /usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311 #27 0x7f3d79dcbd0c in QCoreApplication::notifyInternal (this=0x7fffd35204e0, receiver=0x73d060, event=0x9cfb20) at kernel/qcoreapplication.cpp:915 #28 0x7f3d79dcf5ba in sendEvent (event=0x9cfb20, receiver=0x73d060) at kernel/qcoreapplication.h:231 #29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x688e50) at kernel/qcoreapplication.cpp:1539 #30 0x7f3d79dfa9a3 in sendPostedEvents () at kernel/qcoreapplication.h:236 #31
[Bug 105012] Comments in Content-Transfer-Encoding are not ignored
https://bugs.kde.org/show_bug.cgi?id=105012 Rolf Eike Beer k...@opensource.sf-tec.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Rolf Eike Beer k...@opensource.sf-tec.de --- Works in 4.8.4 now. -- 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 112641] Messages opened in extra windows are closed when expiring groups
https://bugs.kde.org/show_bug.cgi?id=112641 Rolf Eike Beer k...@opensource.sf-tec.de changed: What|Removed |Added Status|UNCONFIRMED |NEW Version|unspecified |4.8 Ever confirmed|0 |1 --- Comment #2 from Rolf Eike Beer k...@opensource.sf-tec.de --- Still in KDE SC 4.8.4 -- 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 282259] kontact quits even if Cancel is choose after Are you sure you want to quit Kontact?
https://bugs.kde.org/show_bug.cgi?id=282259 --- Comment #3 from Dario Cambié dariocam...@gmail.com --- Review Request #102503 fixes the issue for me (and explain the cause). -- 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 302153] New: Crashed when saving an attachment
https://bugs.kde.org/show_bug.cgi?id=302153 Bug ID: 302153 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crashed when saving an attachment Classification: Unclassified OS: Linux Reporter: tsdg...@terra.es Hardware: Ubuntu Packages Status: NEW Component: general Product: kmail2 Application: kmail (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.0-25-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: I was saving an attachment and whn trying to save it kmail crashed. Tried to reproduce it again with the same email and then it worked The crash does not seem to be reproducible. -- 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 0x7f577cec87c0 (LWP 4005))] Thread 7 (Thread 0x7f575a617700 (LWP 4011)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f576f1c8dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f576f1c8f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f5777d00e9a in start_thread (arg=0x7f575a617700) at pthread_create.c:308 #4 0x7f577a2314bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 6 (Thread 0x7f5759d16700 (LWP 4012)): #0 0x7f5777d0405d in __pthread_mutex_unlock_usercnt (mutex=optimized out, decr=optimized out) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f5754000a60) at pthread_mutex_unlock.c:290 #2 0x7f5772b105d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5772ad498b in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5772ad4faa in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5772ad5164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f577abbc426 in QEventDispatcherGlib::processEvents (this=0x7f57540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7f577ab8bc82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f577ab8bed7 in QEventLoop::exec (this=0x7f5759d15dc0, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f577aa8afa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #10 0x7f577aa8dfcb in QThreadPrivate::start (arg=0x2338ca0) at thread/qthread_unix.cpp:298 #11 0x7f5777d00e9a in start_thread (arg=0x7f5759d16700) at pthread_create.c:308 #12 0x7f577a2314bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 5 (Thread 0x7f5712f68700 (LWP 4046)): #0 0x7f577a225b03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5772ad5036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5772ad5164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f577abbc3bf in QEventDispatcherGlib::processEvents (this=0x7f57040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f577ab8bc82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f577ab8bed7 in QEventLoop::exec (this=0x7f5712f67d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f577aa8afa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f577ab6b9ff in QInotifyFileSystemWatcherEngine::run (this=0x25a3890) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f577aa8dfcb in QThreadPrivate::start (arg=0x25a3890) at thread/qthread_unix.cpp:298 #9 0x7f5777d00e9a in start_thread (arg=0x7f5712f68700) at pthread_create.c:308 #10 0x7f577a2314bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 4 (Thread 0x7f5703436700 (LWP 9565)): #0 0x7f577a225b03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5772ad5036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5772ad5164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f577abbc3bf in QEventDispatcherGlib::processEvents (this=0x7f56f4002980, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f577ab8bc82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f577ab8bed7 in QEventLoop::exec (this=0x7f5703435d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f577aa8afa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f577ab6b9ff in QInotifyFileSystemWatcherEngine::run (this=0xffd9260) at
[Bug 289548] Kmail crashed when getting new mail
https://bugs.kde.org/show_bug.cgi?id=289548 S. Burmeister sven.burmeis...@gmx.net changed: What|Removed |Added CC||sven.burmeis...@gmx.net -- 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 289548] Kmail crashed when getting new mail
https://bugs.kde.org/show_bug.cgi?id=289548 --- Comment #1 from S. Burmeister sven.burmeis...@gmx.net --- Created attachment 71927 -- https://bugs.kde.org/attachment.cgi?id=71927action=edit New crash information added by DrKonqi kmail (4.8.3) on KDE Platform 4.8.3 (4.8.3) release 504 using Qt 4.8.1 - What I was doing when the application crashed: Kmail crashed while getting new email. It found some akonadi conflict and crashed after I clicked on keep right version. -- Backtrace (Reduced): #6 isSignalConnected (signal_index=2, this=0x9) at kernel/qobject_p.h:232 [...] #8 0x7f90f3c96030 in useOtherItem (this=0x3cb2180) at /usr/src/debug/kdepimlibs-4.8.3/akonadi/conflicthandling/conflicthandler.cpp:121 #9 Akonadi::ConflictHandler::resolve (this=0x3cb2180) at /usr/src/debug/kdepimlibs-4.8.3/akonadi/conflicthandling/conflicthandler.cpp:88 #10 0x7f90f8be92b6 in QObject::event (this=0x3cb2180, e=optimized out) at kernel/qobject.cpp:1204 #11 0x7f90f7f550d4 in notify_helper (e=0x3c1e330, receiver=0x3cb2180, this=0x65f6d0) at kernel/qapplication.cpp:4554 -- 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 302159] New: Cursor hot-spot wrongly positioned when dragging emails around.
https://bugs.kde.org/show_bug.cgi?id=302159 Bug ID: 302159 Severity: normal Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Cursor hot-spot wrongly positioned when dragging emails around. Classification: Unclassified OS: Linux Reporter: se...@netspace.net.au Hardware: openSUSE RPMs Status: UNCONFIRMED Component: UI Product: kmail2 When clicking and dragging old emails from message list to trash folder, the cursor hot-spot is placed in the MIDDLE of the arrow-head. The same is true when the ensuing dialog prompts for Move here, Copy here or Cancel options. One has to be very careful to avoid mistakenly selecting a neighboring field. This might account for other bug reports which state that when moving an email, the original is kept. This is probably caused by Copy here being mistakenly selected, due to the hot-spot offset error, as mentioned above. Reproducible: Always Steps to Reproduce: 1. Click on an email subject heading line. 2. Drag it to the Trash (for example) folder and HOVER without releasing. 3. Note how the box outline changes as you move the cursor gently up and down. 4. From this one can deduce the cursor's hotspot position. 5. Release the mouse button to drop the email. 6. Note the same occurs during the ensuing Move, Copy, Cancel pop-up dialog. Actual Results: Wong widgets or destinations can be selected. Expected Results: World peace, immortality, endless pleasure. I am impressed with the job you have done. It's good and getting better. -- 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 302166] New: Crash Kmail by open Mail
https://bugs.kde.org/show_bug.cgi?id=302166 Bug ID: 302166 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash Kmail by open Mail Classification: Unclassified OS: Linux Reporter: mathiaswi...@gmx.de Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) release 511 Qt Version: 4.8.2 Operating System: Linux 3.1.10-1.9-desktop i686 Distribution: openSUSE 12.1 (i586) -- Information about the crash: - What I was doing when the application crashed: Kernel: Linux 3.1.10-1.9-desktop i686 Distribution: openSUSE 12.1 (i586) KDE: 4.8.4 (4.8.4) release 511 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb17c0710 (LWP 12846))] Thread 3 (Thread 0xb0060b70 (LWP 12911)): #0 0xb5916782 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0xb5f0c5cc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #2 0xb390e189 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0xb390e1cf in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xb5912a7d in start_thread () from /lib/libpthread.so.0 #5 0xb5efeabe in clone () from /lib/libc.so.6 Thread 2 (Thread 0xaf738b70 (LWP 12912)): #0 0xb4631c90 in clock_gettime () from /lib/librt.so.1 #1 0xb6c52c35 in do_gettime (frac=0xaf738090, sec=0xaf738088) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb6d3c486 in QTimerInfoList::updateCurrentTime (this=0xaed01abc) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb6d3c076 in timerSourceCheckHelper (src=0xaed01a88) at kernel/qeventdispatcher_glib.cpp:150 #5 timerSourceCheckHelper (src=0xaed01a88) at kernel/qeventdispatcher_glib.cpp:144 #6 0xb4578af4 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #7 0xb45794c0 in ?? () from /usr/lib/libglib-2.0.so.0 #8 0xb45797fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0xb6d3bb47 in QEventDispatcherGlib::processEvents (this=0xaed00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0xb6d0764d in QEventLoop::processEvents (this=0xaf7382d0, flags=...) at kernel/qeventloop.cpp:149 #11 0xb6d078e9 in QEventLoop::exec (this=0xaf7382d0, flags=...) at kernel/qeventloop.cpp:204 #12 0xb6bf0dac in QThread::exec (this=0x8372cf0) at thread/qthread.cpp:501 #13 0xb6bf0e9b in QThread::run (this=0x8372cf0) at thread/qthread.cpp:568 #14 0xb6bf4290 in QThreadPrivate::start (arg=0x8372cf0) at thread/qthread_unix.cpp:307 #15 0xb5912a7d in start_thread () from /lib/libpthread.so.0 #16 0xb5efeabe in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb17c0710 (LWP 12846)): [KCrash Handler] #6 deref (this=0xb26bb5ac) at /usr/include/QtCore/qatomic_i386.h:132 #7 ~KSharedPtr (this=0x83b23a0, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.8.4/kdecore/util/ksharedptr.h:90 #8 ~ParsingData (this=0x83b23a0, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/ktraderparse.cpp:40 #9 qThreadStorage_deleteDataKTraderParse::ParsingData (d=0x83b23a0) at /usr/include/QtCore/qthreadstorage.h:97 #10 QThreadStorageKTraderParse::ParsingData*::deleteData (x=0x83b23a0) at /usr/include/QtCore/qthreadstorage.h:140 #11 0xb6bf1f42 in QThreadStorageData::set (this=0x8849e30, p=0x8ad2720) at thread/qthreadstorage.cpp:165 #12 0xb71fe1d9 in qThreadStorage_setLocalDataKTraderParse::ParsingData (d=optimized out, t=optimized out) at /usr/include/QtCore/qthreadstorage.h:92 #13 setLocalData (t=0x8ad2720, this=optimized out) at /usr/include/QtCore/qthreadstorage.h:155 #14 KTraderParse::parseConstraints (_constr=...) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/ktraderparse.cpp:55 #15 0xb71fd655 in applyConstraints (constraint=..., lst=...) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/kservicetypetrader.cpp:59 #16 KServiceTypeTrader::applyConstraints (lst=..., constraint=...) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/kservicetypetrader.cpp:53 #17 0xb71fd84f in KServiceTypeTrader::defaultOffers (this=0x82b8528, serviceType=..., constraint=...) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/kservicetypetrader.cpp:127 #18 0xb71fe060 in KServiceTypeTrader::query (this=0x82b8528, serviceType=..., constraint=...) at /usr/src/debug/kdelibs-4.8.4/kdecore/services/kservicetypetrader.cpp:141 #19 0xb26f4e7f in KEmoticonsPrivate::loadServiceList (this=0x8a3cbc0) at /usr/src/debug/kdelibs-4.8.4/kutils/kemoticons/kemoticons.cpp:71 #20 0xb26f5001 in KEmoticons::KEmoticons (this=0x8d008e8) at /usr/src/debug/kdelibs-4.8.4/kutils/kemoticons/kemoticons.cpp:121 #21 0xb4a2bd55 in operator- (this=optimized out) at /usr/src/debug/kdepimlibs-4.8.4/kpimutils/linklocator.cpp:56 #22 KPIMUtils::LinkLocator::convertToHtml (plainText=..., flags=3, maxUrlLen=4096, maxAddressLen=255) at
