[Bug 296564] kmail2 doesn't remember SMTP password
https://bugs.kde.org/show_bug.cgi?id=296564 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- you store it in kwallet ? -- 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 296561] kmail2 loses POP3 incoming mails
https://bugs.kde.org/show_bug.cgi?id=296561 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- we fixed a lot of bugs in 4.8 please update to 4.8 -- 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 296450] Duplicate General tabs are shown in Address book properties
https://bugs.kde.org/show_bug.cgi?id=296450 --- Comment #2 from Laurent Montel mon...@kde.org --- Git commit e3fc391f766c91ea95ab87002381bca371e74b63 by Montel Laurent. Committed on 23/03/2012 at 09:04. Pushed by mlaurent into branch 'master'. Add missing setCollectionPropertiesPageNames need to fix bug #296450 M +5-0akonadi/contact/standardcontactactionmanager.cpp M +5-0akonadi/contact/standardcontactactionmanager.h http://commits.kde.org/kdepimlibs/e3fc391f766c91ea95ab87002381bca371e74b63 -- 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 296450] Duplicate General tabs are shown in Address book properties
https://bugs.kde.org/show_bug.cgi?id=296450 --- Comment #3 from Laurent Montel mon...@kde.org --- Git commit e63a9e6d03aa8f36f795e6a7621468834dbffebb by Montel Laurent. Committed on 23/03/2012 at 09:04. Pushed by mlaurent into branch 'KDE/4.8'. Add missing setCollectionPropertiesPageNames need to fix bug #296450 (cherry picked from commit e3fc391f766c91ea95ab87002381bca371e74b63) M +5-0akonadi/contact/standardcontactactionmanager.cpp M +5-0akonadi/contact/standardcontactactionmanager.h http://commits.kde.org/kdepimlibs/e63a9e6d03aa8f36f795e6a7621468834dbffebb -- 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 296450] Duplicate General tabs are shown in Address book properties
https://bugs.kde.org/show_bug.cgi?id=296450 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.8.2 Resolution|--- |FIXED --- Comment #4 from Laurent Montel mon...@kde.org --- Git commit 1fde2df74fc23ca85c9d45dfc41801832be3df24 by Montel Laurent. Committed on 23/03/2012 at 09:06. Pushed by mlaurent into branch 'master'. Fix Bug 296450 - Duplicate General tabs are shown in Address book properties FIXED-IN: 4.8.2 M +5-0kaddressbook/mainwidget.cpp http://commits.kde.org/kdepim/1fde2df74fc23ca85c9d45dfc41801832be3df24 -- 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 296450] Duplicate General tabs are shown in Address book properties
https://bugs.kde.org/show_bug.cgi?id=296450 --- Comment #5 from Laurent Montel mon...@kde.org --- Git commit dd33fb42da5ecbb652d37eef3777c14244dc9c4b by Montel Laurent. Committed on 23/03/2012 at 09:06. Pushed by mlaurent into branch 'KDE/4.8'. Fix Bug 296450 - Duplicate General tabs are shown in Address book properties FIXED-IN: 4.8.2 (cherry picked from commit 1fde2df74fc23ca85c9d45dfc41801832be3df24) M +5-0kaddressbook/mainwidget.cpp http://commits.kde.org/kdepim/dd33fb42da5ecbb652d37eef3777c14244dc9c4b -- 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 282721] no filtering on sent mails
https://bugs.kde.org/show_bug.cgi?id=282721 --- Comment #9 from Daniel Moyne daniel.mo...@free.fr --- bug still on on 4.8.1 What is the signification of apply filter before sending mail? -- 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 296609] New: KMail does not display accounts from laposte.net
https://bugs.kde.org/show_bug.cgi?id=296609 Bug ID: 296609 Severity: normal Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail does not display accounts from laposte.net Classification: Unclassified OS: Linux Reporter: mboqu...@free.fr Hardware: Other Status: NEW Component: general Product: kmail2 Hello, Since 4.8.0 I believe, kmail does not display my IMAP account on laposte.net. I tried to create new accounts in kmail and I have the same problem. With other clients i have no problem checking my emails. In the Akonadi debugger i get: AgentBase(akonadi_imap_resource_3): Select failed, server replied: A36 NO System I/O error. The Resource Task List is the following: ResourceScheduler: Online current task: 21 Invalid (no task) queue 0 is empty queue 1 is empty queue 2 is empty queue 3 is empty queue 4 is empty Thanks! -- 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 296613] New: Kontact crash switching beetween emails
https://bugs.kde.org/show_bug.cgi?id=296613 Bug ID: 296613 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crash switching beetween emails Classification: Unclassified OS: Linux Reporter: dhar...@datashit.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: 1)Select new unread email 2)Select another unread email 3)Sometimes (frequently but not always) Kontact crash! -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb773f730 (LWP 27175))] Thread 4 (Thread 0xb5ca9b70 (LWP 27177)): #0 0x00d70416 in __kernel_vsyscall () #1 0x00bcca5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x0023809c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0x073af883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0x073af99f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x00bc8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x0022a46e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 3 (Thread 0xb5380b70 (LWP 27178)): #0 0x00d65d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x04885e35 in do_gettime (frac=0xb5380030, sec=0xb5380028) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x0496fb56 in QTimerInfoList::updateCurrentTime (this=0x8435274) at kernel/qeventdispatcher_unix.cpp:343 #4 0x0496feaa in QTimerInfoList::timerWait (this=0x8435274, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0x0496e6c3 in timerSourcePrepareHelper (src=optimized out, timeout=0xb538011c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x0288188c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x02882637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x02882c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x0496f217 in QEventDispatcherGlib::processEvents (this=0x8433a30, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x0493ad6d in QEventLoop::processEvents (this=0xb53802b0, flags=...) at kernel/qeventloop.cpp:149 #11 0x0493b009 in QEventLoop::exec (this=0xb53802b0, flags=...) at kernel/qeventloop.cpp:204 #12 0x048249dc in QThread::exec (this=0x8433640) at thread/qthread.cpp:501 #13 0x04824acb in QThread::run (this=0x8433640) at thread/qthread.cpp:568 #14 0x04827e70 in QThreadPrivate::start (arg=0x8433640) at thread/qthread_unix.cpp:298 #15 0x00bc8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0x0022a46e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xb229fb70 (LWP 27246)): #0 0x0288188c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0x02882637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x02882c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x0496f217 in QEventDispatcherGlib::processEvents (this=0x9034b28, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x0493ad6d in QEventLoop::processEvents (this=0xb229f280, flags=...) at kernel/qeventloop.cpp:149 #5 0x0493b009 in QEventLoop::exec (this=0xb229f280, flags=...) at kernel/qeventloop.cpp:204 #6 0x048249dc in QThread::exec (this=0x8623730) at thread/qthread.cpp:501 #7 0x049182dd in QInotifyFileSystemWatcherEngine::run (this=0x8623730) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x04827e70 in QThreadPrivate::start (arg=0x8623730) at thread/qthread_unix.cpp:298 #9 0x00bc8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #10 0x0022a46e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb773f730 (LWP 27175)): [KCrash Handler] #7 0x05918f0d in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0xa4a6300, hm=) at access/qnetworkaccesshttpbackend.cpp:827 #8 0x059afd0d in QNetworkAccessHttpBackend::qt_static_metacall (_o=0xa4a6300, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xae914068) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #9 0x0494e461 in QMetaCallEvent::placeMetaCall (this=0xae914020, object=0xa4a6300) at kernel/qobject.cpp:525 #10 0x049574db in QObject::event (this=0xa4a6300, e=0xae914020) at kernel/qobject.cpp:1195 #11 0x00eab844 in notify_helper (e=0xae914020, receiver=0xa4a6300, this=0x82da538) at kernel/qapplication.cpp:4555 #12
[Bug 296616] New: kmail2: mails available offline if offlinemode is disabled
https://bugs.kde.org/show_bug.cgi?id=296616 Bug ID: 296616 Severity: normal Version: Git (master) Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2: mails available offline if offlinemode is disabled Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Other Status: UNCONFIRMED Component: misc Product: kmail2 Hi, I have two IMAP Accounts configured. For one the Offline IMAP is enabled and for the other its disabled. Now when I set kmail to offline mode, both accounts do have all mails available. (Status in Accounts dialog where akonadi resources are listet says that its currently Offline below Account name. This might have security implications as mail is locally stored where it should not be. Is this a real bug or do I have a f***ed up setup? I *may* be that I disabled offline for one account after if having initially enabled or the other way around... -- 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 296617] New: Kontact crashed deleting mail from inbox
https://bugs.kde.org/show_bug.cgi?id=296617 Bug ID: 296617 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed deleting mail from inbox Classification: Unclassified OS: Linux Reporter: cl...@vacuumtube.org.uk Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.1) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.3.0-4.fc16.x86_64 x86_64 Distribution: Fedora release 16 (Verne) -- Information about the crash: - What I was doing when the application crashed: Deleting a single item of mail from the inbox. The account is an IMAP account. Every time I try to delete a mail from this inbox kontact crashes. Evolution does not have a problem. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f76ef488840 (LWP 11244))] Thread 4 (Thread 0x7f76e2e9e700 (LWP 11245)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x0038705b86ec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3870f7cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x0038705b8819 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003842a07d90 in start_thread (arg=0x7f76e2e9e700) at pthread_create.c:309 #4 0x0038422f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f76e2585700 (LWP 11246)): #0 0x0038422e85c3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003845244fd8 in g_main_context_poll (n_fds=1, fds=0x7f76dc0013e0, priority=optimized out, timeout=275, context=0x7f76dc0009a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x7f76dc0009a0, block=optimized out, dispatch=1, self=optimized out) at gmain.c:3084 #3 0x00384524549c in g_main_context_iteration (context=0x7f76dc0009a0, may_block=1) at gmain.c:3152 #4 0x00384d1a7dc6 in QEventDispatcherGlib::processEvents (this=0x7f76dc0008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x00384d178182 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x00384d1783d7 in QEventLoop::exec (this=0x7f76e2584d40, flags=...) at kernel/qeventloop.cpp:204 #7 0x00384d078b27 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x00384d07bb6b in QThreadPrivate::start (arg=0x1e200a0) at thread/qthread_unix.cpp:298 #9 0x003842a07d90 in start_thread (arg=0x7f76e2585700) at pthread_create.c:309 #10 0x0038422f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f7697dff700 (LWP 11269)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x00384d07bfdf in wait (time=3, this=0x2a0ca00) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x2a0c978, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x00384d06f5af in QThreadPoolThread::run (this=0x2a21870) at concurrent/qthreadpool.cpp:141 #4 0x00384d07bb6b in QThreadPrivate::start (arg=0x2a21870) at thread/qthread_unix.cpp:298 #5 0x003842a07d90 in start_thread (arg=0x7f7697dff700) at pthread_create.c:309 #6 0x0038422f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f76ef488840 (LWP 11244)): [KCrash Handler] #6 ref (this=0x250027003d0030) at ../../src/corelib/arch/qatomic_x86_64.h:121 #7 QList (l=..., this=0x7fff0a91e2f0) at ../../src/corelib/tools/qlist.h:122 #8 QNetworkCacheMetaData::rawHeaders (this=0x7fff0a91e610) at access/qabstractnetworkcache.cpp:240 #9 0x00384d66f03c in QNetworkAccessHttpBackend::fetchCacheMetaData (this=0x2fcda90, oldMetaData=...) at access/qnetworkaccesshttpbackend.cpp:1019 #10 0x00384d6707d4 in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x2fcda90, hm=optimized out, sc=optimized out, rp=optimized out, pu=optimized out, db=optimized out, contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:828 #11 0x00384d6f6409 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x2fcda90, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #12 0x00384d191f16 in QObject::event (this=0x2fcda90, e=optimized out) at kernel/qobject.cpp:1195 #13 0x0038571c9994 in notify_helper (e=0x7f768800d980, receiver=0x2fcda90, this=0x1e0cd30) at kernel/qapplication.cpp:4550 #14
[Bug 296617] Kontact crashed deleting mail from inbox
https://bugs.kde.org/show_bug.cgi?id=296617 Clive Messer cl...@vacuumtube.org.uk changed: What|Removed |Added Version|unspecified |4.8.x -- 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 296620] New: Kmail crash after updating IMAP Server configuration and entering password
https://bugs.kde.org/show_bug.cgi?id=296620 Bug ID: 296620 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Kmail crash after updating IMAP Server configuration and entering password Classification: Unclassified OS: Linux Reporter: trackmas...@gmx.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.2.0-18-generic x86_64 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: Notice that I've recently (2 weeks ago) upgraded my system from Kubuntu 8.04 to 10.04 and 12.04 beta. System was updated and has been restarted some minutes before this crash happened. Starting KMail first time on 12.04, it asked me to migrate old (KMail/8.04) data, I agreed but it wasn't successful (possibly thats simply due the fact that I'm using only IMAP ?). I had to re-enter my account settings, and I typed in a wrong server at first (imap.strato-mail.net instead of imap.strato.de), which led to various pop-ups requesting permission to store password, next one complaining about bad reply, and some more. Accepted password storage request and access of KWallet, closed error messages. The account did not show up in KMail (only Local Folder), so I've entered the configure page, where my IMAP Account 1 showed up as No server vonfigured yet. I checked the FAQ of my provider and it seems that imap.strato.de is the correct server now, so I have updated it, clicking okay, and then this crash occured. I'm not too sure whether I had to re-type my password right before the crash or not, and there may be a hidden password window floating around (the popups before). I'm sure that I had given my credentials (and saved them in KWallet) initially when these popups came, but since the server name changed I don't now if that information is reused, or not. Lets say I'm 90% sure that I did NOT re-type my password, but since I've checked the server resolving issue (see below) in between, I just have to say I'm not 100% sure about that. Possibly of interest is that right now there are two windows (Local Folders - KMail and Configure - KMail) visible while typing this report in the Crash reporting assistant. A note about the cause of having to update the server name: Both imap.strato.de and imap.strato-mail.net seem to resolve to IP 81.169.145.103 (used dig --trace), anyway the latter one is strange (seems that only three nameservers of hsd.de knows about this address, which seems to be have valid some years ago, at least google knows about this setup for strato ;) ) Not sure if this is related to this bug, but oddities are always good to know :P -- Backtrace: Application: IMAP Account 1 of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f85d5a1a780 (LWP 10132))] Thread 2 (Thread 0x7f85bbfff700 (LWP 10139)): #0 0x7f85d13cb0bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f85cff52bbf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f85cff17bad in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f85cff18086 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f85cff18214 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f85d4e3fa96 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f85d4e0f2f2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f85d4e0f547 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f85d4d0ef97 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f85d4def06f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7f85d4d11fbb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f85d0a33e9a in start_thread (arg=0x7f85bbfff700) at pthread_create.c:308 #12 0x7f85d13d84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 1 (Thread 0x7f85d5a1a780 (LWP 10132)): [KCrash Handler] #6 0x0030 in ?? () #7 0x7f85d4e260e8 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00454f3b in SessionPool::onPasswordRequestDone (this=0x1d42e70, resultType=optimized out,
[Bug 296620] Kmail crash after updating IMAP Server configuration and entering password
https://bugs.kde.org/show_bug.cgi?id=296620 --- Comment #1 from Björn Toschi trackmas...@gmx.net --- After restarting KMail, some more issues showed up. Whenever I change the server, a message box with title Could not authenticate is showing up. It says StartTls failed, server replied: A01 BAD command unrecognized: STARTTLLS [ CLIENTBUG ] Whenever I say try again, it re-requests my password, but still I come here again. Changing to SSH/TLS did not work. The Configure page itself displayed that the account could not be used due to KWallet access being rejected by user. Auto-detecting connection settings led to Encryption: None, which seems to work (I see correct folder names being synced). Setting manually to SSL/TLS sometimes works, sometimes this changes it to be offline. I did not manage to actually see the folders in KMail itself. Seems there is something _really_ broken. -- 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 295676] kmail crash on compose new email
https://bugs.kde.org/show_bug.cgi?id=295676 E.T. Anderson firebringe...@gmail.com changed: What|Removed |Added CC||firebringe...@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 295676] kmail crash on compose new email
https://bugs.kde.org/show_bug.cgi?id=295676 --- Comment #6 from E.T. Anderson firebringe...@gmail.com --- Created attachment 69828 -- https://bugs.kde.org/attachment.cgi?id=69828action=edit New crash information added by DrKonqi kmail (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 - What I was doing when the application crashed: When I click the New button in Kmail and I have the %SIGNATURE macro set in my new message template, I get a crash. When I leave the %SIGNATURE macro out of the template, Kmail does not crash. I am able to add %SIGNATURE to the reply template without a crash. -- Backtrace (Reduced): #6 0x7f92b80cf8dc in QTextLine::cursorToX (this=0x7fff8edb8270, cursorPos=0x7fff8edb82b8, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #7 0x7f92b80ac9cc in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=0x7fff8edb8270) at ../../include/QtGui/../../src/gui/text/qtextlayout.h:230 #8 QTextControlPrivate::rectForPosition (this=0x4bb9160, position=optimized out) at text/qtextcontrol.cpp:1368 #9 0x7f92b80b01e8 in QTextControl::ensureCursorVisible (this=optimized out) at text/qtextcontrol.cpp:2950 #10 0x7f92b80b3d83 in QTextControl::setTextCursor (this=0x4a50d00, cursor=...) at text/qtextcontrol.cpp:833 -- 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 296624] New: KMail crash on selecting mail
https://bugs.kde.org/show_bug.cgi?id=296624 Bug ID: 296624 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail crash on selecting mail Classification: Unclassified OS: Linux Reporter: tho...@tanghus.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: It happens *very* often, when I either select a mail or delete one so a new mail is selected, that I get this crash. This morning I went through around 100 mails and I had around 10 crashes. The reports I've marked as possible dupes have very similar backtraces, but not exactly so I chose to create a new report. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f608c12c7c0 (LWP 3483))] Thread 4 (Thread 0x7f6070a24700 (LWP 3484)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f6088963c2c in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f608931a220) at wtf/FastMalloc.cpp:2495 #2 0x7f6088963d59 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at wtf/FastMalloc.cpp:1618 #3 0x7f6084130efc in start_thread (arg=0x7f6070a24700) at pthread_create.c:304 #4 0x7f608967359d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f6070123700 (LWP 3485)): #0 0x7f60841341fd in __pthread_mutex_unlock_usercnt (mutex=optimized out, decr=optimized out) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x1f7c528) at pthread_mutex_unlock.c:290 #2 0x7f6083c5ed79 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6083c5f429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6089de1c06 in QEventDispatcherGlib::processEvents (this=0x1f7c0f0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f6089db13e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f6089db1637 in QEventLoop::exec (this=0x7f6070122dc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f6089cb1067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f6089cb408b in QThreadPrivate::start (arg=0x1d98060) at thread/qthread_unix.cpp:298 #9 0x7f6084130efc in start_thread (arg=0x7f6070123700) at pthread_create.c:304 #10 0x7f608967359d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f6024bce700 (LWP 3496)): #0 0x7f6084133034 in __pthread_mutex_lock (mutex=0x2cfea68) at pthread_mutex_lock.c:61 #1 0x7f6083c5e023 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6083c5edfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6083c5f429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6089de1c06 in QEventDispatcherGlib::processEvents (this=0x2cef1d0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f6089db13e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f6089db1637 in QEventLoop::exec (this=0x7f6024bcdd90, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f6089cb1067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f6089d9117f in QInotifyFileSystemWatcherEngine::run (this=0x1fe3910) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7f6089cb408b in QThreadPrivate::start (arg=0x1fe3910) at thread/qthread_unix.cpp:298 #10 0x7f6084130efc in start_thread (arg=0x7f6024bce700) at pthread_create.c:304 #11 0x7f608967359d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7f608c12c7c0 (LWP 3483)): [KCrash Handler] #6 0x7f6084ee2732 in node_copy (src=optimized out, to=0x3ac3618, from=0x228b2218, this=0x7fff377faa20) at ../../include/QtCore/../../src/corelib/tools/qlist.h:399 #7 QListQPairQByteArray, QByteArray ::detach_helper (this=0x7fff377faa20, alloc=optimized out) at ../../include/QtCore/../../src/corelib/tools/qlist.h:711 #8 0x7f6084f2182d in detach_helper (this=optimized out) at ../../include/QtCore/../../src/corelib/tools/qlist.h:725 #9 QList (this=optimized out, l=optimized out) at ../../include/QtCore/../../src/corelib/tools/qlist.h:122 #10 QList (l=optimized out, this=optimized out) at access/qabstractnetworkcache.cpp:238 #11 QNetworkCacheMetaData::rawHeaders (this=optimized out) at
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #100 from Laurent Montel mon...@kde.org --- Why all the time add the same backtrace Please use valgrind to give more infos for example. I know the backtrace but it's more usefull to use other program as valgrind to try to detect why it crashs... 99 comments and just same backtrace... -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #101 from Marc Collin coll...@laboiteaprog.com --- (In reply to comment #100) Why all the time add the same backtrace Please use valgrind to give more infos for example. I know the backtrace but it's more usefull to use other program as valgrind to try to detect why it crashs... 99 comments and just same backtrace... maybe because people are only user? and not developper, designer, architect kde crash report allow user to send backtrace if you find a way to add valgrind info automatically... in thing people will love you -- 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 296609] KMail does not display accounts from laposte.net
https://bugs.kde.org/show_bug.cgi?id=296609 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||kdepim-bugs@kde.org, ||mon...@kde.org, ||vkra...@kde.org Component|general |IMAP resource Assignee|kdepim-bugs@kde.org |er...@kde.org Product|kmail2 |Akonadi -- 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 296629] New: kmail-4.8.1 uses quoted-printable encoded composite mime parts, violating RFC2045
https://bugs.kde.org/show_bug.cgi?id=296629 Bug ID: 296629 Severity: normal Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail-4.8.1 uses quoted-printable encoded composite mime parts, violating RFC2045 Classification: Unclassified OS: Linux Reporter: devuran...@gmx.net Hardware: Other Status: UNCONFIRMED Component: composer Product: kmail2 listserv.fnal.gov replies to my messages sent with kmail-4.8.1: --- Your message contains a QUOTED-PRINTABLE encoded composite MIME part, which is not allowed by Internet standards (see RFC2045, section 6.4, paragraph 5). In plain English, an error in your mail program, or in a firewall or mail gateway between your computer and LISTSERV, has caused an error in the format of your message. --- It refers to this paragraph: --- Certain Content-Transfer-Encoding values may only be used on certain media types. In particular, it is EXPRESSLY FORBIDDEN to use any encodings other than 7bit, 8bit, or binary with any composite media type, i.e. one that recursively includes other Content-Type fields. Currently the only composite media types are multipart and message. All encodings that are desired for bodies of type multipart or message must be done at the innermost level, by encoding the actual body that needs to be encoded. --- The quoted message listserv attached shows that kmail did indeed violate this: --- Content-Type: multipart/signed; boundary=...; micalg=pgp-sha1; protocol=application/pgp-signature Content-Transfer-Encoding: quoted-printable --- This is the same as Akonadi saved in my sent folder, so I can exclude a bug in a mail gateway. The issue did not happen with kmail-4.8.0 or 4.7.4. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 296564] kmail2 doesn't remember SMTP password
https://bugs.kde.org/show_bug.cgi?id=296564 --- Comment #2 from Christopher Heiny christopherhe...@gmail.com --- Presumably that is the case. kmail2 or some related service does ask for access to the wallet, sometimes with annoying frequency, and sometimes on a completely different display than it is running on. Where should I check to confirm this? -- 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 296410] Kontact 4.8.1 (KDE 4.8.1, Kubuntu 11.10, 64 bit) has crashed when deleting mails.
https://bugs.kde.org/show_bug.cgi?id=296410 --- Comment #2 from Thomas Olsen tho...@tanghus.net --- Created attachment 69834 -- https://bugs.kde.org/attachment.cgi?id=69834action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 - What I was doing when the application crashed: Scrolling through the list of emails - for the kde-pim mailing list ironically ;-) -- Backtrace (Reduced): #6 malloc_consolidate (av=0x7f890820) at malloc.c:5161 #7 0x7f89739cba4f in malloc_consolidate (av=0x7f890820) at malloc.c:5115 #8 _int_malloc (av=0x7f890820, bytes=65536) at malloc.c:4373 #9 0x7f89739ce3cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660 #10 0x7f8974076088 in QByteArray::realloc (this=0x120d4c08, alloc=65504) at tools/qbytearray.cpp:1452 -- 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 296410] Kontact 4.8.1 (KDE 4.8.1, Kubuntu 11.10, 64 bit) has crashed when deleting mails.
https://bugs.kde.org/show_bug.cgi?id=296410 Thomas Olsen tho...@tanghus.net changed: What|Removed |Added CC||tho...@tanghus.net -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 296033] Massive problems with akonadi, kwallet and IMAP
https://bugs.kde.org/show_bug.cgi?id=296033 George L. Emigh ab...@georgelemigh.com changed: What|Removed |Added CC||ab...@georgelemigh.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 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #102 from Laurent Montel mon...@kde.org --- (In reply to comment #101) (In reply to comment #100) Why all the time add the same backtrace Please use valgrind to give more infos for example. I know the backtrace but it's more usefull to use other program as valgrind to try to detect why it crashs... 99 comments and just same backtrace... maybe because people are only user? and not developper, designer, architect kde crash report allow user to send backtrace if you find a way to add valgrind info automatically... in thing people will love you For the moment kcrash can't use valgrind but add all the time the same backtrace is not usefull, for me it's just increase number of email in my mailbox. We know that kmail crashs with this backtrace ok so why add same backtrace ? -- 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 296564] kmail2 doesn't remember SMTP password
https://bugs.kde.org/show_bug.cgi?id=296564 --- Comment #3 from Laurent Montel mon...@kde.org --- look at in kwalletmanager if you have mailtransport entry for example -- 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 296564] kmail2 doesn't remember SMTP password
https://bugs.kde.org/show_bug.cgi?id=296564 --- Comment #4 from Christopher Heiny christopherhe...@gmail.com --- It shows mailtransports(5). Also kmail(4). I'm unable to look inside those folders, though. -- 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 285121] kmail2 bugs when choosing a diffusion list in contacts
https://bugs.kde.org/show_bug.cgi?id=285121 --- Comment #3 from poubelle...@neuf.fr --- First you have confirmed this bug, but after you indicate a possibly malfunctioning of nepomuk. Nepomuk works fine on my install. Please can you tell me how I have to configure adresse book / diffusion list / nepomuk to avoid this strange behaviour ? -- 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 296564] kmail2 doesn't remember SMTP password
https://bugs.kde.org/show_bug.cgi?id=296564 --- Comment #5 from Laurent Montel mon...@kde.org --- And I think that you have just one smtp ? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #103 from nmset nm...@netcourrier.com --- As I posted before, disabling the cache in konqueror prevents the crash, not one single crash related to html mail. It's just a workaround, but a useful one ! Le vendredi 23 mars 2012 16:35:24 vous avez écrit : For the moment kcrash can't use valgrind but add all the time the same backtrace is not usefull, for me it's just increase number of email in my mailbox. We know that kmail crashs with this backtrace ok so why add same backtrace ? -- 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 244572] Message templates for new mails are not always used
https://bugs.kde.org/show_bug.cgi?id=244572 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Version Fixed In||4.8.2 Resolution|--- |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 296658] New: KMail crash when closing email
https://bugs.kde.org/show_bug.cgi?id=296658 Bug ID: 296658 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail crash when closing email Classification: Unclassified OS: Linux Reporter: codea...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-12-generic i686 Distribution: Linux Mint 12 Lisa -- Information about the crash: It's difficult for me to say exactly what caused the crash, but it appeared to happen either right after I closed an email that I was reading or when I clicked on another email to read it. Once in the Crash Reporting Assistant, I can't find a way to display my crash backtrace so I can compare it against others to see if there is a duplicate. I'll have to remember to copy it into another text editor in the future so I can do the comparison. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb76ea730 (LWP 25886))] Thread 6 (Thread 0xb5bdbb70 (LWP 25887)): #0 0x009a5416 in __kernel_vsyscall () #1 0x00bbba5c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0x007cf09c in __pthread_cond_wait (cond=0x3644430, mutex=0x3644418) at forward.c:139 #3 0x02f23883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0x02f2399f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x00bb7d31 in start_thread (arg=0xb5bdbb70) at pthread_create.c:304 #6 0x007c146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 5 (Thread 0xb52b2b70 (LWP 25888)): #0 0x009a5416 in __kernel_vsyscall () #1 0x007b27ae in __GI___poll (fds=0x9860a20, nfds=1, timeout=8412) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x06c6f34b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x06c60896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x06c60c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x073aa1c7 in QEventDispatcherGlib::processEvents (this=0x985f200, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x07375d1d in QEventLoop::processEvents (this=0xb52b22b0, flags=...) at kernel/qeventloop.cpp:149 #7 0x07375fb9 in QEventLoop::exec (this=0xb52b22b0, flags=...) at kernel/qeventloop.cpp:204 #8 0x0725f9dc in QThread::exec (this=0x985edd8) at thread/qthread.cpp:501 #9 0x0725facb in QThread::run (this=0x985edd8) at thread/qthread.cpp:568 #10 0x07262e70 in QThreadPrivate::start (arg=0x985edd8) at thread/qthread_unix.cpp:298 #11 0x00bb7d31 in start_thread (arg=0xb52b2b70) at pthread_create.c:304 #12 0x007c146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 4 (Thread 0xb30bdb70 (LWP 8646)): #0 0x009a5416 in __kernel_vsyscall () #1 0x00bbbe04 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:236 #2 0x007cf0f4 in __pthread_cond_timedwait (cond=0x9bf72d8, mutex=0x9bf72c0, abstime=0xb30bd288) at forward.c:152 #3 0x0726336f in wait (time=3, this=0x9bf72c0) at thread/qwaitcondition_unix.cpp:84 #4 QWaitCondition::wait (this=0x9bf7268, mutex=0x9bf7264, time=3) at thread/qwaitcondition_unix.cpp:158 #5 0x07255504 in QThreadPoolThread::run (this=0x9c02798) at concurrent/qthreadpool.cpp:141 #6 0x07262e70 in QThreadPrivate::start (arg=0x9c02798) at thread/qthread_unix.cpp:298 #7 0x00bb7d31 in start_thread (arg=0xb30bdb70) at pthread_create.c:304 #8 0x007c146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 3 (Thread 0xb23b5b70 (LWP 8649)): #0 0x009a5416 in __kernel_vsyscall () #1 0x00bbbe04 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:236 #2 0x007cf0f4 in __pthread_cond_timedwait (cond=0xc075878, mutex=0xc075860, abstime=0xb23b5288) at forward.c:152 #3 0x0726336f in wait (time=3, this=0xc075860) at thread/qwaitcondition_unix.cpp:84 #4 QWaitCondition::wait (this=0xc075830, mutex=0xc07582c, time=3) at thread/qwaitcondition_unix.cpp:158 #5 0x07255504 in QThreadPoolThread::run (this=0xb2655018) at concurrent/qthreadpool.cpp:141 #6 0x07262e70 in QThreadPrivate::start (arg=0xb2655018) at thread/qthread_unix.cpp:298 #7 0x00bb7d31 in start_thread (arg=0xb23b5b70) at pthread_create.c:304 #8 0x007c146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xae6ffb70 (LWP
[Bug 163573] Akregator crashed while clicking an article title
https://bugs.kde.org/show_bug.cgi?id=163573 Karl ka...@cox.net changed: What|Removed |Added CC||ka...@cox.net --- Comment #32 from Karl ka...@cox.net --- Possibly similar to bug 163573 though my crash was immediately after clicking on an Email button in order to share a news article with a friend. BuApplication: akregator (4.7.3) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-16-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: In detail, tell us what you were doing when the application crashed. I had just hit the Email button on a site page in order to send a copy of the article on Joba Chamberlin's ankle injury to a friend. Crash was immediate. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb779e730 (LWP 2622))] Thread 2 (Thread 0xb6cccb70 (LWP 2624)): #0 0x009852a8 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #1 0x0502a8bb in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x0502b637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x0502bf9b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x057b1cea in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #5 0x050525f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0x00864d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #7 0x0097746e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb779e730 (LWP 2622)): [KCrash Handler] #7 0x in ?? () #8 0x01f0e95f in ?? () from /usr/lib/libkhtml.so.5 #9 0x01f0f61e in ?? () from /usr/lib/libkhtml.so.5 #10 0x01e81521 in ?? () from /usr/lib/libkhtml.so.5 #11 0x01e20395 in ?? () from /usr/lib/libkhtml.so.5 #12 0x01e208bc in ?? () from /usr/lib/libkhtml.so.5 #13 0x01d6a254 in KHTMLView::dispatchMouseEvent(int, DOM::NodeImpl*, DOM::NodeImpl*, bool, int, QMouseEvent*, bool, int, int) () from /usr/lib/libkhtml.so.5 #14 0x01d6be39 in KHTMLView::mousePressEvent(QMouseEvent*) () from /usr/lib/libkhtml.so.5 #15 0x0110a454 in QWidget::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #16 0x0150f285 in QFrame::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #17 0x01d7352c in KHTMLView::widgetEvent(QEvent*) () from /usr/lib/libkhtml.so.5 #18 0x01d72bd3 in KHTMLView::eventFilter(QObject*, QEvent*) () from /usr/lib/libkhtml.so.5 #19 0x0543c336 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #20 0x010afd52 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #21 0x010b5deb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #22 0x0046e971 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #23 0x0543c19e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #24 0x010b0d45 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointerQWidget, bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #25 0x0113d304 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #26 0x0113be8d in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #27 0x0116828c in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #28 0x0502b25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #29 0x0502b990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #30 0x0502bc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #31 0x0546aada in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #32 0x01167e7a in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #33 0x0543b1dd in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #34 0x0543b421 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #35 0x0544019d in QCoreApplication::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #36 0x010ad924 in QApplication::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #37 0x0804e27f in ?? () #38 0x008bd113 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6 #39 0x0804e539 in _start () Report to https://bugs.kde.orgg report follows: -- 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
