[Bug 287140] editing a new time-planing item crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=287140 Myriam Schweingruber myr...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Version|4.9.0 |4.9.1 Ever confirmed|0 |1 --- Comment #15 from Myriam Schweingruber myr...@kde.org --- Confirmed by duplicates. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 290903] stream of notifications stating that mail account: There is currently no session to the IMAP server available after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=290903 Joshua J. Kugler jos...@joshuakugler.com changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #9 from Joshua J. Kugler jos...@joshuakugler.com --- Also happening in KDE 4.9.1. Not only after resume, but in this case it's the network link going down, trying to connect to the IMAP server, then the network link goes back up, and it tries again, and gets the stream of messages. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 276571] Does not import properly messages with large attachments
https://bugs.kde.org/show_bug.cgi?id=276571 Saurav Sengupta sengupta.saura...@gmail.com changed: What|Removed |Added CC||sengupta.saura...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 276571] Does not import properly messages with large attachments
https://bugs.kde.org/show_bug.cgi?id=276571 --- Comment #2 from Saurav Sengupta sengupta.saura...@gmail.com --- This problem still occurs in the default KMail in KDE SC 4.9.1. It has been a long time since it was reported. Is this going to be fixed? -- 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 307140] New: Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=307140 Bug ID: 307140 Severity: crash Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed on exit Classification: Unclassified OS: Linux Reporter: kepl...@cmc.pl Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.1) KDE Platform Version: 4.9.1 Qt Version: 4.8.2 Operating System: Linux 3.2.0-30-generic i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I logged in and while session was starting (including Kontact), I immediately opened the main panel menu and clicked Reboot. Kontact crashed during KDE's shutdown sequence. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb771e9c0 (LWP 5480))] Thread 3 (Thread 0xb5680b40 (LWP 5536)): #0 0x0097a416 in __kernel_vsyscall () #1 0x008ed96b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0x037313dc in __pthread_cond_wait (cond=0x6c5da30, mutex=0x6c5da18) at forward.c:139 #3 0x0652c263 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x6c58940) at wtf/FastMalloc.cpp:2495 #4 0x0652c37f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x6c58940) at wtf/FastMalloc.cpp:1618 #5 0x008e9d4c in start_thread (arg=0xb5680b40) at pthread_create.c:308 #6 0x03723ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb4d57b40 (LWP 5537)): #0 0x019c1dcd in __GI_clock_gettime (clock_id=1, tp=0xb4d57008) at ../sysdeps/unix/clock_gettime.c:116 #1 0x04eeb3b5 in do_gettime (frac=0xb4d57000, sec=0xb4d56ff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x04fd56f6 in QTimerInfoList::updateCurrentTime (this=0xb4402074) at kernel/qeventdispatcher_unix.cpp:343 #4 0x04fd5a4a in QTimerInfoList::timerWait (this=0xb4402074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0x04fd42f3 in timerSourcePrepareHelper (src=optimized out, timeout=0xb4d570ec) at kernel/qeventdispatcher_glib.cpp:136 #6 0x018a4872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x018a4faf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x018a5201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x04fd4db7 in QEventDispatcherGlib::processEvents (this=0xb4400468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x04fa067d in QEventLoop::processEvents (this=0xb4d57270, flags=...) at kernel/qeventloop.cpp:149 #11 0x04fa0919 in QEventLoop::exec (this=0xb4d57270, flags=...) at kernel/qeventloop.cpp:204 #12 0x04e899ec in QThread::exec (this=0x8981248) at thread/qthread.cpp:501 #13 0x04e89adb in QThread::run (this=0x8981248) at thread/qthread.cpp:568 #14 0x04e8ce80 in QThreadPrivate::start (arg=0x8981248) at thread/qthread_unix.cpp:307 #15 0x008e9d4c in start_thread (arg=0xb4d57b40) at pthread_create.c:308 #16 0x03723ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb771e9c0 (LWP 5480)): [KCrash Handler] #7 0x010b0dc4 in operator QItemSelectionModel* (this=error reading variable: Cannot access memory at address 0x5) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:78 #8 QAbstractItemView::selectionModel (this=0x1) at itemviews/qabstractitemview.cpp:766 #9 0x04ad6a46 in MailCommon::FolderTreeWidget::selectedCollections (this=0x1) at ../../mailcommon/foldertreewidget.cpp:244 #10 0x042c26f5 in KMMainWidget::updateFolderMenu (this=0x8e896d0) at ../../kmail/kmmainwidget.cpp:4131 #11 0x042dab36 in KMMainWidget::qt_static_metacall (_o=0x8e896d0, _c=QMetaObject::InvokeMetaMethod, _id=121, _a=0xbff80200) at ./kmmainwidget.moc:458 #12 0x04fb8b81 in QMetaObject::activate (sender=0x918d4d0, m=0x50feed8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3547 #13 0x04fc1b25 in QSingleShotTimer::timeout (this=0x918d4d0) at .moc/release-shared/qtimer.moc:97 #14 0x04fc1c0c in QSingleShotTimer::timerEvent (this=0x918d4d0) at kernel/qtimer.cpp:317 #15 0x04fbcf94 in QObject::event (this=0x918d4d0, e=0xbff8070c) at kernel/qobject.cpp:1157 #16 0x00b02df4 in notify_helper (e=0xbff8070c, receiver=0x918d4d0, this=0x883e170) at kernel/qapplication.cpp:4556 #17 QApplicationPrivate::notify_helper (this=0x883e170, receiver=0x918d4d0, e=0xbff8070c) at kernel/qapplication.cpp:4528 #18 0x00b0815d in QApplication::notify (this=0xbff8070c, receiver=0x918d4d0, e=0xbff8070c) at kernel/qapplication.cpp:4285 #19 0x003132a1 in KApplication::notify (this=0xbff81314, receiver=0x918d4d0, event=0xbff8070c) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x04fa1dde in QCoreApplication::notifyInternal (this=0xbff81314, receiver=0x918d4d0,
[Bug 307144] New: LDAP credentials saved wrongly if password cotains a colon
https://bugs.kde.org/show_bug.cgi?id=307144 Bug ID: 307144 Severity: normal Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: LDAP credentials saved wrongly if password cotains a colon Classification: Unclassified OS: Linux Reporter: joerg.schai...@gmx.de Hardware: Other Status: UNCONFIRMED Component: kldap Product: kdepimlibs Using an LDAP resource for the address book with an user who has a colon in its password, the credentials are constantly mixed up, because parts of the password are used for the user's name. Reproducible: Always Steps to Reproduce: 1. Create an LDAP resource and connect with an user that has a colon in its password 2. Start Kmail, create a new email and start typing in the address field 3. Auto-completion tries to access the LDAP, fails and a dialog appears to enter user name and password 4. Enter correct values, check box to save values and press OK 5. Auto-completion worked, results are visible in the drop-down box 6. Press next character Actual Results: LDAP dialog appears again (obviously LDAP connection failed again) and this time the dialog field for the user contains additionally parts of the password as default Expected Results: It should have been possible to establish the LDAP connection again without problems Example connecting to an Active Directory server with LDAP: - Username: DOMAIN\me - Password: my:pwd The dialog will use later as wrong defaults: - Username: DOMAIN\me:my - Password: pwd It looks like that some component has problems with URL encoding and/or URL interpretation. The LDAP URL should be something like: ldaps://DOMAIN%92me:my%58password@host:port/... However, if some component fails to URL encode the values, you get: ldaps://DOMAIN\me:my:password@host:port/... In this case it is now moot to guess how this URL has to be interpreted, but the wrong default values in the LDAP dialog get obvious. Since the LDAP connection works right directly after entering the proper values, the error must be later either when the values are saved for later reuse or when the URL is built 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 307144] LDAP credentials saved wrongly if password cotains a colon
https://bugs.kde.org/show_bug.cgi?id=307144 --- Comment #1 from Jörg Schaible joerg.schai...@gmx.de --- BTW: Since all configuration files and KWallet contains the plain value of the password, it has to be the code that retrieves the values from the configuration or KWallet. Otherwise the connect to the LDAP directly after entering the proper values in the dialog box again, could not happen. -- 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 307145] New: Kontact todo summary doesn't exclude unstarted items when configured to do so
https://bugs.kde.org/show_bug.cgi?id=307145 Bug ID: 307145 Severity: minor Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact todo summary doesn't exclude unstarted items when configured to do so Classification: Unclassified OS: Linux Reporter: n...@leverton.org Hardware: Ubuntu Packages Status: UNCONFIRMED Component: summary Product: kontact I created a TODO item with a start date in the future. I configured kontact to exclude unstarted todos from the summary page. However the item was still shown there. I changed away from the summary and back to force a refresh, which sometimes seems to be necessary, but the item was still wrongly shown. Reproducible: Always -- 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 298837] kmail does not re-ask for SMTP password if it has been entered wrong
https://bugs.kde.org/show_bug.cgi?id=298837 --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- Any news on this? Its really a PITA if you mistype your SMTP password when sending a mail. Kmail will keep trying to use th wrong password instead of asking the user again. -Marc -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 --- Comment #13 from Myriam Schweingruber myr...@kde.org --- (In reply to comment #12) I nominate this one for extra mile. Laurent? -- 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 306534] filter does not apply systematically on sent messages
https://bugs.kde.org/show_bug.cgi?id=306534 Myriam Schweingruber myr...@kde.org changed: What|Removed |Added Version|4.9.0 |4.9.1 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 307079] Kmail error after saving settings
https://bugs.kde.org/show_bug.cgi?id=307079 Myriam Schweingruber myr...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Version|unspecified |4.8.4 Resolution|--- |BACKTRACE --- Comment #1 from Myriam Schweingruber myr...@kde.org --- Unfortunately your backtrace lacks debugging symbols, please install those and provide a better backtrace. See also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports -- 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 301088] Cannot delete an IMAP folder, although it can create folders
https://bugs.kde.org/show_bug.cgi?id=301088 Myriam Schweingruber myr...@kde.org changed: What|Removed |Added Version|unspecified |4.9.1 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 307165] New: Crash when pressing Ctrl+shift+l
https://bugs.kde.org/show_bug.cgi?id=307165 Bug ID: 307165 Severity: crash Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash when pressing Ctrl+shift+l Classification: Unclassified OS: Linux Reporter: aa...@kde.org Hardware: Ubuntu Packages Status: NEW Component: general Product: kmail2 Application: kmail (4.9.1) KDE Platform Version: 4.9.1 Qt Version: 4.8.3 Operating System: Linux 3.5.0-15-generic x86_64 Distribution: Ubuntu quantal (development branch) -- Information about the crash: - What I was doing when the application crashed: I pressed Ctrl+shift+l after opening kmail and it crashed. I can reproduce the crash all the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7ff9143cc7c0 (LWP 10959))] Thread 4 (Thread 0x7ff90ae72700 (LWP 10963)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7ff91f5ceb2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7ff91f5cec39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7ff9282c7e9a in start_thread (arg=0x7ff90ae72700) at pthread_create.c:308 #4 0x7ff92aa1339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7ff90a571700 (LWP 10964)): #0 0x7ff922e8deb0 in pthread_mutex_lock@plt () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff922ef8f71 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff922ebb7eb in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff922ebbdf9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff922ebbfa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff92b39dc16 in QEventDispatcherGlib::processEvents (this=0x7ff9040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7ff92b36e2bf in QEventLoop::processEvents (this=this@entry=0x7ff90a570dc0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7ff92b36e548 in QEventLoop::exec (this=0x7ff90a570dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7ff92b26fb10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7ff92b272aec in QThreadPrivate::start (arg=0x1afa3b0) at thread/qthread_unix.cpp:338 #10 0x7ff9282c7e9a in start_thread (arg=0x7ff90a571700) at pthread_create.c:308 #11 0x7ff92aa1339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 2 (Thread 0x7ff909029700 (LWP 10965)): #0 0x7ff92aa079e3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7ff922ebbe84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff922ebbfa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff92b39dc16 in QEventDispatcherGlib::processEvents (this=0x7ff8fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7ff92b36e2bf in QEventLoop::processEvents (this=this@entry=0x7ff909028d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7ff92b36e548 in QEventLoop::exec (this=0x7ff909028d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7ff92b26fb10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7ff92b34e9af in QInotifyFileSystemWatcherEngine::run (this=0x1b45120) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7ff92b272aec in QThreadPrivate::start (arg=0x1b45120) at thread/qthread_unix.cpp:338 #9 0x7ff9282c7e9a in start_thread (arg=0x7ff909029700) at pthread_create.c:308 #10 0x7ff92aa1339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7ff9143cc7c0 (LWP 10959)): [KCrash Handler] #6 QList (l=error reading variable: Cannot access memory at address 0x20, this=0x7fff823f9960) at /usr/include/qt4/QtCore/qlist.h:122 #7 QForeachContainer (t=error reading variable: Cannot access memory at address 0x20, this=0x7fff823f9960) at /usr/include/qt4/QtCore/qglobal.h:2346 #8 Akonadi::FavoriteCollectionsModel::collections (this=0x0) at ../../akonadi/favoritecollectionsmodel.cpp:181 #9 0x7ff92748e412 in Akonadi::StandardActionManager::Private::slotSynchronizeFavoriteCollections (this=optimized out) at ../../akonadi/standardactionmanager.cpp:956 #10 0x7ff927487e0e in qt_static_metacall (_a=optimized out, _id=optimized out, _o=optimized out, _c=optimized out) at ./standardactionmanager.moc:160 #11 Akonadi::StandardActionManager::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=0x7fff823f9b70) at ./standardactionmanager.moc:137 #12 0x7ff92b384f5f in QMetaObject::activate
[Bug 307165] Crash when pressing Ctrl+shift+l
https://bugs.kde.org/show_bug.cgi?id=307165 András Manţia aman...@kde.org changed: What|Removed |Added Status|NEW |RESOLVED Version Fixed In||4.10 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/cb9bd1a2b30be96f4a82520f ||5ffcaf6584aefd5e --- Comment #1 from András Manţia aman...@kde.org --- Git commit cb9bd1a2b30be96f4a82520f5ffcaf6584aefd5e by Andras Mantia. Committed on 21/09/2012 at 18:36. Pushed by amantia into branch 'master'. Enable the favorite actions only when we have favorite folders. This avoid crashes in the StandardMailActionManager if the action is invoked without a favorite model. FIXED-IN: 4.10 M +12 -0kmail/kmmainwidget.cpp http://commits.kde.org/kdepim/cb9bd1a2b30be96f4a82520f5ffcaf6584aefd5e -- 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 307165] Crash when pressing Ctrl+shift+l
https://bugs.kde.org/show_bug.cgi?id=307165 --- Comment #2 from András Manţia aman...@kde.org --- Git commit a0d3c0ad6f8811cbb1c7eabeae748ee1888af735 by Andras Mantia. Committed on 21/09/2012 at 18:39. Pushed by amantia into branch 'KDE/4.9'. Enable the favorite actions only when we have favorite folders. This avoid crashes in the StandardMailActionManager if the action is invoked without a favorite model. FIXED-IN: 4.9.2 (cherry picked from commit cb9bd1a2b30be96f4a82520f5ffcaf6584aefd5e) M +11 -0kmail/kmmainwidget.cpp http://commits.kde.org/kdepim/a0d3c0ad6f8811cbb1c7eabeae748ee1888af735 -- 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 303861] Can't write CalDav items from korganizer
https://bugs.kde.org/show_bug.cgi?id=303861 mgualtieri mgualti...@sinthera.com changed: What|Removed |Added CC||mgualti...@sinthera.com --- Comment #11 from mgualtieri mgualti...@sinthera.com --- Confirmed on 4.9.1!!! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 306534] filter does not apply systematically on sent messages
https://bugs.kde.org/show_bug.cgi?id=306534 --- Comment #4 from Daniel Moyne daniel.mo...@free.fr --- may be related to presence of attachments -- 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 303861] Can't write CalDav items from korganizer
https://bugs.kde.org/show_bug.cgi?id=303861 Allen Winter win...@kde.org changed: What|Removed |Added CC||win...@kde.org --- Comment #12 from Allen Winter win...@kde.org --- this will be really hard to fix and test if the problem is specific to Exchange's CalDAV. is there some free site where I can test? I use CalDAV with Google Calendar and can write there without any problems. -- 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 305280] Kmail crashes wyle moving a folder to the parant folder
https://bugs.kde.org/show_bug.cgi?id=305280 Allen Winter win...@kde.org changed: What|Removed |Added CC||win...@kde.org --- Comment #8 from Allen Winter win...@kde.org --- Myriam, but this looks like a bug in kdelibs, no? -- 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 307079] Kmail error after saving settings
https://bugs.kde.org/show_bug.cgi?id=307079 Allen Winter win...@kde.org changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||win...@kde.org Resolution|BACKTRACE |UNMAINTAINED --- Comment #2 from Allen Winter win...@kde.org --- sorry, this is kmail1 and we no longer maintain that version. -- 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 307185] New: Kontact crashes on login
https://bugs.kde.org/show_bug.cgi?id=307185 Bug ID: 307185 Severity: crash Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes on login Classification: Unclassified OS: Linux Reporter: rob...@narnia.homeunix.com Hardware: Ubuntu Packages Status: NEW Component: general Product: kontact Application: kontact (4.9.1) KDE Platform Version: 4.9.1 Qt Version: 4.8.3 Operating System: Linux 3.5.0-10-generic x86_64 Distribution: Ubuntu quantal (development branch) -- Information about the crash: When I log in to KDE4, this crash report always pops up. I can't open Kontact until I close the crash report, so it really is running, but it crashes before I can interact with it. Once I close the bug report and reopen Kontact, everything seems fine. Possibly there is a race condition with something in Plasma? A possible related symptom is that the first time I pull up Akregator, it asks me if I want to restore a previous session. Even if I close out normally, so that the message goes away, it comes back whenever I log out and back in. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f500d9637c0 (LWP 3107))] Thread 5 (Thread 0x7f50064d8700 (LWP 3192)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f501eedab2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f501eedac39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f501a425e9a in start_thread (arg=0x7f50064d8700) at pthread_create.c:308 #4 0x7f501fc0339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f5005bd7700 (LWP 3209)): #0 0x7f501fbf79e3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5019f56e84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5019f56fa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5020377c16 in QEventDispatcherGlib::processEvents (this=0x7f5008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f50203482bf in QEventLoop::processEvents (this=this@entry=0x7f5005bd6dc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5020348548 in QEventLoop::exec (this=0x7f5005bd6dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f5020249b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f502024caec in QThreadPrivate::start (arg=0x122a460) at thread/qthread_unix.cpp:338 #8 0x7f501a425e9a in start_thread (arg=0x7f5005bd7700) at pthread_create.c:308 #9 0x7f501fc0339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 3 (Thread 0x7f4fb7ef7700 (LWP 3413)): #0 0x7f501fbf79e3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5019f56e84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5019f56fa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5020377c16 in QEventDispatcherGlib::processEvents (this=0x7f4fb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f50203482bf in QEventLoop::processEvents (this=this@entry=0x7f4fb7ef6d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5020348548 in QEventLoop::exec (this=0x7f4fb7ef6d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f5020249b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f50203289af in QInotifyFileSystemWatcherEngine::run (this=0x188e2b0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f502024caec in QThreadPrivate::start (arg=0x188e2b0) at thread/qthread_unix.cpp:338 #9 0x7f501a425e9a in start_thread (arg=0x7f4fb7ef7700) at pthread_create.c:308 #10 0x7f501fc0339d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f4faa7d2700 (LWP 3445)): #0 0x7f501fbf79e3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f5019f56e84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5019f56fa4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5020377c16 in QEventDispatcherGlib::processEvents (this=0x7f4fa8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f50203482bf in QEventLoop::processEvents (this=this@entry=0x7f4faa7d1dc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5020348548 in QEventLoop::exec (this=0x7f4faa7d1dc0, flags=...)
