[Bug 193514] Crash when activating plugin
https://bugs.kde.org/show_bug.cgi?id=193514 --- Comment #53 from Christian Reiner reiner imageware de 2009-12-08 09:05:31 --- To comment #52: Why do you think it's random ? I tested again, the bug still exists in kde-4.3.4, behaves exactly as written in Comment #9. That means it is clearly reproduceable. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 169048] Crashes when applying all filters on IMAP folder
https://bugs.kde.org/show_bug.cgi?id=169048 Ralf Kleineisel r...@kleineisel.de changed: What|Removed |Added CC||r...@kleineisel.de --- Comment #20 from Ralf Kleineisel ralf kleineisel de 2009-12-08 09:35:20 --- This bugs exists in the current Fedora 12 kdepim package, too. I use KMail 1.23.1 from the kdepim-4.3.3-1.fc12.i686 package. KMail crashes several times a day when it tries to apply the filters to new mails. Here is the backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 contains (t=value optimized out, this=0xb04) at /usr/include/QtCore/qlist.h:667 #7 KMFilter::applyOnAccount (t=value optimized out, this=0xb04) at /usr/src/debug/kdepim-4.3.3/kmail/kmfilter.cpp:217 #8 0x009f4b62 in KMail::ActionScheduler::filterMessage (this=value optimized out) at /usr/src/debug/kdepim-4.3.3/kmail/actionscheduler.cpp:628 #9 0x009f4f54 in KMail::ActionScheduler::qt_metacall (this=value optimized out, _c=value optimized out, _id=17, _a=value optimized out) at /usr/src/debug/kdepim-4.3.3/i686-redhat-linux-gnu/kmail/actionscheduler.moc:124 #10 0x03b4cc0c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #11 0x03b4d843 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #12 0x03b872f8 in QTimer::timeout() () from /usr/lib/libQtCore.so.4 #13 0x03b5232e in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4 #14 0x03b46d3f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #15 0x0443cb24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #16 0x0281 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0x065fe02b in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #18 0x03b36d73 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #19 0x03b642be in ?? () from /usr/lib/libQtCore.so.4 #20 0x03b61c21 in ?? () from /usr/lib/libQtCore.so.4 #21 0x0130f118 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #22 0x01312a48 in ?? () from /lib/libglib-2.0.so.0 #23 0x01312b74 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #24 0x03b61b6d in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #25 0x044dc356 in ?? () from /usr/lib/libQtGui.so.4 #26 0x03b352aa in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #27 0x03b3570a in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #28 0x03b37bf7 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #29 0x0443c9a8 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #30 0x0804a59e in main (argc=value optimized out, argv=value optimized out) at /usr/src/debug/kdepim-4.3.3/kmail/main.cpp:146 -- 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 217298] SMTP password not saved by configuration dialog
https://bugs.kde.org/show_bug.cgi?id=217298 Tom Albers t...@kde.org changed: What|Removed |Added AssignedTo|t...@kde.org|kdepim-bugs@kde.org -- 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. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 146627] Mail submission agent on port 587 ignored by Mailtransport
https://bugs.kde.org/show_bug.cgi?id=146627 Tom Albers t...@kde.org changed: What|Removed |Added AssignedTo|t...@kde.org|kdepim-bugs@kde.org -- 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. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162175] Does not recognise/use the port number set in the smtp account settings dialog
https://bugs.kde.org/show_bug.cgi?id=162175 Tom Albers t...@kde.org changed: What|Removed |Added AssignedTo|t...@kde.org|kdepim-bugs@kde.org -- 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. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 162192] Server lists are not sorted properly on load
https://bugs.kde.org/show_bug.cgi?id=162192 Tom Albers t...@kde.org changed: What|Removed |Added AssignedTo|t...@kde.org|kdepim-bugs@kde.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 178862] Enable HTML with signature types file and command
https://bugs.kde.org/show_bug.cgi?id=178862 Tom Albers t...@kde.org changed: What|Removed |Added AssignedTo|t...@kde.org|kdepim-bugs@kde.org -- 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. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217388] Scolling with mousewheel in KMail opened Linux ToDay Newsletter distorts music played with Amarok
https://bugs.kde.org/show_bug.cgi?id=217388 --- Comment #4 from Frans Leerink f leerink xs4all nl 2009-12-08 11:27:36 --- Hello Bjoern, Open the attached file id 38835 with kmail as proposed. Open the text document in html by clicking on body part html and then again on 2 popup windows. If you than scroll through the articles while the computer plays in Amarok a quiet song you should hear the twitter. You hear it also if you scroll through the text version of the document. It is not restricted to the Linux TODAY Newsletter, it happens allways by reading mail via Kontact/kmail, as long I use the scrollwheel. Clicking with the mouse on the scollbar does not cause the stutter effect. Amarok does not stutter in other situations, like scrolling with the mouse wheel through a large pdf document with ADOBE Reader. Hopefully this helps Regards, Frans -- 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 217721] KTimetracker crash when embded in kontact
https://bugs.kde.org/show_bug.cgi?id=217721 --- Comment #1 from Nicolas Lécureuil nlecureuil mandriva com 2009-12-08 12:38:51 --- I created a review request : http://reviewboard.kde.org/r/2339/ -- 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 215519] kmail improperly makes path name italic
https://bugs.kde.org/show_bug.cgi?id=215519
Thomas McGuire mcgu...@kde.org changed:
What|Removed |Added
CC||julien...@no-log.org
--- Comment #5 from Thomas McGuire mcguire kde org 2009-12-08 12:50:03 ---
This test breaks 3 unit tests, for example the case *BLA BLA BLA BLA*..
Please have a look at those and modify the patch so that they still pass.
The new unit test for this case would be:
QTest::newRow( ) the /etc/{rsyslog.d,syslog-ng.d}/package.rpmnew file
0x09 the /etc/{rsyslog.d,syslog-ng.d}/package.rpmnew file;
--
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 215519] kmail improperly makes path name italic
https://bugs.kde.org/show_bug.cgi?id=215519 Thomas McGuire mcgu...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Component|general |kpimutils Version|unspecified |4.4 Product|kmail |kdepimlibs Ever Confirmed|0 |1 -- 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 215519] kmail improperly makes path name italic
https://bugs.kde.org/show_bug.cgi?id=215519 Julien Richard-Foy julien...@no-log.org changed: What|Removed |Added CC|julien...@no-log.org| --- Comment #6 from Julien Richard-Foy julien rf no-log org 2009-12-08 13:19:58 --- I know it breaks these tests, I said it before: the old behaviour is restored, so highlighting marks can *not* be followed by punctuation marks. -- 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 47600] inconsistency with ssl certificates for mail download not handled correctly
https://bugs.kde.org/show_bug.cgi?id=47600 --- Comment #12 from Dominik Haumann dhdev gmx de 2009-12-08 13:28:28 --- Still present in KDE 4.3.4: Accept forever, restart KDE and you are prompted again. Is there any change getting this fixed at all? :) -- 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 215519] kmail improperly makes path name italic
https://bugs.kde.org/show_bug.cgi?id=215519 --- Comment #7 from Thomas McGuire mcguire kde org 2009-12-08 13:55:36 --- Oh sorry, I didn't read closely enough, then. Could you also update the test, then, either by uncommenting the failing tests or by marking them with QEXCEPT_FAIL? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217867] New: Attribute template not saved in address ressource of type LDAP server
https://bugs.kde.org/show_bug.cgi?id=217867 Summary: Attribute template not saved in address ressource of type LDAP server Product: kaddressbook Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rei...@imageware.de CC: to...@kde.org Version:(using KDE 4.3.4) OS:Linux Installed from:openSUSE RPMs In a configured (and working) address ressource of type LDAP it is not possible to change the attribute template (Configuration = Edit Attributes = Template). Instead of being saved the selection is always back the the first entry (Kolab) whenever you open the configuration dialogue. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 205791] kmail cannot display html messages with images refered with Content ID
https://bugs.kde.org/show_bug.cgi?id=205791 --- Comment #5 from Mathieu Jobin somekool somekool net 2009-12-08 15:35:26 --- the src attribute in the img tag is different but it is a similar problem to #205626 -- 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 117752] Not all embedded images in html mails are displayed correctly
https://bugs.kde.org/show_bug.cgi?id=117752 Mathieu Jobin somek...@somekool.net changed: What|Removed |Added CC||somek...@somekool.net --- Comment #1 from Mathieu Jobin somekool somekool net 2009-12-08 15:36:35 --- still relevant in 4.3.4 please fix -- 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 217874] New: Kontact crashed without warning or apparent reason
https://bugs.kde.org/show_bug.cgi?id=217874 Summary: Kontact crashed without warning or apparent reason Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@eisgr.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 KIO::Slave::deref (this=0x54b2e70) at ../../kio/kio/slave.cpp:242 #6 0x7fedb322f159 in KIO::Slave::gotInput (this=0x54b2e70) at ../../kio/kio/slave.cpp:335 #7 0x7fedb323126c in KIO::Slave::qt_metacall (this=0x54b2e70, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff889b8f10) at ./slave.moc:76 #8 0x7fedb4d1fddc in QMetaObject::activate (sender=0x54b4580, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0xbe4a0) at kernel/qobject.cpp:3113 #9 0x7fedb314bf57 in KIO::ConnectionPrivate::dequeue (this=0x54b3470) at ../../kio/kio/connection.cpp:82 #10 0x7fedb314c07d in KIO::Connection::qt_metacall (this=0x54b4580, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x3960500) at ./connection.moc:73 #11 0x7fedb4d1a0f9 in QObject::event (this=0x54b4580, e=0x6cdf8a0) at kernel/qobject.cpp: #12 0x7fedb562aefc in QApplicationPrivate::notify_helper (this=0x1d3f050, receiver=0x54b4580, e=0x6cdf8a0) at kernel/qapplication.cpp:4056 #13 0x7fedb56321ce in QApplication::notify (this=0x7fff889bb530, receiver=0x54b4580, e=0x6cdf8a0) at kernel/qapplication.cpp:4021 #14 0x7fedb6261ab6 in KApplication::notify (this=0x7fff889bb530, receiver=0x54b4580, event=0x6cdf8a0) at ../../kdeui/kernel/kapplication.cpp:302 #15 0x7fedb4d0ac2c in QCoreApplication::notifyInternal (this=0x7fff889bb530, receiver=0x54b4580, event=0x6cdf8a0) at kernel/qcoreapplication.cpp:610 #16 0x7fedb4d0b80a in QCoreApplication::sendEvent (receiver=0x0, event_type=value optimized out, data=0x1d10080) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value optimized out, data=0x1d10080) at kernel/qcoreapplication.cpp:1247 #18 0x7fedb4d33533 in QCoreApplication::sendPostedEvents (s=value optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #19 postEventSourceDispatch (s=value optimized out) at kernel/qeventdispatcher_glib.cpp:210 #20 0x7fedae584bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #21 0x7fedae588588 in ?? () from /lib/libglib-2.0.so.0 #22 0x7fedae5886b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #23 0x7fedb4d331a6 in QEventDispatcherGlib::processEvents (this=0x1d0fcb0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327 #24 0x7fedb56bf4be in QGuiEventDispatcherGlib::processEvents (this=0x54b2e70, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #25 0x7fedb4d09532 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #26 0x7fedb4d09904 in QEventLoop::exec (this=0x7fff889b9810, flags=) at kernel/qeventloop.cpp:201 #27 0x7fedb5aa59de in QDialog::exec (this=0x6d12030) at dialogs/qdialog.cpp:498 #28 0x7fedb61e8185 in KMessageBox::createKMessageBox (dialog=value optimized out, icon=value optimized out, text=value optimized out, strlist=value optimized out, ask=value optimized out, checkboxReturn=value optimized out, options=) at ../../kdeui/dialogs/kmessagebox.cpp:331 #29 0x7fedb61e9400 in KMessageBox::createKMessageBox (dialog=value optimized out, icon=QMessageBox::Information, text=value optimized out, strlist=value optimized out, ask=..., checkboxReturn=0x7fff889b9eaf, options=..., details=...) at ../../kdeui/dialogs/kmessagebox.cpp:151 #30 0x7fedb61eab91 in KMessageBox::informationListWId (parent_id=0, text=value optimized out, strlist=..., caption=..., dontShowAgainName=..., options=) at ../../kdeui/dialogs/kmessagebox.cpp:1008 #31 0x7fedb61eacff in KMessageBox::informationList (parent=value optimized out, text=..., strlist=..., caption=..., dontShowAgainName=..., options=value optimized out) at ../../kdeui/dialogs/kmessagebox.cpp:977 #32 0x7fedb61ead50 in KMessageBox::information (parent=0x54b2e70, text=..., caption=value optimized out, dontShowAgainName=value optimized out, options=value optimized out) at ../../kdeui/dialogs/kmessagebox.cpp:964 #33 0x7fed9f482c9d in ?? () from /usr/lib/libkmailprivate.so.4 #34 0x7fed9f47d909 in ?? () from /usr/lib/libkmailprivate.so.4 #35 0x7fed9f481f74 in ?? () from
[Bug 93203] kmail always start when loggin, regardless of session
https://bugs.kde.org/show_bug.cgi?id=93203 Alvin i...@alvin.be changed: What|Removed |Added CC||i...@alvin.be -- 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 217635] Kontact crashes when clicking Summary tab [QEventLoop::exec, KJob::exec, SDSummaryWidget::updateView]
https://bugs.kde.org/show_bug.cgi?id=217635 Thomas McGuire mcgu...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #1 from Thomas McGuire mcguire kde org 2009-12-08 16:19:12 --- Fixed in r1059987, will be in KDE 4.4 beta2. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217867] Attribute template not saved in address ressource of type LDAP server
https://bugs.kde.org/show_bug.cgi?id=217867 Tobias Koenig to...@kde.org changed: What|Removed |Added CC||mich...@jabster.pl Component|general |general Product|kaddressbook|k3b -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217867] Attribute template not saved in address ressource of type LDAP server
https://bugs.kde.org/show_bug.cgi?id=217867 Tobias Koenig to...@kde.org changed: What|Removed |Added Component|general |general Product|k3b |kab3 -- 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 217879] New: Kontact crash on attempt to sync with Zimbra Calendar
https://bugs.kde.org/show_bug.cgi?id=217879 Summary: Kontact crash on attempt to sync with Zimbra Calendar Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: cfarine...@appropriatesolutions.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.31-ARCH i686 What I was doing when the application crashed: In Kontact, I right clicked the Zimbra calendar, selected reload and it crashed. Sometimes I get an error Unknown Authorization method instead. Not consistently reproducable. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x092fb5d9 in ?? () #7 0xadec5832 in KOrg::IncidenceMonthItem::realStartDate() const () from /usr/lib/libkorganizerprivate.so.4 #8 0xadec2db6 in KOrg::MonthView::reloadIncidences() () from /usr/lib/libkorganizerprivate.so.4 #9 0xadec404c in KOrg::MonthView::setStartDate(QDate const) () from /usr/lib/libkorganizerprivate.so.4 #10 0xadec40be in KOrg::MonthView::showDates(QDate const, QDate const) () from /usr/lib/libkorganizerprivate.so.4 #11 0xadf0f31a in KOViewManager::updateView(QDate const, QDate const) () from /usr/lib/libkorganizerprivate.so.4 #12 0xadefd127 in CalendarView::updateView(QDate const, QDate const, bool) () from /usr/lib/libkorganizerprivate.so.4 #13 0xadefee55 in CalendarView::updateView() () from /usr/lib/libkorganizerprivate.so.4 #14 0xadefc830 in CalendarView::resourcesChanged() () from /usr/lib/libkorganizerprivate.so.4 #15 0xadf0d8a8 in CalendarView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkorganizerprivate.so.4 #16 0xb70678ac in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #17 0xb70684e2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #18 0xb53284d7 in KCal::Calendar::calendarChanged() () from /usr/lib/libkcal.so.4 #19 0xb532853d in KCal::Calendar::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkcal.so.4 #20 0xb538fa8a in KCal::CalendarResources::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkcal.so.4 #21 0xb70678ac in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #22 0xb70684e2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #23 0xb537cdb3 in KCal::ResourceCalendar::resourceChanged(KCal::ResourceCalendar*) () from /usr/lib/libkcal.so.4 #24 0xae005cde in KCal::ResourceRemote::doLoad(bool) () from /usr/lib/libkcal_resourceremote.so.4 #25 0xb538a399 in KCal::ResourceCached::load(KCal::ResourceCached::CacheAction) () from /usr/lib/libkcal.so.4 #26 0xb538a835 in KCal::ResourceCached::load() () from /usr/lib/libkcal.so.4 #27 0xadf8775a in ResourceView::reloadResource() () from /usr/lib/libkorganizerprivate.so.4 #28 0xadf8d643 in ResourceView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkorganizerprivate.so.4 #29 0xb70678ac in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #30 0xb7067cf8 in QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () from /usr/lib/libQtCore.so.4 #31 0xb66a2e01 in QAction::triggered(bool) () from /usr/lib/libQtGui.so.4 #32 0xb66a4382 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQtGui.so.4 #33 0xb6ae7cbc in ?? () from /usr/lib/libQtGui.so.4 #34 0xb6aee28b in ?? () from /usr/lib/libQtGui.so.4 #35 0xb6aeee47 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4 #36 0xb66fdc52 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #37 0xb6af1094 in QMenu::event(QEvent*) () from /usr/lib/libQtGui.so.4 #38 0xb66a93a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #39 0xb66b13d0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #40 0xb755e0aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #41 0xb7051e8b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #42 0xb66b0393 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointerQWidget) () from /usr/lib/libQtGui.so.4 #43 0xb671e33a in ?? () from /usr/lib/libQtGui.so.4 #44 0xb671d365 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #45 0xb6747a52 in ?? () from /usr/lib/libQtGui.so.4 #46 0xb4aed328 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #47 0xb4af0ba0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #48 0xb4af0cd3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #49 0xb707c5f5 in
[Bug 217880] New: Selecting New Contact doesn't do anything.
https://bugs.kde.org/show_bug.cgi?id=217880 Summary: Selecting New Contact doesn't do anything. Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: vec...@vectro.org CC: to...@kde.org Version:(using KDE 4.3.2) OS:Linux Installed from:Ubuntu Packages I discovered this bug after upgrading to Ubuntu Karmic Koala. I am not using Kubuntu. If you'd rather I report this bug over at launchpad.net first, just let me know. STEPS TO REPRODUCE: 1. Start Kaddressbook. 2. Click the New Contact button, or browse to File...New...Contact. EXPECTED BEHAVIOR: Dialog box would appear prompting information on new contact. ACTUAL BEHAVIOR: Nothing happens (no crash, no dialog box, no feedback of any kind). Since this isn't a crash, I haven't a backtrace to provide. Let me know if there are any interesting breakpoints you'd like to look at, though, and I can open this up in the debugger and let you know what I find. Cheers, --Ian Turner -- 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 217758] Clicked on 'This is not a SPAM' button, Kmail crashed
https://bugs.kde.org/show_bug.cgi?id=217758 Nicolas Lécureuil nlecure...@mandriva.com changed: What|Removed |Added CC||nlecure...@mandriva.com --- Comment #1 from Nicolas Lécureuil nlecureuil mandriva com 2009-12-08 16:53:44 --- please install the debug packages from your distribution and paste a new crashlog -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Rado rado.kljucev...@ksec.si changed: What|Removed |Added CC||rado.kljucev...@ksec.si --- Comment #98 from Rado rado kljucevsek ksec si 2009-12-08 17:00:36 --- Everyone who seeks success in his doing must hear the wishes of his/her customers or users of his/her achievements and results. Being a volunteer does not free you from the need to fulfil those wishes. Yes, we need the behaviour of this software so that it contains all the basic or usual business needs. We cannot use this software anymore without a bad feeling of being understood as IT illiterate. But on the contrary we would all like to believe that we are on the edge of development! Please listen to us as we are the only ones who truly love this software. Knock, knock to your minds, maintainers and developers! If you lose us you lose everything. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 jack samt...@hotmail.com changed: What|Removed |Added CC||samt...@hotmail.com --- Comment #99 from jack samtuke hotmail com 2009-12-08 17:13:50 --- There are lots of demands, needs, and consumers posting recently and not many contributors and community members. We can all sit and squawk like hungry chicks or we can contribute to the solution. Demanding and complaining isn't very constructive. Why not set up a bounty, learn to fix it yourself, get together a petition, find out what's really stopping progress etc.. You'll get what you want faster that way I reckon. -- 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 217721] KTimetracker crash when embded in kontact
https://bugs.kde.org/show_bug.cgi?id=217721 Nicolas Lécureuil nlecure...@mandriva.com changed: What|Removed |Added Severity|normal |crash -- 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 217721] KTimetracker crash when embded in kontact
https://bugs.kde.org/show_bug.cgi?id=217721 Nicolas Lécureuil nlecure...@mandriva.com changed: What|Removed |Added CC||moor...@gmail.com --- Comment #2 from Nicolas Lécureuil nlecureuil mandriva com 2009-12-08 17:36:50 --- *** Bug 212563 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217887] New: kmail crash backtrace during automatic mail fetching
https://bugs.kde.org/show_bug.cgi?id=217887 Summary: kmail crash backtrace during automatic mail fetching Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: f...@wemgehoertderstaat.de Application that crashed: kmail Version of the application: 1.12.3 KDE Version: 4.3.3 (KDE 4.3.3) Qt Version: 4.5.3 Operating System: Linux 2.6.27.38-170.2.113.fc10.x86_64 x86_64 -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #5 0x003cbf4feaa3 in KMail::MessageListView::StorageModel::initializeMessageItem (this=0x1a907d0, mi=0x380f690, row=value optimized out, bUseReceiver=false) at /usr/src/debug/kdepim-4.3.3/kmail/messagelistview/storagemodel.cpp:402 #6 0x003cbf525960 in KMail::MessageListView::Core::Model::viewItemJobStepInternalForJobPass1Fill (this=0x1874080, job=0x262ca10, tsta...@0x7fff2d235a60) at /usr/src/debug/kdepim-4.3.3/kmail/messagelistview/core/model.cpp:2704 #7 0x003cbf52729d in KMail::MessageListView::Core::Model::viewItemJobStepInternalForJob (this=0x1874080, job=0x381, tsta...@0x7fff2d235a60) at /usr/src/debug/kdepim-4.3.3/kmail/messagelistview/core/model.cpp:3346 #8 0x003cbf527adb in KMail::MessageListView::Core::Model::viewItemJobStepInternal (this=0x1874080) at /usr/src/debug/kdepim-4.3.3/kmail/messagelistview/core/model.cpp:3718 #9 0x003cbf528650 in KMail::MessageListView::Core::Model::viewItemJobStep (this=0x1874080) at /usr/src/debug/kdepim-4.3.3/kmail/messagelistview/core/model.cpp:3906 #10 0x003cbf5298f7 in KMail::MessageListView::Core::Model::setStorageModel (this=0x1874080, storageModel=value optimized out, preSelectionMode=KMail::MessageListView::Core::PreSelectLastSelected) at /usr/src/debug/kdepim-4.3.3/kmail/messagelistview/core/model.cpp:798 #11 0x003cbf52a3a9 in KMail::MessageListView::Core::Model::slotStorageModelLayoutChanged (this=value optimized out) at /usr/src/debug/kdepim-4.3.3/kmail/messagelistview/core/model.cpp:4389 #12 0x003cbf0edae0 in KMail::MessageListView::Core::Model::qt_metacall (this=0x1874080, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff2d236120) at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/moc_model.cpp:80 #13 0x003c25358662 in QMetaObject::activate (sender=0x1a907d0, from_signal_index=value optimized out, to_signal_index=17, argv=0x2ef7b70) at kernel/qobject.cpp:3112 #14 0x003c25339174 in QAbstractItemModel::reset (this=0x1a907d0) at kernel/qabstractitemmodel.cpp:2263 #15 0x003cbf0ed4a8 in KMail::MessageListView::StorageModel::qt_metacall (this=0x1a907d0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff2d236270) at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/moc_storagemodel.cpp:92 #16 0x003c25358662 in QMetaObject::activate (sender=0x11d6c80, from_signal_index=value optimized out, to_signal_index=22, argv=0x2ef7b70) at kernel/qobject.cpp:3112 #17 0x003cbf1cdf1f in KMFolder::setUserWhoField (this=0x11d6c80, whofie...@0x7fff2d236580, writeConfig=false) at /usr/src/debug/kdepim-4.3.3/kmail/kmfolder.cpp:745 #18 0x003cbf1cecba in KMFolder::readConfig (this=0x11d6c80, configgro...@0x7fff2d2366e0) at /usr/src/debug/kdepim-4.3.3/kmail/kmfolder.cpp:211 #19 0x003cbf1fa884 in FolderStorage::readConfig (this=0x11d7f80) at /usr/src/debug/kdepim-4.3.3/kmail/folderstorage.cpp:963 #20 0x003cbf1f6ac0 in FolderStorage::countUnread (this=0x11d7f80) at /usr/src/debug/kdepim-4.3.3/kmail/folderstorage.cpp:866 #21 0x003cbf3b1665 in KMMainWidget::updateMarkAsReadAction (this=0x1863f80) at /usr/src/debug/kdepim-4.3.3/kmail/kmmainwidget.cpp:4427 #22 0x003cbf3c6e33 in KMMainWidget::updateFolderMenu (this=0x1863f80) at /usr/src/debug/kdepim-4.3.3/kmail/kmmainwidget.cpp:4458 #23 0x003cbf3d3cd3 in KMMainWidget::slotMailChecked (this=0x1863f80, newMail=value optimized out, sendOnCheck=value optimized out, newinfold...@0x1848a30) at /usr/src/debug/kdepim-4.3.3/kmail/kmmainwidget.cpp:1112 #24 0x003cbf3d6197 in KMMainWidget::qt_metacall (this=0x1863f80, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff2d236bd0) at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmmainwidget.moc:386 #25 0x003c25358662 in QMetaObject::activate (sender=0x1848a00, from_signal_index=value optimized out, to_signal_index=4, argv=0x2ef7b70) at kernel/qobject.cpp:3112 #26 0x003cbf20f3d2 in KMail::AccountManager::checkedMail (this=0x11d7f80, _t1=true, _t2=false, _t3=value optimized out) at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/accountmanager.moc:109 #27 0x003cbf21147e in KMail::AccountManager::processNextCheck (this=0x1848a00, _newMail=224) at
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #100 from Manolete variosinftk gmail com 2009-12-08 17:41:37 --- El Martes 08 Diciembre 2009 17:13:54 jack escribió: --- Comment #99 from jack samtuke hotmail com 2009-12-08 17:13:50 --- Why not set up a bounty, learn to fix it yourself, get together a petition, find out what's really stopping progress etc.. You'll get what you want faster that way I reckon. That may be an option -and very reasonable- for programmers, but for users who are economists, history students, musicians; in short: for all those who have a non-computer related job or studies it's inviable; so, unless KDE wants to be a computer geeks DE instead an universal one, I think there's some truth to be taken into account in those comments that say Twitter plasmoids (or similar cute apps) should be secondary. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Rob Hasselbaum r...@hasselbaum.net changed: What|Removed |Added CC||r...@hasselbaum.net --- Comment #101 from Rob Hasselbaum rob hasselbaum net 2009-12-08 17:58:50 --- (In reply to comment #100) That may be an option -and very reasonable- for programmers, but for users who are economists, history students, musicians; in short: for all those who have a non-computer related job or studies it's inviable; so, unless KDE wants to be a computer geeks DE instead an universal one, I think there's some truth to be taken into account in those comments that say Twitter plasmoids (or similar cute apps) should be secondary. Anyone can offer a bounty (i.e. money). You don't have to be a programmer to do that. It's a typical misconception among some users of open source software that developers somehow owe you something. They do not. But it is well within your power to offer incentives to developers in the form of money or something else of value. Or, if you're a programmer, contribute a patch. Either alternative is better than demanding action. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Simon Toth happy.cerbe...@gmail.com changed: What|Removed |Added CC||happy.cerbe...@gmail.com --- Comment #102 from Simon Toth Happy Cerberus gmail com 2009-12-08 18:13:47 --- Anyone can offer a bounty (i.e. money). You don't have to be a programmer to do that. Not true. Unless there will be a developer who will actually say something like: OK, I will do it for 200USD a bounty will never work. There are several types of OpenSource developers and with the exception freelancers none of them will or can accept money for fixing a bug/implementing a feature. It's a typical misconception among some users of open source software that developers somehow owe you something. Of course they don't but once you have a product (OpenSource or not) there are certain quality levels that are expected. The problem with OpenSource is that OpenSource developers will rather spend 48 hour writing excuses why they can't implement feature ABC then implement it in 2 hours. They do not. But it is well within your power to offer incentives to developers in the form of money or something else of value. Or, if you're a programmer, contribute a patch. ROFL, good joke :-D Probably never tried that did you? Btw. I'm an OpenSource developer, success rate of patches is pretty much zero once they actually do change something. I don't care because I have no problem with maintaining a fork. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Simon Bühler si...@aktionspotential.de changed: What|Removed |Added CC||si...@aktionspotential.de --- Comment #103 from Simon Bühler simon aktionspotential de 2009-12-08 18:17:28 --- i feel i have to start this: 20€ from me for the one - or shared among those - who realizes a working patch against trunk until the first of june 2010. everybody - join in and show whats it worth for you -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #104 from Manolete variosinftk gmail com 2009-12-08 18:39:17 --- El Martes 08 Diciembre 2009 17:58:54 Rob Hasselbaum escribió: Anyone can offer a bounty (i.e. money). You don't have to be a programmer to do that. It's a typical misconception among some users of open source software that developers somehow owe you something. Donations received by many projects aren't grown from soil. And no, I understand these scarce donations can not be considered like hiring devs who receive them, so of course devs don't owe anything to users. But again, if they are trying to make a widely used desktop environment they should pay some attention to certain reasonable claims from real world users and not just statements form computer science students or even experienced programmers who affirm html mails are evil just because in their strait world text mails are enough. I think eyecandy and some not too important plasmoids can wait, and manpower be concentrated on important things like Nepomuk, Akonadi or making Kmail a serious emaill client which can be used in enterprise environments (and I'm sure companies would make better donations than private users... if apps were just useful); but I am not thinking developers owe it to me because I once donated some euros; it's just a feature most users who use mail for work think any modern mail composer should have. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Pavel Denisov paul_deni...@inbox.ru changed: What|Removed |Added CC||paul_deni...@inbox.ru --- Comment #105 from Pavel Denisov paul_denisov inbox ru 2009-12-08 18:42:55 --- 20€ from me too -- 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 217898] New: Crash using the kontact (Personal information manager)
https://bugs.kde.org/show_bug.cgi?id=217898 Summary: Crash using the kontact (Personal information manager) Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rudolf.h...@gmx.de Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.1 (KDE 4.3.1) release 6 Qt Version: 4.5.3 Operating System: Linux 2.6.31.5-0.1-default i686 Distribution: openSUSE 11.2 (i586) -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xaf93a4b5 in QWidget::setUpdatesEnabled(bool) () from /usr/lib/libkorganizerprivate.so.4 #7 0xb6514946 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #8 0xaf936c89 in QWidget::setUpdatesEnabled(bool) () from /usr/lib/libkorganizerprivate.so.4 #9 0xb64bd8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #10 0xb64c529e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #11 0xb73b2ce1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #12 0xb6e7732e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #13 0xb651cb79 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #14 0xb651d3ac in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #15 0xb651c79a in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #16 0xb651d3ac in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #17 0xb651c79a in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #18 0xb66b12f4 in ?? () from /usr/lib/libQtGui.so.4 #19 0xb650d80e in QWidgetPrivate::syncBackingStore() () from /usr/lib/libQtGui.so.4 #20 0xb6514720 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #21 0xb68cfaa4 in QMainWindow::event(QEvent*) () from /usr/lib/libQtGui.so.4 #22 0xb749e9e4 in KMainWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5 #23 0xb74e6522 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5 #24 0xb64bd8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #25 0xb64c529e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #26 0xb73b2ce1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #27 0xb6e7732e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #28 0xb66ae579 in ?? () from /usr/lib/libQtGui.so.4 #29 0xb66b1bb4 in ?? () from /usr/lib/libQtGui.so.4 #30 0xb650f9e8 in QWidget::repaint(QRect const) () from /usr/lib/libQtGui.so.4 #31 0xb650fb11 in QWidget::repaint() () from /usr/lib/libQtGui.so.4 #32 0xb6922841 in QStatusBar::reformat() () from /usr/lib/libQtGui.so.4 #33 0xb6923e8b in QStatusBar::removeWidget(QWidget*) () from /usr/lib/libQtGui.so.4 #34 0xb74c391e in KStatusBar::removeItem(int) () from /usr/lib/libkdeui.so.5 #35 0xafaaef32 in ?? () from /usr/lib/kde4/kaddressbookpart.so #36 0xb611ef94 in KParts::Part::customEvent(QEvent*) () from /usr/lib/libkparts.so.4 #37 0xb6e8780b in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #38 0xb64bd8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #39 0xb64c534e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #40 0xb73b2ce1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #41 0xb6e7732e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #42 0xb612b230 in KParts::MainWindow::createGUI(KParts::Part*) () from /usr/lib/libkparts.so.4 #43 0xb771af6a in Kontact::MainWindow::selectPlugin(Kontact::Plugin*) () from /usr/lib/libkontactprivate.so.4 #44 0xb771fc21 in Kontact::MainWindow::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkontactprivate.so.4 #45 0xb6e8d864 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #46 0xb6e8e585 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #47 0xb7720f75 in ?? () from /usr/lib/libkontactprivate.so.4 #48 0xb7720fe7 in ?? () from /usr/lib/libkontactprivate.so.4 #49 0xb77212de in ?? () from /usr/lib/libkontactprivate.so.4 #50 0xb6e8d864 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #51
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Tyler Wagner ty...@tolaris.com changed: What|Removed |Added CC||ty...@tolaris.com --- Comment #106 from Tyler Wagner tyler tolaris com 2009-12-08 18:52:00 --- £50 from me, and £50 from my employer as matching funds, if Simon Bühler's bounty is achieved. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #107 from Manolete variosinftk gmail com 2009-12-08 18:58:31 --- El Martes 08 Diciembre 2009 18:17:33 Simon Bühler escribió: --- Comment #103 from Simon Bühler simon aktionspotential de 2009-12-08 18:17:28 --- i feel i have to start this: 20€ from me for the one - or shared among those - who realizes a working patch against trunk until the first of june 2010. everybody - join in and show whats it worth for you Haha, nice, Simon; but I don't think it works that way. You donate your money to a project and devs do whatever they want; you can't request determinate implementations, at least wasn't able when I donated. As Rob Hasselbaum has said, incentives are not contracts nor developers owe anything to users even if donated some money, and I think it's in general a correct attitude, if not software libre development would be a messy auction where best paid ideas would be the only to be developed, to the detriment of other important projects which aren't seen so atractive by the majority. Anyway, I don't want to look stingy, hehe. 20 € more from me for Kmail being able to efficaciousy reply in HTML and efficaciously compose HTML mails (I'm not sure this is a good practice, though). -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 mi+...@aldan.algebra.com changed: What|Removed |Added CC||mi+...@aldan.algebra.com --- Comment #108 from mi+kde aldan algebra com 2009-12-08 19:13:57 --- Not to insult anyone, but this bounty-talk is silly. Money sure can speed-up an open-source project, but in this case the speed of development is not the problem. The problem is absence of ANY development. It has been 5 years since the feature was requested -- tons of features were added to KDE within that time, most of them for free. Because developers wanted to do them and the architects approved of them. This feature's trouble is with the subtle ideological resistance. Stefan Gehn's comment #14 is the rare explicit statement on the matter, but it is quite apparent, that other decision-makers feel similarly and may even consider one of their own, who finally implements it, to be a sell-out. Our measly 20-200-1000 dollars/euros aren't going to change their minds very much -- the bug already has thousands of votes, so there is no question, they know, the users want it. Even if we collect enough pledges to hire a developer just for that, chances are, his work will not be accepted by the KDE-project under some pretext or another, and the separate patches would have to be maintained separately. The pretexts wouldn't be dishonest: every new feature violates existing balance in some way, so it has to add valuable functionality to justify it. Clearly, this feature is not perceived as beneficial -- nay, it is viewed as DETRIMENTAL -- and thus it will be sincerely rejected. I'd love for this opinion of mine to turn into a self-defeating prophecy, but -- after all these years -- I'm not particularly hopeful... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 193514] Crash when activating plugin
https://bugs.kde.org/show_bug.cgi?id=193514 --- Comment #54 from Jakub 'Livio' Rusinek jakub rusinek gmail com 2009-12-08 19:19:26 --- 2.) It happens exactly every second (!) time kontact is started. That means: after closing kontact the first attempt to start crashes, the second one succeeds. I tried. First crashed but next three times it started. 2.) The crash seems to occur only, if akregator has been started inside kontact. Well, I haven't tried without Akregator. 3.) It appears to me that starting something like kmail --composer directly instead of kontact is not possible, only starting the kontact shell seems to fix the problem to allow success with the second try. I can start 'kmail --composer'. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #109 from jack samtuke hotmail com 2009-12-08 19:44:20 --- http://pledgie.com/campaigns/7325 I think that bounties are a good idea for this bug. Clearly doing nothing is not going to help the situation, and pledging money is a good way of showing that users care about the problem and are prepared to support patch. I started a pledgie campaign to allow people to formally pledge funds. Being unable to find anyone else to provide a paypal account to act as the recipient I have used my own, from which I will obviously pass funds on to whoever is decided to have succeeded in implementing a patch if indeed anyone does. See the link at the top for more info. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #110 from Thomas McGuire mcguire kde org 2009-12-08 19:47:11 --- I said I didn't want to reply to this again, but oh well, I have to clarify something. I'd like to address comment 108, in which the author says things like subtle ideological resistance, decision-makers [..] may even consider one of their own, who finally implements it, to be a \sell-out\ and it is viewed as DETRIMENTAL. This is simply not true. As I've said before in comment 64: I'd like better HTML support in KMail. In fact, I have worked on some minor stuff like inline images for HTML myself. I don't know any developer who is opposed to better HTML support. I know I'm repeating myself: We consider better HTML support good. The only reason it is not implemented is that I had no time to do that myself, so far, and no one else came up with a complete patch yet. Right now, I'm most busy with the Akonadi port of KMail, which does indeed have greater priority, there is a _lot_ to do to make KMail work properly with Akonadi. That said, the plan in the back of my head was always to refactor the template parser and then add HTML support to it. Maybe I can come to this during the Akonadi port at some point. Money certainly helps shifting the priorities :) But don't get your hopes up, it mainly depends on available time. Also, the composer wouldn't use the WebKit editor, that is too much work. Instead if would use QTextEdit, which means same HTML format preserving as Mailody has, nothing fancy. Porting the whole composer to a WebKit editor would really be much work. At this point, KMail is feature-frozen, so any new feature has to be developed in the Akonadi ports branch. KMail 2 (based on Akonadi) is expected/hoped to be released with KDE 4.5. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #111 from Rob rob globaljunkdrawer com 2009-12-08 19:53:17 --- (In reply to comment #110) I said I didn't want to reply to this again, but oh well, I have to clarify something. --- Thanks, Thomas. I fully understand the time constraints and do appreciate the time spent on the issue by fellow developers. I am eagerly awaiting a solution - an embedded solution is KDE would be well received - no mater what branch it comes from. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #112 from mi+kde aldan algebra com 2009-12-08 20:07:01 --- (In reply to comment #110) This is simply not true. As I've said before in comment 64: I'd like better HTML support in KMail. I'm very glad to be wrong on this. Also, the composer wouldn't use the WebKit editor, that is too much work. Instead if would use QTextEdit, which means same HTML format preserving as Mailody has, nothing fancy. The nothing fancy promise is disappointing. It is the 21st century, the minimal goal should be to allow e-mailing anything, that can be written, drawn, or painted on a piece of paper and stuffed into an envelope. An external attachment should not be required for anything, where a physical equivalent does not require a parcel-box, so to speak. No need for everything at once -- I'll be happy with gradual progress. But I'm wary of forswearing fancy... Thanks for listening. -- 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 217880] Selecting New Contact doesn't do anything.
https://bugs.kde.org/show_bug.cgi?id=217880 Tobias Koenig to...@kde.org changed: What|Removed |Added Component|general |general Product|kaddressbook|kab3 -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #113 from Tomas nicco ts gmail com 2009-12-08 20:47:15 --- Hey Thomas We all appreciate all your work for Kmail. I have just one problem with your priorities. Who has required porting Kmail to Akonadi? How much votes do you have for this and why is this higher priority than HTML support? It looks like you are building skyscraper on 5th avenue but people in Bronx still don't have roof on their houses. (In reply to comment #110) I said I didn't want to reply to this again, but oh well, I have to clarify something. I'd like to address comment 108, in which the author says things like subtle ideological resistance, decision-makers [..] may even consider one of their own, who finally implements it, to be a \sell-out\ and it is viewed as DETRIMENTAL. This is simply not true. As I've said before in comment 64: I'd like better HTML support in KMail. In fact, I have worked on some minor stuff like inline images for HTML myself. I don't know any developer who is opposed to better HTML support. I know I'm repeating myself: We consider better HTML support good. The only reason it is not implemented is that I had no time to do that myself, so far, and no one else came up with a complete patch yet. Right now, I'm most busy with the Akonadi port of KMail, which does indeed have greater priority, there is a _lot_ to do to make KMail work properly with Akonadi. That said, the plan in the back of my head was always to refactor the template parser and then add HTML support to it. Maybe I can come to this during the Akonadi port at some point. Money certainly helps shifting the priorities :) But don't get your hopes up, it mainly depends on available time. Also, the composer wouldn't use the WebKit editor, that is too much work. Instead if would use QTextEdit, which means same HTML format preserving as Mailody has, nothing fancy. Porting the whole composer to a WebKit editor would really be much work. At this point, KMail is feature-frozen, so any new feature has to be developed in the Akonadi ports branch. KMail 2 (based on Akonadi) is expected/hoped to be released with KDE 4.5. -- 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 217721] KTimetracker crash when embded in kontact
https://bugs.kde.org/show_bug.cgi?id=217721 Nicolas Lécureuil nlecure...@mandriva.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #3 from Nicolas Lécureuil nlecureuil mandriva com 2009-12-08 20:48:07 --- SVN commit 1060398 by nlecureuil: Fix crash when KTimetracker is in Kontact BUG:217721 M +5 -2 timetrackerwidget.cpp WebSVN link: http://websvn.kde.org/?view=revrevision=1060398 -- 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 151457] mail filter rules import feature
https://bugs.kde.org/show_bug.cgi?id=151457 tstaerk d...@staerk.de changed: What|Removed |Added AssignedTo|d...@staerk.de |kdepim-bugs@kde.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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Pascal Vandeputte bugskde...@asmodeus.be changed: What|Removed |Added CC||bugskde...@asmodeus.be --- Comment #114 from Pascal Vandeputte bugskdeorg asmodeus be 2009-12-08 21:36:53 --- There are 2 things I perceive to be vital for KDE Kontact/KMail in the enterprise: - editable HTML mail forwards replies - ability to work as an Exchange client, with full support for mail, contacts, and appointments (IMAP only does mail, requires co-operation from the exchange admin to enable it, and Exchange contacts nor calendar work) (and frustratingly, my KMail IMAP sessions always get stale after a while) Exchange support relies on getting OpenChange ready (See http://www.kdedevelopers.org/node/4107 ) and getting it fully integrated in Akonadi which also isn't done yet. Kontact/KMail will support Exchange thanks to Akonadi, so getting KMail ready for that is certainly a task I wouldn't like to see Thomas or others others being pulled away from. What I think would make everybody happy: - If KMail could get HTML support with QTextEdit with reasonably little work, that would be *fantastic* if you ask me. nothing fancy sounds way better than absolutely nothing at all and then this wish/bug can be done away with. Fancy stuff isn't necessary, as long as what should work, works without tarnishing KMail's reputation by crashing or something like that - Next, the Akonadi skyscraper on 5th avenue without people on your back moaning about bug 86423 - Finally, once KMail/Akonadi is in maintenance mode, who knows if there's now time for a WebKit composer? Personally, I always have too much stuff to do. Some things take a week, some take two months. But usually I have to multitask and as a result some tasks take years to complete. Had I taken a week out for task 1, I'd have enjoyed the fruits of that week while working on all the other stuff after that. Life just isn't sequential. In the end, it's all up to the devs. Thanks for all the effort put into this fine and promising platform. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217867] Attribute template not saved in address ressource of type LDAP server
https://bugs.kde.org/show_bug.cgi?id=217867 Michał Małek mich...@jabster.pl changed: What|Removed |Added CC|mich...@jabster.pl | -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Ian i...@pairowoodies.com changed: What|Removed |Added CC||i...@pairowoodies.com --- Comment #115 from Ian ian pairowoodies com 2009-12-08 22:02:58 --- I am the original reporter of this bug. It was reported back in 2004 - so I certainly can understand the frustration of those who like me, have wished and hoped for this feature to be implemented in Kmail. Regarding folks putting money toward getting the bug fixed: Well... here's the problem with that - prior to this bug being reported, I paid out of my own pocket to a developer to write a patch that would enable Kmail to even simply compose email in HTML. At the time, I was of the understanding that this would also allow replies to HTML email similar to how Evolution is able to. However, it did not - all it did was enable HTML composed email. But now I see there appears to even be a regression in that in that when there is a reason for me to compose email in HTML, it is not received correctly by other email readers. So for me personally, it is quite frustrating to have paid out of my own pocket for HTML ability, find out it is not quite what I expected, and then see it regress. I'm not a developer. I wish I was. But my other business efforts have supported KDE through donations over the years, on top of the feature I specifically paid for, so I believe I do not have to simply read some folks saying Pay for it.. develop it yourself.. blah blah... I have supported KDE for years - both through giving it publicity, recommending it to others, showing others how to use it - AND through my donations! So it is very disconcerting to read some folks replies to this, admonishing them to provide a patch, etc. Do you want us non-programmers to use the KDE desktop and associated apps or not? I for one won't be donating any more to KDE until this bug is corrected, and the self grandiose comments from some in regard to Provide your own patch cease. I can't provide a patch, but I HAVE done other things when I can, including throwing bucks and support to the KDE project. So please to those of you that keep asking for us non-programmers to provide a patch - give it a rest. -- 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 216843] [feature] Accept events without sending response
https://bugs.kde.org/show_bug.cgi?id=216843 Hrishikesh Mehendale (हृषीकेश मेहेंदळे) hashincl...@gmail.com changed: What|Removed |Added CC||hashincl...@gmail.com --- Comment #1 from Hrishikesh Mehendale (हृषीकेश मेहेंदळे) hashinclude gmail com 2009-12-08 22:15:15 --- Frankly, I'm surprised it was removed. I very clearly remember using this (quite often, too) in KDE 3.5.x. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Tzvetan Mikov tmi...@gmail.com changed: What|Removed |Added CC||tmi...@gmail.com --- Comment #116 from Tzvetan Mikov tmikov gmail com 2009-12-08 22:18:28 --- It is clear that by the time KMail gets proper HTML support - meaning *full* composing, replying and so on - it will have become irrelevant. Objectively, KMail is dead, even though it doesn't know it yet. It pains me to say it, because excepting the two major problems (HTML and IMAP), it is the best e-mail client I have used. May I suggest that instead of waging a lost battle, some serious effort is made to integrate Thunderbird better in KDE. KWallet, KGPG support and so on. That would be the constructive thing to 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 217367] KMail hangs when I'm writing e-mail
https://bugs.kde.org/show_bug.cgi?id=217367 --- Comment #3 from Szőts Ákos szotsaki gmail com 2009-12-08 23:26:10 --- No, there's not any special reason; I use it to send mails. I haven't discovered what can cause this, and it's unpredictable when it occurs, so I'm unable to reproduce it (yet). -- 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 217933] New: can't get access to save addressbook entries
https://bugs.kde.org/show_bug.cgi?id=217933 Summary: can't get access to save addressbook entries Product: kaddressbook Version: unspecified Platform: unspecified OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: p8qesm...@sneakemail.com CC: to...@kde.org Version: 3.5.9 (using 3.5.10, Debian Package 4:3.5.10.dfsg.1-0lenny3 (5.0.3)) Compiler: Target: i486-linux-gnu OS:Linux (i686) release 2.6.27-1-mepis-smp Nothing I do will enable addressbook to save to the addressbook file-resource (or any other attempted addressbook.) Working from root login, and root has cosmic access to the target address, yet the app can't get access. Side note: there is no OK button at bottom of editor page as shown in help file; info entered in the edit page is added to designated file buffer, but no way to save it to disk. -- 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 142917] kio_imap4 has memory leak when using DIMAP
https://bugs.kde.org/show_bug.cgi?id=142917 Austin Howard ahow...@gmx.com changed: What|Removed |Added CC||ahow...@gmx.com --- Comment #11 from Austin Howard ahoward gmx com 2009-12-09 00:37:33 --- This bug is still present in my installation of KDE 4.3.2. -- 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 142917] kio_imap4 has memory leak when using DIMAP
https://bugs.kde.org/show_bug.cgi?id=142917 --- Comment #12 from Danny Auble da llnl gov 2009-12-09 00:40:38 --- as it is in 4.3.4 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217939] New: error to open kontact
https://bugs.kde.org/show_bug.cgi?id=217939 Summary: error to open kontact Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: kile...@gmail.com Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: error to open kontact -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is auto; currently c. [KCrash Handler] #5 Kontact::MainWindow::activatePluginModule (this=0x1a11b20) at ../../../kontact/src/mainwindow.cpp:303 #6 0x00404772 in KontactApp::newInstance (this=0x75f8c8b0) at ../../../kontact/src/main.cpp:147 #7 0x7f1b4cdfccb6 in KUniqueApplicationAdaptor::newInstance (this=0x1acd530, asn_id=value optimized out, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459 #8 0x7f1b4cdfd2a6 in KUniqueApplicationAdaptor::qt_metacall (this=0x1acd530, _c=QMetaObject::InvokeMetaMethod, _id=32370736, _a=0x75f8bbe0) at ./kuniqueapplication_p.moc:75 #9 0x7f1b499caad4 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=..., slotIdx=value optimized out) at qdbusintegrator.cpp:891 #10 0x7f1b499cbcc3 in QDBusConnectionPrivate::activateCall (this=value optimized out, object=0x1acd530, flags=337, msg=...) at qdbusintegrator.cpp:803 #11 0x7f1b499cc547 in QDBusConnectionPrivate::activateObject (this=value optimized out, node=..., msg=value optimized out, pathStartPos=value optimized out) at qdbusintegrator.cpp:1347 #12 0x7f1b499cc7c8 in QDBusActivateObjectEvent::placeMetaCall (this=0x2157770) at qdbusintegrator.cpp:1464 #13 0x7f1b4b8aa0f9 in QObject::event (this=0x75f8c8b0, e=0x2157770) at kernel/qobject.cpp: #14 0x7f1b4c1c8b4d in QApplication::event (this=0x75f8c8b0, e=0x2157770) at kernel/qapplication.cpp:2317 #15 0x7f1b4c1beefc in QApplicationPrivate::notify_helper (this=0x1a07f10, receiver=0x75f8c8b0, e=0x2157770) at kernel/qapplication.cpp:4056 #16 0x7f1b4c1c61ce in QApplication::notify (this=0x75f8c8b0, receiver=0x75f8c8b0, e=0x2157770) at kernel/qapplication.cpp:4021 #17 0x7f1b4cdf5e56 in KApplication::notify (this=0x75f8c8b0, receiver=0x75f8c8b0, event=0x2157770) at ../../kdeui/kernel/kapplication.cpp:302 #18 0x7f1b4b89ac2c in QCoreApplication::notifyInternal (this=0x75f8c8b0, receiver=0x75f8c8b0, event=0x2157770) at kernel/qcoreapplication.cpp:610 #19 0x7f1b4b89b80a in QCoreApplication::sendEvent (receiver=0x0, event_type=value optimized out, data=0x19e0080) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value optimized out, data=0x19e0080) at kernel/qcoreapplication.cpp:1247 #21 0x7f1b4b8c3533 in QCoreApplication::sendPostedEvents (s=value optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #22 postEventSourceDispatch (s=value optimized out) at kernel/qeventdispatcher_glib.cpp:210 #23 0x7f1b45114bbe in g_main_dispatch (context=0x1a09620) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:1960 #24 IA__g_main_context_dispatch (context=0x1a09620) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2513 #25 0x7f1b45118588 in g_main_context_iterate (context=0x1a09620, block=value optimized out, dispatch=value optimized out, self=value optimized out) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2591 #26 0x7f1b451186b0 in IA__g_main_context_iteration (context=0x1a09620, may_block=1) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2654 #27 0x7f1b4b8c31a6 in QEventDispatcherGlib::processEvents (this=0x19dfcb0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327 #28 0x7f1b4c2534be in QGuiEventDispatcherGlib::processEvents (this=0x1a11b20, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #29 0x7f1b4b899532 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #30 0x7f1b4b899904 in QEventLoop::exec (this=0x75f8c7f0, flags=) at kernel/qeventloop.cpp:201 #31 0x7f1b4b89bab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #32 0x00403f47 in main (argc=value optimized out, argv=value optimized out) at ../../../kontact/src/main.cpp:218 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 John Murphy murph...@bigpond.net.au changed: What|Removed |Added CC||murph...@bigpond.net.au --- Comment #117 from John Murphy murphyjj bigpond net au 2009-12-09 01:15:57 --- I must point out that in my (fairly extensive) experience with failed projects - they almost always prioritise technical integration over the user needs. So we will wind up having a fantastic integrated solution for very few people. Also, I agree that this resistance to HTML is partly (maybe wholly) driven by a geek purity meme; I think HTML is viewed as something nasty corporations use. After 3 or 4 years I am now investigating Zimbra and other clients. If I adopt that, I probably won't come back - integration or not. It is a great, great pity - and I feel great reluctance to do it. But I must move on. -- 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 217946] New: LDAP directory contact attributes cannot be modified
https://bugs.kde.org/show_bug.cgi?id=217946 Summary: LDAP directory contact attributes cannot be modified Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: rdrat...@yahoo.co.uk CC: to...@kde.org Version:(using KDE 4.3.2) OS:Linux Installed from:Ubuntu Packages I tested kaddressbook (4.3) as front-end to manage contacts in a LDAP directory (addressbook). The server runs openldap 2.4. kaddressbook perfectly adds and deletes contacts. But it fails to modify attribute values of a contact within the LDAP directory. After changing e. g. the facsimile number of a contact, kaddressbook shows the updated number but the new number is not saved in the LDAP directory. OpenLDAP reports following failure: 'value #0 invalid per syntax'. According to other sources in the internet this is a sign for a missing objectClass. When checking further I found out that kaddressbook CAN modify contact information in the LDAP directory if following objectClasses are part of the contact entry: person, organizationalPerson, inetOrgPerson. If I add directly a contact to the LDAP directory (using ldapadd) with all mentioned objectClass values defined, kaddressbook can save the modifications to the directory. But during modification the objectClass values person and organizationalPerson disappear in the directory entry. objectClass inetOrgPerson is the only one left. It seems that kaddressbook can only handle this objectClass. As a work-around I set up an ACL (olcAccess: to attrs=objectClass value=organizationalPerson by dn=cn=admin,dc=gas,dc=de write by dn=cn=AddrAdmin,dc=gas,dc=de add by * read) that prohibits the addressbook admin (i. e. kaddressbook) from deleting the objectClass values person and organizationalPerson of a contact entry in LDAP. But this doesn't help. In fact, instead of modifying single attributes of a contact within the LDAP directory, kaddressbook completely deletes the contact from the LDAP directory and adds it again. But only with those LDAP attributes that kaddressbook can handle. As there are several Internet sources that recommend kaddressbook as a LDAP front-end for managing LDAP based addressbooks, this is a severe bug. kaddressbook should only be allowed to modify attribute values, but not deleting them. LDAP directories are a sensitive central network resource that are usually accessed and managed by several applications. -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #118 from Rado rado kljucevsek ksec si 2009-12-09 02:01:50 --- I cannot agree more with the last comments from John and Tzvetan. We lost this battle and I believe we lost this war. It is not the problem that somebody compares me with a hungry chick who can only squawk but it is the whole attitude which is the base for the only logical conclusion: we are not important and never will be, we are just a burden. Most of the people here share a passionate support for KMail, Kontact etc. Some of us are also donators. But what are we facing here? Thank you Ian for sharing your experience with donations with us. The system of donations is clearly flawed. Who cares for Akonadi at this very moment? The system of priorities is clearly flawed, two. This project has unfortunately no future. I am sorry to admit that. It hurts and it also means a lot of work to migrate and switch to another solution but it seems unavoidable. I think the final curtain is down and behind it one can built whatever he wants we won't take care because it is not meant for us. Anyway, thank you for the past work. -- 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 217946] LDAP directory contact attributes cannot be modified
https://bugs.kde.org/show_bug.cgi?id=217946 --- Comment #1 from rdratlos yahoo co uk 2009-12-09 02:06:14 --- Created an attachment (id=38937) -- (http://bugs.kde.org/attachment.cgi?id=38937) LDAP test contact -- 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 217960] New: Kmail does not open attachments
https://bugs.kde.org/show_bug.cgi?id=217960 Summary: Kmail does not open attachments Product: kmail Version: 1.12.1 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: gil...@seznam.cz Version: 1.12.1 (using 4.3.1 (KDE 4.3.1), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.30-gentoo-r5 How to reproduce: start kmail, click on mail with attachement so it is in preview window, click on attachment (like file.pdf)(left click, or right click+open with...) Result: nothing visible, kmail spawns one zombie Expected result: Open attachement in external application (like xpdf) Side effect/workaround: /home/gilhad/.kde4/tmp-COMPNAME/kmaildSOMETHING/file.pdf exists and can be directly open with xpdf from command line --- More details: I am not running full KDE, but fluxbox. Dbus+HAL are running. ps axf: .. 2194 ?Sl 0:04 kmail 2206 ?Z 0:00 \_ [kmail] defunct 3252 ?Z 0:00 \_ [kmail] defunct 3253 ?Z 0:00 \_ [kmail] defunct 2197 ?Ss 0:00 kdeinit4: kdeinit4 Running... 2198 ?S 0:00 \_ kdeinit4: klauncher [kdeinit] --fd=8 2204 ?S 0:00 \_ kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-gilhad/klauncherMT2198.slave-socket local:/tmp/ks 2200 ?S 0:00 kdeinit4: kded4 [kdeinit] e here we see 3 zombies, from 3 unsuccessful attempts to open file.pdf While i have highlighted the mail, the attachements are stored in subfolders of /tmp and it is possible to open it from there with any program the attachements can be View from right mouse click and the result is what is expected: [KMail: Attachment contains binary data. Trying to show first 75 characters.] %PDF-1.4 %âãÏÓ 2 0 obj /Type/XObject/ColorSpace[/Indexed/DeviceRGB 255(@g Left click opens dialog Open attachment 'file.pdf'? Note that opening an attachment may compromise your system's security. [Save As] [Open with xpdf] [Cancel] (Save As works, Open with xpdf does not) The problem is somewhere along running external applications from KMail, but i do not know, where to look for more details/logs, or what more configuration is needed. No error dialogs, nothing in /var/log/syslog. Please help me and direct me, where to look for more... -- 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 217933] can't get access to save addressbook entries
https://bugs.kde.org/show_bug.cgi?id=217933 Tobias Koenig to...@kde.org changed: What|Removed |Added Component|general |general Product|kaddressbook|kab3 -- 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 217964] New: Kmail crashes when starting up and reading message
https://bugs.kde.org/show_bug.cgi?id=217964 Summary: Kmail crashes when starting up and reading message Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: matthijstij...@gmail.com Application that crashed: kmail Version of the application: 1.12.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.31-ARCH x86_64 What I was doing when the application crashed: When I click a message to read while KMail is starting up, it crashes. I use IMAP. This also happens when KMail selects a new message for me, without me clicking on one. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #5 0x7fa31706efa0 in DwHeaders::FindField(char const*) const () from /usr/lib/libmimelib.so.4 #6 0x7fa31db04f14 in KMMessage::rawHeaderField (this=value optimized out, name=...) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmmessage.cpp:1961 #7 0x7fa31db07325 in KMMessage::from (this=0x2d50460) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmmessage.cpp:1712 #8 0x7fa31dd5769f in KMail::FancyHeaderStyle::format (this=value optimized out, message=value optimized out, strategy=value optimized out, vCardName=value optimized out, printing=value optimized out, topLevel=true) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/headerstyle.cpp:457 #9 0x7fa31dbf7767 in KMReaderWin::writeMsgHeader (this=0x2330b90, aMsg=value optimized out, hasVCard=false, topLevel=value optimized out) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmreaderwin.cpp:1791 #10 0x7fa31dbff478 in KMReaderWin::parseMsg (this=0x2330b90, aMsg=0x2d50460) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmreaderwin.cpp:1678 #11 0x7fa31dbee45a in KMReaderWin::displayMessage (this=0x2330b90) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmreaderwin.cpp:1608 #12 0x7fa31dbee634 in KMReaderWin::updateReaderWin (this=0x2330b90) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmreaderwin.cpp:1548 #13 0x7fa31dbfbc7d in KMReaderWin::update (this=0x10001, observable=0x2d81978) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmreaderwin.cpp:950 #14 0x7fa31de21259 in KMail::ISubject::notify (this=0x2d50530) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/isubject.cpp:33 #15 0x7fa31db0c62c in KMMessage::updateBodyPart (this=0x2d50460, partSpecifier=) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/kmmessage.cpp:3237 #16 0x7fa31ddf54ba in KMail::ImapJob::slotGetMessageResult (this=0x2cbf3b0, job=value optimized out) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/imapjob.cpp:435 #17 0x7fa31ddf993b in KMail::ImapJob::qt_metacall (this=0x2cbf3b0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff7fd44120) at /home/phil/kdemod/core/kdepim/src/kdepim-4.3.4/kmail/imapjob.moc:82 #18 0x7fa31d3eb47c in QMetaObject::activate (sender=0x2d6cb40, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x6d6f72) at kernel/qobject.cpp:3112 #19 0x7fa31e4bcb02 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5 #20 0x7fa31e4bce7f in KJob::emitResult() () from /usr/lib/libkdecore.so.5 #21 0x7fa31681ec43 in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so.5 #22 0x7fa31681f103 in KIO::TransferJob::slotFinished() () from /usr/lib/libkio.so.5 #23 0x7fa31681da11 in KIO::TransferJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #24 0x7fa31d3eb47c in QMetaObject::activate (sender=0x2a989f0, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x6d6f72) at kernel/qobject.cpp:3112 #25 0x7fa3168df871 in KIO::SlaveInterface::dispatch(int, QByteArray const) () from /usr/lib/libkio.so.5 #26 0x7fa3168dc123 in KIO::SlaveInterface::dispatch() () from /usr/lib/libkio.so.5 #27 0x7fa3168cef4d in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #28 0x7fa3168d106c in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #29 0x7fa31d3eb47c in QMetaObject::activate (sender=0x211c150, from_signal_index=value optimized out, to_signal_index=value optimized out, argv=0x6d6f72) at kernel/qobject.cpp:3112 #30 0x7fa3167ebd97 in KIO::ConnectionPrivate::dequeue() () from /usr/lib/libkio.so.5 #31 0x7fa3167ebebd in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #32 0x7fa31d3e5799 in QObject::event (this=0x211c150, e=0x2d866a0) at kernel/qobject.cpp:1110 #33 0x7fa31c88260c in QApplicationPrivate::notify_helper (this=0x1fcb7d0, receiver=0x211c150, e=0x2d866a0) at kernel/qapplication.cpp:4065 #34 0x7fa31c8898de in
