[kontact] [Bug 446419] New: Scam detection triggers on links which read 'http://' but point to 'https://'
https://bugs.kde.org/show_bug.cgi?id=446419 Bug ID: 446419 Summary: Scam detection triggers on links which read 'http://' but point to 'https://' Product: kontact Version: 5.18.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: --- SUMMARY In the HTML view of an e-mail message, benign links will trigger scam detection if the displayed URL starts with "http://; but the target URL starts with "https://; (or vice versa). STEPS TO REPRODUCE 1. Send an e-mail to yourself, in rich text mode, containing a link with the text "http://example.com; which leads to "https://example.com;. 2. Open the e-mail in HTML view. OBSERVED RESULT A "This message may be a scam" warning appears. EXPECTED RESULT Scam detection should not be triggered on URLs with an HTTP/HTTPS protocol mismatch, as long as the domain and path are the same. It's not a meaningful difference, and displaying the warning in this case may condition users to ignore it when there *is* a misleading link. SOFTWARE/OS VERSIONS Linux: Gentoo KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 434492] Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 --- Comment #4 from Keith --- Created attachment 136742 --> https://bugs.kde.org/attachment.cgi?id=136742=edit Google Groupware configuration dialog This is the configuration dialog I was talking about. It's accessible under "Configure -> Configure Natively" in Akonadi Console or by right-clicking in Kontact and choosing "Calendar Properties..." -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 434492] Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 --- Comment #3 from Keith --- (In reply to Allen Winter from comment #2) > not sure what tool you are using for the configuration (akonadiconsole, > KMail, KOrganizer)? you could use KOrganizer to select/deselect individual > calendars from the top-level folder. Inside the configuration dialog of the Google Groupware resource itself. KOrganizer allows you to *hide* calendars, but it looks like it still syncs them. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 434492] Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 --- Comment #1 from Keith --- I'm really sorry, I somehow submitted this while I was typing up the information. SUMMARY Google Groupware resource does not allow you to de-select calendars for syncing when configuring it. STEPS TO REPRODUCE 1. Add a Google Groupware resource. 2. Open the configuration dialog and sign in. 3. Try to uncheck some calendars. OBSERVED RESULT Calendars still synchronize, and if you hit the "Reload" button in the dialog, all unchecked calendars become checked. EXPECTED RESULT Calendars that are unchecked don't appear anywhere and don't sync. ADDITIONAL INFORMATION Perhaps a temporary solution to this bug would just be to allow the user to disable calendar syncing for a specific Google resource entirely? -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 434492] New: Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 Bug ID: 434492 Summary: Cannot deselect calendars in Google resource settings Product: Akonadi Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Google Resource Assignee: dvra...@kde.org Reporter: keithhacks-kde...@yahoo.com CC: kdepim-bugs@kde.org Target Milestone: --- SUMMARY Googl STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.21 User Edition (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are on the CC list for the bug.
[kontact] [Bug 426906] New: Attempting to change Google Calendar colour crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=426906 Bug ID: 426906 Summary: Attempting to change Google Calendar colour crashes Kontact Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: --- Application: kontact (5.15.1 (20.08.1)) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.4.0-45-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: I right-clicked on a folder in my Google Calendar account and clicked Change Folder Colour. As soon as I hit OK on the picker dialog, Kontact crashed. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f1cd3ecb969 in QColor::operator=(QColor const&) (this=0x8, color=...) at painting/qcolor.cpp:2929 #5 0x7f1c26255c9a in EventViews::setResourceColor(Akonadi::Collection const&, QColor const&, QSharedPointer const&) (coll=..., color=..., preferences=...) at ./src/helper.cpp:59 #6 0x7f1c26591a34 in KOHelper::setResourceColor(Akonadi::Collection const&, QColor const&) (collection=..., color=...) at ./src/kohelper.cpp:52 #7 0x7f1c26547c1b in AkonadiCollectionView::assignColor() (this=0x55a0aecf2d40) at ./src/akonadicollectionview.cpp:670 #8 0x7f1cd38e15ae in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc239c2270, r=0x55a0aecf2d40, this=0x55a0afadcb80) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate(QObject*, int, void**) (sender=0x55a0afadc670, signal_index=4, argv=0x7ffc239c2270) at kernel/qobject.cpp:3886 #10 0x7f1cd38da977 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55a0afadc670, m=m@entry=0x7f1cd48f4280 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc239c2270) at kernel/qobject.cpp:3946 #11 0x7f1cd43dd7f6 in QAction::triggered(bool) (this=this@entry=0x55a0afadc670, _t1=) at .moc/moc_qaction.cpp:376 #12 0x7f1cd43dfec8 in QAction::activate(QAction::ActionEvent) (this=0x55a0afadc670, event=) at kernel/qaction.cpp:1161 #13 0x7f1cd456a712 in QMenuPrivate::activateCausedStack(QVector > const&, QAction*, QAction::ActionEvent, bool) (this=this@entry=0x55a0afcd20f0, causedStack=..., action=action@entry=0x55a0afadc670, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1353 #14 0x7f1cd4571dbe in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) (this=this@entry=0x55a0afcd20f0, action=action@entry=0x55a0afadc670, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1430 #15 0x7f1cd4573052 in QMenu::mouseReleaseEvent(QMouseEvent*) (this=0x55a0afcd20b0, e=0x7ffc239c2950) at widgets/qmenu.cpp:2927 #16 0x7f1cd4426db6 in QWidget::event(QEvent*) (this=this@entry=0x55a0afcd20b0, event=event@entry=0x7ffc239c2950) at kernel/qwidget.cpp:8671 #17 0x7f1cd457565b in QMenu::event(QEvent*) (this=0x55a0afcd20b0, e=0x7ffc239c2950) at widgets/qmenu.cpp:3049 #18 0x7f1cd43e3cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55a0ae6dc490, receiver=receiver@entry=0x55a0afcd20b0, e=e@entry=0x7ffc239c2950) at kernel/qapplication.cpp:3671 #19 0x7f1cd43ecec3 in QApplication::notify(QObject*, QEvent*) (this=, receiver=0x55a0afcd20b0, e=0x7ffc239c2950) at kernel/qapplication.cpp:3115 #20 0x7f1cd38aa6aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a0afcd20b0, event=0x7ffc239c2950) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #21 0x7f1cd43ebfd7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) (receiver=0x55a0afcd20b0, event=event@entry=0x7ffc239c2950, alienWidget=0x0, nativeWidget=0x55a0afcd20b0, buttonDown=, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2603 #22 0x7f1cd4442a86 in QWidgetWindow::handleMouseEvent(QMouseEvent*) (this=0x55a0afcd2570, event=0x7ffc239c2dd0) at /usr/include/c++/9/bits/atomic_base.h:413 #23 0x7f1cd44454dc in QWidgetWindow::event(QEvent*) (event=0x7ffc239c2dd0, this=0x55a0afcd2570) at kernel/qwidgetwindow.cpp:295 #24 QWidgetWindow::event(QEvent*) (this=0x55a0afcd2570, event=0x7ffc239c2dd0) at kernel/qwidgetwindow.cpp:238 #25 0x7f1cd43e3cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55a0ae6dc490, receiver=receiver@entry=0x55a0afcd2570, e=e@entry=0x7ffc239c2dd0) at kernel/qapplication.cpp:3671
[kontact] [Bug 420052] New: Cannot create folders in Personal Contacts
https://bugs.kde.org/show_bug.cgi?id=420052 Bug ID: 420052 Summary: Cannot create folders in Personal Contacts Product: kontact Version: 5.13.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-bugs@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: --- SUMMARY Attempting to create a folder in Personal Contacts fails. STEPS TO REPRODUCE 1. Open Kontact and navigate to Contacts. 2. Right-click Personal Contacts. 3. Choose "Add Address Book Folder", enter a name, and click OK. OBSERVED RESULT Kontact fails with the following error: Could not create address book folder: Could not create collection Test, resourceId 7 EXPECTED RESULT An address book folder is created. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon 5.18 User Edition (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402333] New: Kmail closing unexpectedly, particularly when opening a message to read it.
https://bugs.kde.org/show_bug.cgi?id=402333 Bug ID: 402333 Summary: Kmail closing unexpectedly, particularly when opening a message to read it. Product: kmail2 Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: ke...@keithsayers.id.au Target Milestone: --- Created attachment 117003 --> https://bugs.kde.org/attachment.cgi?id=117003=edit Crash report from /var/crash SUMMARY Kmail crashes when I am opening a message to read it and I get the 'closed unexpectedly' message. I have tried taking the option there to send a report but get told there is not enough to make that useful. STEPS TO REPRODUCE 1. Open Kmial 2. Download new mail 3. Attempt to open any message OBSERVED RESULT After a varying interval of only a few seconds Kmail crashes and I get the 'closed unexpectedly' report. Has happened many times over several weeks EXPECTED RESULT The message to be displayed for reading. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Sending crash report as an attachment because it is so long -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 310694] Kmail thinks it is offline, switching online as offered does not work
https://bugs.kde.org/show_bug.cgi?id=310694 Keith Zubot-Gephart <keit...@gmail.com> changed: What|Removed |Added CC||keit...@gmail.com --- Comment #14 from Keith Zubot-Gephart <keit...@gmail.com> --- Running into this this week at work on Kubuntu 14.04 (KMail 4.13.3, Platform Version 4.13.3) ever since I set my two configured mail accounts (both IMAP, one a local server on the office network and one Gmail) to "Switch offline on Kmail Shutdown". Even though it shows me as online, if try and copy messages from a folder in one account to a folder in another, for example, or even just delte an email, it complains it can't do so in offline mode. I can toggle to offline and back and there's no change. However, as soon as I toggle off the "Switch offline on Kmail Shutdown" option on the two accounts, everything acts fine again. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 302012] New: Akregator crashes each time I try to close a specfic tab with a open webpage.
https://bugs.kde.org/show_bug.cgi?id=302012 Bug ID: 302012 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Akregator crashes each time I try to close a specfic tab with a open webpage. Classification: Unclassified OS: Linux Reporter: drall...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: akregator Application: akregator (4.7.2) KDE Platform Version: 4.7.2 (4.7.2) release 5 Qt Version: 4.7.4 Operating System: Linux 3.1.10-1.9-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: When I close a tab with a open webpage it crashes Akregator. s -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0x7f3baca43760 (LWP 591))] Thread 6 (Thread 0x7f3b8dc76700 (LWP 594)): #0 0x7f3ba4b92e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f3b945739dc in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f3b94573b09 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f3ba4b8ef05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f3ba961a10d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f3b8d375700 (LWP 595)): #0 0x7fff0cbaa8de in ?? () #1 0x7f3ba3accd9a in clock_gettime () from /lib64/librt.so.1 #2 0x7f3baadd2114 in do_gettime (frac=0x7f3b8d374bf8, sec=0x7f3b8d374bf0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7f3baae93d2d in QTimerInfoList::updateCurrentTime (this=0x7f3b80001ed0) at kernel/qeventdispatcher_unix.cpp:339 #5 0x7f3baae939b1 in timerSourceCheckHelper (src=optimized out) at kernel/qeventdispatcher_glib.cpp:150 #6 timerSourceCheckHelper (src=optimized out) at kernel/qeventdispatcher_glib.cpp:144 #7 0x7f3ba3818264 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #8 0x7f3ba3818ab2 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f3ba3818f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7f3baae93586 in QEventDispatcherGlib::processEvents (this=0x7f3b88c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #11 0x7f3baae67a32 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #12 0x7f3baae67c2f in QEventLoop::exec (this=0x7f3b8d374e20, flags=...) at kernel/qeventloop.cpp:201 #13 0x7f3baad7f5df in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #14 0x7f3baad82025 in QThreadPrivate::start (arg=0xa17e90) at thread/qthread_unix.cpp:331 #15 0x7f3ba4b8ef05 in start_thread () from /lib64/libpthread.so.0 #16 0x7f3ba961a10d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f3b3d24e700 (LWP 598)): #0 0x7f3ba4b92e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f3b3d272fc1 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x7f3ba4b8ef05 in start_thread () from /lib64/libpthread.so.0 #3 0x7f3ba961a10d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f3b3ca4d700 (LWP 599)): #0 0x7f3ba4b92e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f3b3d272fc1 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x7f3ba4b8ef05 in start_thread () from /lib64/libpthread.so.0 #3 0x7f3ba961a10d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f3b3c24c700 (LWP 600)): #0 0x7f3ba4b92e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f3b3d272fc1 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x7f3ba4b8ef05 in start_thread () from /lib64/libpthread.so.0 #3 0x7f3ba961a10d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f3baca43760 (LWP 591)): [KCrash Handler] #6 0x in ?? () #7 0x7f3bac65f84e in KParts::StatusBarExtension::statusBar (this=0xb9f0b0) at /usr/src/debug/kdelibs-4.7.2/kparts/statusbarextension.cpp:149 #8 0x7f3bac65fd54 in KParts::StatusBarExtension::~StatusBarExtension (this=0xb9f0b0, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.7.2/kparts/statusbarextension.cpp:99 #9 0x7f3bac660109 in KParts::StatusBarExtension::~StatusBarExtension (this=0xb9f0b0, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.7.2/kparts/statusbarextension.cpp:110 #10 0x7f3baae7a465 in QObjectPrivate::deleteChildren (this=0xb2a430) at kernel/qobject.cpp:1964 #11 0x7f3baae7fa09 in QObject::~QObject (this=0xb8f1c0, __in_chrg=optimized out) at kernel/qobject.cpp:946 #12 0x7f3bac644a98 in KParts::Part::~Part (this=0xb8f1c0, __vtt_parm=0x7f3b8decc8f0, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.7.2/kparts/part.cpp:190 #13 0x7f3b8dc94427 in KWebKitPart::~KWebKitPart
[Bug 243402] New: Crash while moving contacts
https://bugs.kde.org/show_bug.cgi?id=243402 Summary: Crash while moving contacts Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: kjgil...@kjgillis.name Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-21-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Kontact crashed while moving contacts. The contacts were in the personal addressbook stored on my hard drive. They were not in a folder. Contact crashed immediately after dropping them into a new folder in the person address book. -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0xb77eb990 (LWP 18842))] Thread 2 (Thread 0xb0b67b70 (LWP 18873)): #0 0x02d39e16 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1 #1 0x008906fb in qt_gettime () at kernel/qcore_unix.cpp:111 #2 0x00895825 in QTimerInfoList::updateCurrentTime (this=0x92e8ba4) at kernel/qeventdispatcher_unix.cpp:340 #3 0x0089586a in QTimerInfoList::timerWait (this=0x92e8ba4, tm=...) at kernel/qeventdispatcher_unix.cpp:443 #4 0x00893818 in timerSourcePrepareHelper (src=value optimized out, timeout=0xb0b670ac) at kernel/qeventdispatcher_glib.cpp:136 #5 0x008938a5 in timerSourcePrepare (source=0x0, timeout=0x2d3dff4) at kernel/qeventdispatcher_glib.cpp:169 #6 0x0371aaca in g_main_context_prepare () from /lib/libglib-2.0.so.0 #7 0x0371aee9 in ?? () from /lib/libglib-2.0.so.0 #8 0x0371b4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #9 0x0089360f in QEventDispatcherGlib::processEvents (this=0x911f1e0, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #10 0x00866059 in QEventLoop::processEvents (this=0xb0b67270, flags=) at kernel/qeventloop.cpp:149 #11 0x008664aa in QEventLoop::exec (this=0xb0b67270, flags=...) at kernel/qeventloop.cpp:201 #12 0x007625a8 in QThread::exec (this=0x9227728) at thread/qthread.cpp:487 #13 0x00845c1b in QInotifyFileSystemWatcherEngine::run (this=0x9227728) at io/qfilesystemwatcher_inotify.cpp:248 #14 0x0076532e in QThreadPrivate::start (arg=0x9227728) at thread/qthread_unix.cpp:248 #15 0x00df196e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #16 0x05150a4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb77eb990 (LWP 18842)): [KCrash Handler] #6 0x00cc7422 in __kernel_vsyscall () #7 0x050ad651 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0x050b0a82 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0x005aa52f in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #10 0x005a8465 in ?? () from /usr/lib/libstdc++.so.6 #11 0x005a84a2 in std::terminate() () from /usr/lib/libstdc++.so.6 #12 0x005a855b in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #13 0x0087b75a in QMetaObject::activate (sender=0xa4c9648, m=0x363c88, local_signal_index=3, argv=0xbf833d98) at kernel/qobject.cpp:3303 #14 0x001f5183 in KJob::result (this=0xa4c9648, _t1=0xa4c9648) at ./kjob.moc:194 #15 0x001f54e8 in KJob::emitResult (this=0xa4c9648) at ../../kdecore/jobs/kjob.cpp:312 #16 0x00be9f6d in Akonadi::JobPrivate::handleResponse (this=0x994f990, tag=..., data=...) at ../../akonadi/job.cpp:67 #17 0x00c1a8ff in Akonadi::SessionPrivate::dataReceived (this=0xa34c2b8) at ../../akonadi/session.cpp:121 #18 0x00c1b16e in Akonadi::Session::qt_metacall (this=0xa42fe70, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbf833fbc) at ./session.moc:87 #19 0x0086cc9a in QMetaObject::metacall (object=0xa42fe70, cl=18842, idx=7, argv=0xbf833fbc) at kernel/qmetaobject.cpp:237 #20 0x0087b3d5 in QMetaObject::activate (sender=0xa4cfc40, m=0x97ac48, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #21 0x008ca797 in QIODevice::readyRead (this=0xa4cfc40) at .moc/release-shared/moc_qiodevice.cpp:91 #22 0x008ca85f in QIODevice::qt_metacall (this=0xa4cfc40, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf83411c) at .moc/release-shared/moc_qiodevice.cpp:77 #23 0x05ec36ca in QLocalSocket::qt_metacall (this=0xa4cfc40, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf83411c) at .moc/release-shared/moc_qlocalsocket.cpp:81 #24 0x0086cc9a in QMetaObject::metacall (object=0xa4cfc40, cl=18842, idx=4, argv=0xbf83411c) at kernel/qmetaobject.cpp:237 #25 0x0087b3d5 in QMetaObject::activate (sender=0xa4b6188, m=0x97ac48, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #26 0x008ca797 in QIODevice::readyRead (this=0xa4b6188) at .moc/release-shared/moc_qiodevice.cpp:91 #27 0x05ebbdf2 in QAbstractSocketPrivate::canReadNotification (this=0xa0d1378) at socket/qabstractsocket.cpp:626 #28 0x05ea8d1b in QAbstractSocketEngine::readNotification (this=0x9fffd38) at socket/qabstractsocketengine.cpp:154 #29 0x05eaa0e3 in QReadNotifier::event (this=0x6, e=0xbf8345d4) at
[Bug 161044] SMTP SASL: no mechanism available (GMail+SSL)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=161044 --- Additional Comments From kjwaugh gmail com 2008-04-20 22:04 --- I fixed it by installing cyrus sasl plain package. using Software Management from Yast. Have Cyrus sasl already installed by default, checked Konqueror crypto settings and have SSL2 location listed (/usr/lib/sasl2). Using openSuse 10.3, KDE4 live version with Kde 4.03 and Kmail version 4.0.69-26.4. Apparently installing the Plain package adds this functionality. Hope this helps. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 155043] SSL no longer working since recent upgrade (trying to get Gmail with POP3 - SSL configuration)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=155043 --- Additional Comments From kjwaugh gmail com 2008-01-08 21:45 --- You are right, I get the same error when I try to access an SSL web pages using Konqueror - like the Gmail login page and another I tried. (...SSL Negotiation failed etc.) Keith On 8 Jan 2008 12:42:00 -, Thomas McGuire Thomas.McGuire gmx net wrote: [bugs.kde.org quoted mail] You are right,nbsp; I get the same error when I try to access an SSL web pages using Konqueror - like the Gmail login page and another I tried. (quot;...SSL Negotiation failed etc.quot;)brbrKeithbrbrbrdiv class=gmail_quote On 8 Jan 2008 12:42:00 -, Thomas McGuire lt;a href=mailto:Thomas.McGuire gmx netThomas McGuire gmx net/agt; wrote:brblockquote class=gmail_quote style=border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex; div class=Ih2E3d--- You are receiving this mail because: ---brYou reported the bug, or are watching the reporter.brbra href=http://bugs.kde.org/show_bug.cgi?id=155043; target=_blankhttp://bugs.kde.org/show_bug.cgi?id=155043 /abrbrbrbrbr/div--- Additional Comments From Thomas.McGuire gmx net nbsp;2008-01-08 13:42 ---brGoogle POP3 works for me with the packages from the Suse build service.brAgain: Are you seeing the same problems in Konqueror with HTTPS sites? br/blockquote/divbrbr clear=allbr-- brKeith Waugh ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 155043] SSL no longer working since recent upgrade (trying to get Gmail with POP3 - SSL configuration)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=155043 --- Additional Comments From kjwaugh gmail com 2008-01-08 00:00 --- I am using openSuse 10.3, and the Build Service to update KDE4 from RPMs. I continue to update (currently using 3.97.2 Release 4.2), and have not yet seen any difference from day to day. Hope this helps. Keith On 5 Jan 2008 01:18:22 -, Thomas McGuire Thomas.McGuire gmx net wrote: [bugs.kde.org quoted mail] I am using openSuse 10.3, and the Build Service to update KDE4 from RPMs.brI continuenbsp; to update (currently using 3.97.2 quot;Release 4.2quot;),nbsp; and have not yet seen any difference from day to day.brbrHope this helps. brbrKeithbrbrbrdiv class=gmail_quoteOn 5 Jan 2008 01:18:22 -, Thomas McGuire lt;a href=mailto:Thomas.McGuire gmx netThomas McGuire gmx net/agt; wrote:brblockquote class=gmail_quote style=border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex; --- You are receiving this mail because: ---brYou reported the bug, or are watching the reporter.brbra href=http://bugs.kde.org/show_bug.cgi?id=155043; target=_blankhttp://bugs.kde.org/show_bug.cgi?id=155043 /abrThomas.McGuire gmx net changed:brbr nbsp; nbsp; nbsp; nbsp; nbsp; What nbsp; nbsp;|Removed nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; |Addedbrbr nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; Status|UNCONFIRMED nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; |RESOLVED br nbsp; nbsp; nbsp; nbsp; Resolution| nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;|WORKSFORMEbr nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;Summary|SSL no longer working since |SSL no longer working sincebr nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; |recent upgrade (trying to nbsp; |recent upgrade (trying to br nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; |get Gmail with POP3 - SSL nbsp; |get Gmail with POP3 - SSLbr nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; |configuration) nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;|configuration)brbrbrbr--- Additional Comments From Thomas.McGuire gmx net nbsp;2008-01-05 02:18 --- brThis is a bug in Qt, a workaround has recently been added to kdelibs.brYou probably have the same problem with SSL sites in Konqueror, right?brbrPlease reopen if you can still reproduce with the lastest SVN version (make sure you recompile kdelibs, then kdepimlibs) and only have the issue in KMail. br/blockquote/divbrbr clear=allbr-- brKeith Waugh ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 155043] New: SSL no longer working since recent upgrade (trying to get Gmail with POP3 - SSL configuration)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=155043 Summary: SSL no longer working since recent upgrade (trying to get Gmail with POP3 - SSL configuration) Product: kmail Version: 1.9.50 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: kjwaugh gmail com Version: 1.9.50 (using KDE 3.97.2 (KDE 4.0 = 20080101) release 3.1, compiled sources) Compiler: gcc OS:Linux (i686) release 2.6.22.13-0.3-default Could not connect to pop.gmail.com SSL Negotiation Failed The configuration has not changed and it worked before upgrading. Regular POP3 email works fine. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
