[Bug 44880] would like to be able to strip tags from html messages
https://bugs.kde.org/show_bug.cgi?id=44880 --- Comment #19 from2011-08-14 07:02:13 --- Torgny in #17, I am going blind. I want a screen reader. It will be easier to get a screen reader working properly if the intermediate step proposed above is already working. Sadly other people _send_ emails that do not conform to RFCs, or my taste. :-( There is nothing that we can do to stop them. I would strongly oppose generating non-standard messages. Do you really object to displaying messages any way that the recipient likes, or even needs? Christian in #18, How is your script supposed to be installed and used? Should it just be copied to somewhere on $PATH? -- 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 209604] Crash when opening the settings dialog if the KMail module was previously disabled
https://bugs.kde.org/show_bug.cgi?id=209604 Fabian Badoi changed: What|Removed |Added CC|fabian.ba...@gmail.com | -- 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 280011] Akonadi Agent (akonadi_nepomuk_email_feeder) crash on shutdown
https://bugs.kde.org/show_bug.cgi?id=280011 Christoph changed: What|Removed |Added CC||cis...@online.ms -- 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 278020] KMail cannot send e-mail via SMTP
https://bugs.kde.org/show_bug.cgi?id=278020 --- Comment #11 from Matthias 2011-08-14 11:14:09 --- After trying things like deleting the directory .local/share/akonad, regenerating settings for my mail accounts in kmail, I still could not send messages yesterday. After rebooting this morning and logging in, however, I saw a pop up message saying that my message in the outbox folder was sent. Very strange... At the same time I saw some virtuoso processes running. Anyway, I do not know exactly why, but now kmail can send messages. -- 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 247615] gcal shows wrong error message on network problems and too often
https://bugs.kde.org/show_bug.cgi?id=247615 yartsa changed: What|Removed |Added CC||yar...@clovermail.net --- Comment #6 from yartsa 2011-08-14 11:31:51 --- I confirm Comment #5 in my kde 4.7 also. -- 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 280069] New: Update folders
https://bugs.kde.org/show_bug.cgi?id=280069 Summary: Update folders Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: the_a...@gmx.de Application: kmail (4.7.0 ) KDE Platform Version: 4.7.00 (4.7.0) Qt Version: 4.7.2 Operating System: Linux 2.6.38-10-generic x86_64 Distribution: Ubuntu 11.04 -- Information about the crash: - What I was doing when the application crashed: First, Kmail-migrator started and successfully ended. Next, open kmail and update local folder and subfolder. Now, i haved wait for finish. Progressbar started sometimes and go to end. Now, Crash. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f5be1dd77a0 (LWP 5834))] Thread 3 (Thread 0x7f5bc3ebc700 (LWP 5838)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f5bd40e1832 in ?? () from /usr/lib/libQtWebKit.so.4 #2 0x7f5bdcd65d8c in start_thread (arg=0x7f5bc3ebc700) at pthread_create.c:304 #3 0x7f5bdf1b604d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #4 0x in ?? () Thread 2 (Thread 0x7f5bc0810700 (LWP 5843)): #0 0x7f5bdcd683a3 in __pthread_mutex_lock (mutex=0x2c3db88) at pthread_mutex_lock.c:51 #1 0x7f5bd7a39624 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5bdfb06446 in QEventDispatcherGlib::processEvents (this=0x23231e0, flags=) at kernel/qeventdispatcher_glib.cpp:424 #3 0x7f5bdfada882 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #4 0x7f5bdfadaabc in QEventLoop::exec (this=0x7f5bc080fdb0, flags=...) at kernel/qeventloop.cpp:201 #5 0x7f5bdf9f1924 in QThread::exec (this=) at thread/qthread.cpp:492 #6 0x7f5bdfabcc2f in QInotifyFileSystemWatcherEngine::run (this=0x2c3bba0) at io/qfilesystemwatcher_inotify.cpp:248 #7 0x7f5bdf9f4175 in QThreadPrivate::start (arg=0x2c3bba0) at thread/qthread_unix.cpp:320 #8 0x7f5bdcd65d8c in start_thread (arg=0x7f5bc0810700) at pthread_create.c:304 #9 0x7f5bdf1b604d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 1 (Thread 0x7f5be1dd77a0 (LWP 5834)): [KCrash Handler] #6 operator== (this=0x2334b30, item=0x34e2c80) at /usr/include/qt4/QtCore/qbasicatomic.h:70 #7 data (this=0x2334b30, item=0x34e2c80) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:565 #8 parent (this=0x2334b30, item=0x34e2c80) at ../../libkdepim/progressmanager.h:61 #9 KPIM::StatusbarProgressWidget::slotProgressItemCompleted (this=0x2334b30, item=0x34e2c80) at ../../libkdepim/statusbarprogresswidget.cpp:161 #10 0x7f5bd96f60c4 in KPIM::StatusbarProgressWidget::qt_metacall (this=0x2334b30, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff69424e80) at ./statusbarprogresswidget.moc:90 #11 0x7f5bdfaf05f8 in QMetaObject::activate (sender=0x22f5f20, m=, local_signal_index=, argv=0x7fff69424e80) at kernel/qobject.cpp:3287 #12 0x7f5bd96f1a42 in KPIM::ProgressManager::progressItemCompleted (this=, _t1=0x34e2c80) at ./progressmanager.moc:272 #13 0x7f5bd96f2533 in KPIM::ProgressManager::qt_metacall (this=0x22f5f20, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff69424f90) at ./progressmanager.moc:246 #14 0x7f5bdfaf05f8 in QMetaObject::activate (sender=0x34e2c80, m=, local_signal_index=, argv=0x7fff69424f90) at kernel/qobject.cpp:3287 #15 0x7f5bd96f1612 in KPIM::ProgressItem::progressItemCompleted (this=, _t1=0x34e2c80) at ./progressmanager.moc:121 #16 0x7f5bd96f1d10 in KPIM::ProgressItem::setComplete (this=0x34e2c80) at ../../libkdepim/progressmanager.cpp:55 #17 0x7f5bd96f3589 in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x3c5d3c0, instance=...) at ../../libkdepim/agentprogressmonitor.cpp:87 #18 0x7f5bd96f36fa in KPIM::AgentProgressMonitor::qt_metacall (this=0x3c5d260, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff694250d0) at ./agentprogressmonitor.moc:78 #19 0x7f5bdfaf05f8 in QMetaObject::activate (sender=0x2558140, m=, local_signal_index=, argv=0x7fff694250d0) at kernel/qobject.cpp:3287 #20 0x7f5bdbc37ba5 in Akonadi::AgentManager::instanceStatusChanged (this=, _t1=) at ./agentmanager.moc:177 #21 0x7f5bdbc3c2ff in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged (this=0x22d5b80, identifier=, status=2, msg=...) at ../../akonadi/agentmanager.cpp:129 #22 0x7f5bdbc3e7de in Akonadi::AgentManager::qt_metacall (this=0x2558140, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff69425240) at ./agentmanager.moc:131 #23 0x7f5bdfaf05f8 in QMetaObject::activate (sender=0x24fe880, m=, local_signal_index=, argv=0x7fff69425240) at kernel/qobject.cpp:3287 #24 0x7f5bdbd5970b in OrgFreedesktopAkona
[Bug 275736] Sending mail hangs if KWallet has been closed and reopened by another application
https://bugs.kde.org/show_bug.cgi?id=275736 tim blechmann changed: What|Removed |Added CC||t...@klingt.org --- Comment #1 from tim blechmann 2011-08-14 13:09:48 --- similar issue here, and it could be related to kwallet (usually my kmail has the permissions to access the wallet) mails stay in the outbox forever until i killall akonadi_maildispatcher_agent -- 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 139088] running kmail with any other web-client on the same account creates duplicate new messages
https://bugs.kde.org/show_bug.cgi?id=139088 --- Comment #6 from tim blechmann 2011-08-14 13:11:20 --- still a problem with kmail2 -- 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 280075] New: KMail does not show messages from Domain Factory IMAP account
https://bugs.kde.org/show_bug.cgi?id=280075 Summary: KMail does not show messages from Domain Factory IMAP account Product: kmail2 Version: 4.7 Platform: Archlinux Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@klomp.eu Version: 4.7 (using KDE 4.7.0) OS:Linux I added an new IMAP account which is hosted by Domain Factory using sslmailpool.ispgateway.de Authentication works without problems and KMail shows the correct folder tree. However, no message is shown in any of the folder. I also tried to configure disconnected IMAP. Again, the folders are shown but not the mails. Interestingly, KMail does not try to download any mails: I watched the traffic, but almost nothing is downloaded altough the IMAP account contains approx 2GiB of data. Thereafter I tried it with another account from another hoster and everything works as expected. Reproducible: Always Steps to Reproduce: Create IMAP account using Domain Factory as hoster. Actual Results: No mails shown in folders. Expected Results: Downloading a lot of data and showing the mails. -- 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 44880] would like to be able to strip tags from html messages
https://bugs.kde.org/show_bug.cgi?id=44880 Torgny Nyblom changed: What|Removed |Added Component|messageviewer |messageviewer Version|1.4.1 |unspecified Product|kmail |kdepim --- Comment #20 from Torgny Nyblom 2011-08-14 14:25:16 --- (In reply to comment #19) > I want a screen reader. It will be easier to get a screen reader working > properly if the intermediate step proposed above is already working. > > Sadly other people _send_ emails that do not conform to RFCs, or my taste. > :-( Use case for helping screen readers: Yes that is a valid argument in my book. Fixing mails that do not conform to personal taste is not. > There is nothing that we can do to stop them. I would strongly oppose > generating non-standard messages. Do you really object to displaying messages > any way that the recipient likes - yes, the formatting of a mail is up to the sender to decide, also any reformatting means more code for us to maintain. >, or even needs? - no, due to that I'll see what I can do. -- 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 280075] KMail does not show messages from Domain Factory IMAP account
https://bugs.kde.org/show_bug.cgi?id=280075 --- Comment #1 from Torgny Nyblom 2011-08-14 14:26:58 --- Please attach a copy of the commands sent between akonadi and the server. -- 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 259439] Kmail2 gets stuck retrieving folder
https://bugs.kde.org/show_bug.cgi?id=259439 Alvise changed: What|Removed |Added CC||pub...@alvise.ch --- Comment #3 from Alvise 2011-08-14 16:43:13 --- Still there with kmail2 4.7.0 If I launch kmail from the command menu, I get the following message when kmail becomes stuck retrieving folder contents: kmail2(8586) MessageViewer::ContactPhotoMemento::slotSearchJobFinished: Unable to fetch photo for contact: "Item query returned empty result set" -- 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 257970] Message won't be shown in preview pane
https://bugs.kde.org/show_bug.cgi?id=257970 Alvise changed: What|Removed |Added CC||pub...@alvise.ch --- Comment #14 from Alvise 2011-08-14 16:47:06 --- Still there with kmail2 4.7.0 If I launch kmail from the command menu, I get the following message when kmail becomes stuck retrieving folder contents: kmail2(8586) MessageViewer::ContactPhotoMemento::slotSearchJobFinished: Unable to fetch photo for contact: "Item query returned empty result set" -- 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 139088] running kmail with any other web-client on the same account creates duplicate new messages
https://bugs.kde.org/show_bug.cgi?id=139088 Bent Bisballe Nyeng changed: What|Removed |Added CC|d...@aasimon.org| -- 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 270141] Distribution lists can't be used from kmail
https://bugs.kde.org/show_bug.cgi?id=270141 enge...@sunrise.ch changed: What|Removed |Added CC||enge...@sunrise.ch --- Comment #2 from2011-08-14 18:09:09 --- I found a work-around in a forum: Add an empty space before each name in the list. (OpenSuse 11.4, kde 4.6.5 rel 7, kontact 4.4.11, kmail 1.13.7) Kurt -- 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 277859] kmail2 does not remove the "sending failed" message from emails
https://bugs.kde.org/show_bug.cgi?id=277859 Martin Bednar changed: What|Removed |Added CC||seraf...@gmail.com --- Comment #1 from Martin Bednar 2011-08-14 18:26:54 --- I can confirm this. Kmail 4.7.0. -- 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 280090] New: kmail crashed at start
https://bugs.kde.org/show_bug.cgi?id=280090
Summary: kmail crashed at start
Product: kmail2
Version: 4.8 pre
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de
Application: kmail (4.8 pre)
KDE Platform Version: 4.7.41 (4.7.41 (KDE 4.8 >= 20110807) (Compiled from
sources)
Qt Version: 4.7.1
Operating System: Linux 3.0.0 x86_64
Distribution: Debian GNU/Linux 5.0.8 (lenny)
-- Information about the crash:
I tried to start kmail but it crashed. The used version is from git.
-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 0 (LWP 3959)]
Thread 2 (Thread 0x40d56950 (LWP 3963)):
#0 0x7fc239630d29 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
#1 0x7fc231dc96ca in WTF::TCMalloc_PageHeap::scavengerThread () from
/home/kde-devel/qt4/lib/libQtWebKit.so.4
#2 0x7fc231dc9753 in WTF::TCMalloc_PageHeap::runScavengerThread () from
/home/kde-devel/qt4/lib/libQtWebKit.so.4
#3 0x7fc23962cfc7 in start_thread () from /lib/libpthread.so.0
#4 0x7fc238bfd64d in clone () from /lib/libc.so.6
#5 0x in ?? ()
Thread 1 (Thread 0x7fc23fb8a740 (LWP 3959)):
[KCrash Handler]
#6 0x7fc23a8705e2 in QScopedPointer >::data (this=0x8) at
../../include/QtCore/../../../../qt-copy/src/corelib/tools/qscopedpointer.h:135
#7 0x7fc23a869e11 in qGetPtrHelper > > (p=@0x8) at
../../include/QtCore/../../../../qt-copy/src/corelib/global/qglobal.h:2338
#8 0x7fc23a87061d in QAction::d_func (this=0x0) at
../../include/QtGui/../../../../qt-copy/src/gui/kernel/qaction.h:67
#9 0x7fc23a86c20b in QAction::setText (this=0x0, text=@0x7fffcc0096d0) at
/home/kde-devel/kdesvn/qt-copy/src/gui/kernel/qaction.cpp:814
#10 0x7fc23e98e621 in KMMainWidget::updateFolderMenu (this=0x6a14a0) at
/home/kde-devel/kdesvn/kdepim/kmail/kmmainwidget.cpp:3839
#11 0x7fc23e995350 in KMMainWidget::setupActions (this=0x6a14a0) at
/home/kde-devel/kdesvn/kdepim/kmail/kmmainwidget.cpp:3426
#12 0x7fc23e997b44 in KMMainWidget (this=0x6a14a0, parent=, aGUIClient=0x6a7390, actionCollection=, config={d =
0x7fffcc00b430})
at /home/kde-devel/kdesvn/kdepim/kmail/kmmainwidget.cpp:246
#13 0x7fc23e8e4bfb in KMMainWin (this=0x6a7330) at
/home/kde-devel/kdesvn/kdepim/kmail/kmmainwin.cpp:63
#14 0x7fc23e947027 in KMKernel::openReader (this=0x7fffcc00d4e0,
onlyCheck=false) at /home/kde-devel/kdesvn/kdepim/kmail/kmkernel.cpp:552
#15 0x7fc23e94e148 in KMKernel::action (this=0x7fffcc00d4e0, mailto=, check=208, to=@0x7fffcc00bbf0, cc=@0x7fffcc00bbe0,
bcc=@0x7fffcc00bbd0, subj=@0x7fffcc00bbc0,
body=@0x7fffcc00bbb0, messageFile=@0x7fffcc00b7b0,
attachURLs=@0x7fffcc00bb90, customHeaders=@0x7fffcc00bba0) at
/home/kde-devel/kdesvn/kdepim/kmail/kmkernel.cpp:1288
#16 0x7fc23e94f372 in KMKernel::handleCommandLine (this=0x7fffcc00d4e0,
noArgsOpensReader=true) at /home/kde-devel/kdesvn/kdepim/kmail/kmkernel.cpp:471
#17 0x00403872 in KMailApplication::newInstance (this=0x7fffcc00d5c0)
at /home/kde-devel/kdesvn/kdepim/kmail/main.cpp:85
#18 0x7fc23f694de2 in KUniqueApplicationAdaptor::newInstance
(this=0x834e80, asn_id=, args=@0x8c73f0)
at /home/kde-devel/kdesvn/kdelibs/kdeui/kernel/kuniqueapplication.cpp:442
#19 0x7fc23f694e86 in KUniqueApplicationAdaptor::qt_metacall
(this=0x834e80, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fffcc00bf40)
at /home/kde-devel/kdesvn/build/kdelibs/kdeui/kuniqueapplication_p.moc:81
#20 0x7fc239dda7e1 in QDBusConnectionPrivate::deliverCall (this=0x64c290,
object=0x834e80, msg=@0xaeaea0, metaTypes=@0x7fffcc00c198, slotIdx=4)
at /home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:919
#21 0x7fc239ddb8a8 in QDBusConnectionPrivate::activateCall (this=0x64c290,
object=0x834e80, flags=337, msg=@0xaeaea0) at
/home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:822
#22 0x7fc239ddd993 in QDBusConnectionPrivate::activateObject
(this=0x64c290, node=@0xaeae78, msg=@0xaeaea0, pathStartPos=16) at
/home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:1379
#23 0x7fc239dddc00 in QDBusActivateObjectEvent::placeMetaCall
(this=0xaeae30) at
/home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:1493
#24 0x7fc239a2fd52 in QObject::event (this=0x7fffcc00d5c0, e=0xaeae30) at
/home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qobject.cpp:1219
#25 0x7fc239a13b59 in QCoreApplication::event (this=0x7fffcc00d5c0,
e=0xaeae30) at
/home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qcoreapplication.cpp:1561
#26 0x7fc23a87bc3f in QApplication::event (this=0x7fffcc00d5c0, e=0xaeae30)
at /home/kde-devel/kdesvn/qt-copy/src/gui/kernel/qapplication.cpp:2486
#27 0x7fc23a87503b in QApplicationPrivate::notify_helper (this=0x749ad0,
receiver=0x7fffcc00d5c0, e=0xaeae30) at
[Bug 280091] New: "Failed to fetch resource collection" on startup
https://bugs.kde.org/show_bug.cgi?id=280091 Summary: "Failed to fetch resource collection" on startup Product: kmail2 Version: Git (master) Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@rusu.info Version: Git (master) (using Devel) OS:Linux When I start kmail2, it displays a messageBox stating "KMail encountered a fatal error and will terminate now. The error was: Failed to fetch the resource collection." See: http://wstaw.org/m/2011/08/14/plasma-desktopee2398.jpg If I put the window on the side withoud closing it, KMail is fully operational. But if I click OK or close this box, KMail quits. Reproducible: Always Steps to Reproduce: Launch kmail Actual Results: KMail quits. Expected Results: KMail program ready to use. Please let me know what other information may be useful. I can provide quite all the needed information, as I'm running from git master. -- 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 280096] New: Crash soon after startup after migration to 4.7.0 and Akonadi
https://bugs.kde.org/show_bug.cgi?id=280096 Summary: Crash soon after startup after migration to 4.7.0 and Akonadi Product: kontact Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: maar...@treewalker.org Application: kontact (4.7.0) KDE Platform Version: 4.7.00 (4.7.0) "release 10" Qt Version: 4.7.3 Operating System: Linux 2.6.37.1-1.2-desktop x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: Today I migrated from KDE 4.6.x to 4.7.0 and also to a new Kontact/KMail. The conversion went fine, according to the migration wizard. I gave the migration tool one-time access to my KWallet and Akonadi forever access. However, KMail did prompt for my e-mail passwords soon after the migration was finished. This may have nothing to do with the crash, but I'm mentioning it just in case. When Kontact was running after the migration, it was very unresponsive and there was a lot of harddisk activity. It wasn't swapping, so it must have been activity on files. I saw some mails pop up in the Inbox with subjects in blue, which were later filtered out to the mailbox they belong in. After a while, Kontact crashed while I was reorganising the width of the different panes. I restarted Kontact and didn't touch it and it continued to do something that caused harddisk activity and a while later it crashed again. And now if I start it, it crashes within seconds of being launched. I'm using local maildir storage for most of my mail and I have also configured a GMail account via IMAP. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7ff59c4ab760 (LWP 9000))] Thread 2 (Thread 0x7ff585b26700 (LWP 9001)): #0 0x7ff59485438c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff598ed21d4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #2 0x7ff59484fa3f in start_thread () from /lib64/libpthread.so.0 #3 0x7ff599a7467d in clone () from /lib64/libc.so.6 #4 0x in ?? () Thread 1 (Thread 0x7ff59c4ab760 (LWP 9000)): [KCrash Handler] #6 0x7ff596cf5e15 in QList::clear() () from /usr/lib64/libakonadi-kde.so.4 #7 0x7ff596cb7435 in Akonadi::ItemFetchJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libakonadi-kde.so.4 #8 0x7ff59ae2da5f in QMetaObject::activate (sender=0x5c97ca0, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3278 #9 0x7ff59ae2d0a9 in QObject::event (this=0x5c97ca0, e=) at kernel/qobject.cpp:1181 #10 0x7ff59a1e1144 in QApplicationPrivate::notify_helper (this=0x6424a0, receiver=0x5c97ca0, e=0x7fff8fe21790) at kernel/qapplication.cpp:4462 #11 0x7ff59a1e96fa in QApplication::notify (this=, receiver=0x5c97ca0, e=0x7fff8fe21790) at kernel/qapplication.cpp:4341 #12 0x7ff59b85f736 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #13 0x7ff59ae1947c in QCoreApplication::notifyInternal (this=0x7fff8fe24730, receiver=0x5c97ca0, event=0x7fff8fe21790) at kernel/qcoreapplication.cpp:731 #14 0x7ff59ae46df8 in sendEvent (this=0x649280) at kernel/qcoreapplication.h:215 #15 QTimerInfoList::activateTimers (this=0x649280) at kernel/qeventdispatcher_unix.cpp:619 #16 0x7ff59ae43b54 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:184 #17 0x7ff5934debd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7ff5934df3b0 in ?? () from /lib64/libglib-2.0.so.0 #19 0x7ff5934df650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7ff59ae4422f in QEventDispatcherGlib::processEvents (this=0x612790, flags=) at kernel/qeventdispatcher_glib.cpp:422 #21 0x7ff59a286bae in QGuiEventDispatcherGlib::processEvents (this=, flags=) at kernel/qguieventdispatcher_glib.cpp:204 #22 0x7ff59ae188d2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #23 0x7ff59ae18ae5 in QEventLoop::exec (this=0x7fff8fe21aa0, flags=...) at kernel/qeventloop.cpp:201 #24 0x7ff59b2833c6 in KJob::exec() () from /usr/lib64/libkdecore.so.5 #25 0x7ff580c72060 in MailCommon::SearchRuleString::matchesInternal(QString const&) const () from /usr/lib64/libmailcommon.so.4 #26 0x7ff580c75220 in MailCommon::SearchRuleString::matches(Akonadi::Item const&) const () from /usr/lib64/libmailcommon.so.4 #27 0x7ff580c74380 in MailCommon::SearchPattern::matches(Akonadi::Item const&, bool) const () from /usr/lib64/libmailcommon.so.4 #28 0x7ff580c43d02 in MailCommon::FilterManager::Private::isMatching(Akonadi::Item const&, MailCommon::MailFilter const*) () from /usr/lib64/libmailcommo
[Bug 280096] Crash soon after startup after migration to 4.7.0 and Akonadi
https://bugs.kde.org/show_bug.cgi?id=280096 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org -- 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 280096] Crash soon after startup after migration to 4.7.0 and Akonadi
https://bugs.kde.org/show_bug.cgi?id=280096 --- Comment #1 from Maarten ter Huurne 2011-08-14 22:37:14 --- Created an attachment (id=62828) --> (http://bugs.kde.org/attachment.cgi?id=62828) New crash information added by DrKonqi kontact (4.7.0) on KDE Platform 4.7.00 (4.7.0) "release 10" using Qt 4.7.3 I just got another crash with the same symptoms but different methods at the top of the stack trace. So I attached it in case it gives a better picture of what is wrong. -- Backtrace (Reduced): #6 ~QVector (x=0x75584c0) at ../../src/corelib/tools/qvector.h:119 #7 ~QRegionPrivate (x=0x75584c0) at painting/qregion.cpp:1085 #8 QRegion::cleanUp (x=0x75584c0) at painting/qregion.cpp:3904 #9 0x7f1e797299d2 in QRegion::operator= (this=, r=...) at painting/qregion.cpp:3928 #10 0x7f1e79798be7 in QX11PaintEngine::begin (this=0xeb1d20, pdev=0x80cee8) at painting/qpaintengine_x11.cpp:504 -- 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 280096] Crash soon after startup after migration to 4.7.0 and Akonadi
https://bugs.kde.org/show_bug.cgi?id=280096 --- Comment #2 from Maarten ter Huurne 2011-08-14 22:47:31 --- Created an attachment (id=62829) --> (http://bugs.kde.org/attachment.cgi?id=62829) Third backtrace, again similar but not the same Attached a third backtrace. Is it normal to have a 400-level call stack or did recursion go wrong? MailCommon::SearchRuleString::matchesInternal is in this backtrace 13 times... -- 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 280096] Crash soon after startup after migration to 4.7.0 and Akonadi
https://bugs.kde.org/show_bug.cgi?id=280096 --- Comment #3 from Maarten ter Huurne 2011-08-14 23:59:32 --- Workaround found: if I edit ~/.kde4/share/config/kmail2rc to remove all my filters, KMail seems to be stable. -- 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 259574] conflict resolution box appears a lot
https://bugs.kde.org/show_bug.cgi?id=259574 --- Comment #22 from Hussam Al-Tayeb 2011-08-15 00:11:51 --- So if I understand correctly, there is more than one reason/bug which makes us see this behavior? Any instructions from the developers for what we users can do to capture some information we can submit when bug happens (i.e. conflict window shows)? -- 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 174034] Word wrapping in effect even when turned off
https://bugs.kde.org/show_bug.cgi?id=174034 Matt Whitlock changed: What|Removed |Added CC||k...@mattwhitlock.name --- Comment #4 from Matt Whitlock 2011-08-15 04:04:41 --- (In reply to comment #3) > This bug is especially annoying when sending patches. If the patch has long > lines, the composer window must be resized to be wide enough to prevent KMail > from wordwrapping and thus corrupting the patch when sending. Yes, exactly. And it's not just a problem when sending patches. The bottom line is that KMail should *NEVER* be inserting hard line breaks into messages unless word wrapping is enabled. If a line is wider than the composer window, it can soft-wrap in the composer window, but that is an issue of the *editor*, not the *document*. The size of my composer window should have absolutely no effect on the content of the message I ultimately send. And just to drive the point home, if I type a long paragraph of text that is greater than 1000 characters, KMail must throw out 7bit content transfer encoding as a possibility and use only quoted-printable or base64. It should *NOT* just throw in a hard line break wherever it wants to. Again, the *document* should be unchanged by whatever transfer encoding happens to be in use. For the record, the last version of KMail 1 that I used did all of this perfectly right. (In fact it was one of the few MUAs that actually did.) -- 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 280102] New: KMail doesn't handle HTML anchors (regression from kde 4.4)
https://bugs.kde.org/show_bug.cgi?id=280102 Summary: KMail doesn't handle HTML anchors (regression from kde 4.4) Product: kdepim Version: 4.6 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: messageviewer AssignedTo: kdepim-bugs@kde.org ReportedBy: ltski...@gmail.com Created an attachment (id=62832) --> (http://bugs.kde.org/attachment.cgi?id=62832) Sample message digest from Yahoo groups Version: 4.6 (using KDE 4.6.3) OS:Linux Yahoo groups sends e-mails as HTML with a table of contents at the top. Each entry in the table of contents is a HTML that references an farther down in the HTML. Kmail now doesn't jump-to those links when clicking on the table of contents. The only thing I see "funny" is that the HTML is sent as quoted-printable. Reproducible: Always Steps to Reproduce: Click on a TOC link. Actual Results: Nothing. Expected Results: Display jumps to the digest message. -- 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 252369] Can't login to Google IMAP Account
https://bugs.kde.org/show_bug.cgi?id=252369 --- Comment #3 from Blindauer Emmanuel 2011-08-15 05:34:48 --- I think this bug can be closed, as white spaces works now with 4.7.0 -- 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 258479] Akonadi IMAP resource not syncing after system startup/resume, requires Akonadi to be restarted
https://bugs.kde.org/show_bug.cgi?id=258479 Blindauer Emmanuel changed: What|Removed |Added CC||bugs.kde@mooby.net --- Comment #5 from Blindauer Emmanuel 2011-08-15 05:36:40 --- still happens with 4.7.0 sometimes, just restarting the resource in the akonadiconsole is sufficient. -- 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 280103] New: Inbox should be sync first
https://bugs.kde.org/show_bug.cgi?id=280103 Summary: Inbox should be sync first Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: bugs.kde@mooby.net CC: vkra...@kde.org, kdepim-bugs@kde.org Version: unspecified (using KDE 4.7.0) OS:Linux when having a very large list of folders, the 'INBOX' forder isn't the first of the list of all synched directories. It should be synced first, so the user will see mail in the inbox earlier (currently I wait 20s to see the INBOX sync coming) Reproducible: Always Expected Results: having the INBOX directory synced first and all other directories after it -- 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
