[Bug 295010] Does not remember the smtp password
https://bugs.kde.org/show_bug.cgi?id=295010 --- Comment #5 from Albert Astals Cid 2012-03-02 18:34:31 --- I don't think so, i've got no "KWallet is not available. It is strongly recommended to use KWallet for managing your passwords." message -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286320] Message status corrupted when jump to first unread set
https://bugs.kde.org/show_bug.cgi?id=286320 --- Comment #5 from Laurent Montel 2012-03-02 17:28:52 --- *** Bug 295225 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295225] Crashes while reading e-mails
https://bugs.kde.org/show_bug.cgi?id=295225 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution||DUPLICATE --- Comment #1 from Laurent Montel 2012-03-02 17:28:52 --- *** This bug has been marked as a duplicate of bug 286320 *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295095] HTML display icons in header doesn't show up on some emails
https://bugs.kde.org/show_bug.cgi?id=295095 --- Comment #5 from2012-03-02 17:19:45 --- Created an attachment (id=69245) --> (http://bugs.kde.org/attachment.cgi?id=69245) Mail with the wanted icons for displaying either HTML or plain text Hmm, that's a shame. I rather like it :-) Just the way it should be... But had a second look at the one that shows icons and decided there is no secret info in there so it is attached. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295095] HTML display icons in header doesn't show up on some emails
https://bugs.kde.org/show_bug.cgi?id=295095 --- Comment #4 from Laurent Montel 2012-03-02 17:08:52 --- I don't know how you get icons in header. For all my html email I don't have it. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286320] Message status corrupted when jump to first unread set
https://bugs.kde.org/show_bug.cgi?id=286320 --- Comment #4 from Tony Eikelmann 2012-03-02 17:06:14 --- I dont think it is a bug in the filtering part. This will also happend when you are reading an e-mail as well. What is used is highlighting the e-mail and read it in the preview pan. Tony -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295214] Edits to Image attachments from the Kmail composer window are not saved
https://bugs.kde.org/show_bug.cgi?id=295214 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel 2012-03-02 16:59:42 --- I confirm it. don't know why it doesn't work. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295225] New: Crashes while reading e-mails
https://bugs.kde.org/show_bug.cgi?id=295225 Summary: Crashes while reading e-mails Product: kmail2 Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: eike...@philnor.net Application: kmail (4.7.4) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.8.0 Operating System: Linux 3.2.7-1.fc16.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: This will happend each I am trying to read an e-mail. sometimes immediatly or after reading 3-4 emails. I am using Fedora 16 -- 64 bit version The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), 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 0x7fb6e2ca4840 (LWP 32018))] Thread 6 (Thread 0x7fb6d679f700 (LWP 32022)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x00352f9b86ec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x353037cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x00352f9b8819 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003b4dc07d90 in start_thread (arg=0x7fb6d679f700) at pthread_create.c:309 #4 0x003b4d4f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 5 (Thread 0x7fb6d5e96700 (LWP 32023)): #0 0x003b4d4e85c3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0037a0444fd8 in ?? () from /lib64/libglib-2.0.so.0 #2 0x0037a044549c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x003521da7dc6 in QEventDispatcherGlib::processEvents (this=0x7fb6d8c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #4 0x003521d78182 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x003521d783d7 in QEventLoop::exec (this=0x7fb6d5e95d40, flags=...) at kernel/qeventloop.cpp:204 #6 0x003521c78b27 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x003521c7bb6b in QThreadPrivate::start (arg=0xf664f0) at thread/qthread_unix.cpp:298 #8 0x003b4dc07d90 in start_thread (arg=0x7fb6d5e96700) at pthread_create.c:309 #9 0x003b4d4f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 4 (Thread 0x7fb68e056700 (LWP 32046)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x003521c7bfdf in wait (time=3, this=0x7fb688005ee0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x7fb688005e88, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003521c6f5af in QThreadPoolThread::run (this=0x7fb688006130) at concurrent/qthreadpool.cpp:141 #4 0x003521c7bb6b in QThreadPrivate::start (arg=0x7fb688006130) at thread/qthread_unix.cpp:298 #5 0x003b4dc07d90 in start_thread (arg=0x7fb68e056700) at pthread_create.c:309 #6 0x003b4d4f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7fb68d855700 (LWP 32047)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x003521c7bfdf in wait (time=3, this=0x7fb688005ee0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x7fb688005e88, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003521c6f5af in QThreadPoolThread::run (this=0x7fb6880067a0) at concurrent/qthreadpool.cpp:141 #4 0x003521c7bb6b in QThreadPrivate::start (arg=0x7fb6880067a0) at thread/qthread_unix.cpp:298 #5 0x003b4dc07d90 in start_thread (arg=0x7fb68d855700) at pthread_create.c:309 #6 0x003b4d4f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7fb68cc4a700 (LWP 32048)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x003521c7bfdf in wait (time=3, this=0x7fb688005ee0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x7fb688005e88, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003521c6f5af in QThreadPoolThread::run (this=0x7fb68800e140) at concurrent/qthreadpool.cpp:141 #4 0x003521c7bb6b in QThreadPrivate::start (arg=0x7fb68800e140) at thread/qthread_unix.cpp:298 #5 0x003b4dc07d90 in start_thread (arg=0x7fb68cc4a700) at pthread_create.c:309 #6 0x003b4d4f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fb6e2ca4840 (LWP 32018)): [KCrash Handler] #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x120a9d0, hm=, sc=, rp=, pu=, db=, conte
[Bug 295218] New: KMail freezes when GPG doesn't respond
https://bugs.kde.org/show_bug.cgi?id=295218 Summary: KMail freezes when GPG doesn't respond Product: kmail2 Version: 4.8 Platform: Gentoo Packages OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: crypto AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@eliasprobst.eu I've experienced KMail freezes multiple times which have been related to GnuPG not responding/waiting for a timeout etc. Such operations should be done in a separate thread or so, as it renders the whole KMail GUI unusable as nothing can be done at all until the timeout is reached, which might take up to 5 minutes in some cases (e.g. keyserver cannot be reached). Using KDE 4.8.0 an GnuPG 2.0.17. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295217] New: KMail renders GPG error message into mail body
https://bugs.kde.org/show_bug.cgi?id=295217 Summary: KMail renders GPG error message into mail body Product: kmail2 Version: 4.8 Platform: Unlisted Binaries OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: crypto AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@eliasprobst.eu Created an attachment (id=69241) --> (http://bugs.kde.org/attachment.cgi?id=69241) Screenshot showing the GPG error message rendered into the mail body I had issues with GnuPG not being able to connect to a keyserver. The resulting error message was rendered into the message body of the signed mail instead of being displayed in the header where the signature information is shown or as an separate error dialog box. See the screenshot. The raw view of the mail looked correct, so I don't mistake this for an error message already being rendered into the original mail itself. Using KDE 4.8.0 and GnuPG 2.0.17. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295216] New: Kontact crashes on Forward Inline
https://bugs.kde.org/show_bug.cgi?id=295216 Summary: Kontact crashes on Forward Inline Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: gkour...@gmail.com Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 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: After starting Kontact I open any message (no matter new in inbox or old in other file folders). As soon as I hold the Forward button and go to Inline option, Kontact crashes. After reloading it, the new message is there opened in a separate window but formatted in one narrow coloumn. This can be reproduced every time. Steps to do that: 1. Start Kontact. 2. Open any message. 3. Press and hold Forward button from the task bar. 4. Go to option Inline. 5. Kontact crashes. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb785a730 (LWP 2382))] Thread 4 (Thread 0xb5dc3b70 (LWP 2383)): #0 0x004d2416 in __kernel_vsyscall () #1 0x05dd5a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x00905cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0x022a9883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0x022a999f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x05dd1d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x008f80ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 3 (Thread 0xb549ab70 (LWP 2384)): #0 0x004d2416 in __kernel_vsyscall () #1 0x008e940e in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0x02f1034b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x02f01896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x02f01c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x006821c7 in QEventDispatcherGlib::processEvents (this=0x95636e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x0064dd1d in QEventLoop::processEvents (this=0xb549a2b0, flags=...) at kernel/qeventloop.cpp:149 #7 0x0064dfb9 in QEventLoop::exec (this=0xb549a2b0, flags=...) at kernel/qeventloop.cpp:204 #8 0x005379dc in QThread::exec (this=0x95b27b8) at thread/qthread.cpp:501 #9 0x00537acb in QThread::run (this=0x95b27b8) at thread/qthread.cpp:568 #10 0x0053ae70 in QThreadPrivate::start (arg=0x95b27b8) at thread/qthread_unix.cpp:298 #11 0x05dd1d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x008f80ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xb3712b70 (LWP 2433)): #0 0x05dd3dc6 in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0 #1 0x00905f14 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #2 0x02f00f53 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x02f018f0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x02f01c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x006821c7 in QEventDispatcherGlib::processEvents (this=0x9e85210, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x0064dd1d in QEventLoop::processEvents (this=0xb3712280, flags=...) at kernel/qeventloop.cpp:149 #7 0x0064dfb9 in QEventLoop::exec (this=0xb3712280, flags=...) at kernel/qeventloop.cpp:204 #8 0x005379dc in QThread::exec (this=0x9e84ee8) at thread/qthread.cpp:501 #9 0x0062b2dd in QInotifyFileSystemWatcherEngine::run (this=0x9e84ee8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x0053ae70 in QThreadPrivate::start (arg=0x9e84ee8) at thread/qthread_unix.cpp:298 #11 0x05dd1d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x008f80ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb785a730 (LWP 2382)): [KCrash Handler] #7 0x07368b51 in QTextLine::cursorToX (this=0xbfc584a0, cursorPos=0xbfc584b8, edge=QTextLine::Leading) at text/qtextlayout.cpp:2511 #8 0x07343dba in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=0xbfc584a0) at ../../include/QtGui/../../src/gui/text/qtextlayout.h:230 #9 QTextControlPrivate::rectForPosition (this=0xb66c268, position=634) at text/qtextcontrol.cpp:1368 #10 0x07347f00 in QTextControl::ensureCursorVisible (this=0xb66c258) at text/qtextcontrol.cpp:2950 #11 0x0734c14d in QTextControl::setTextCursor (this=0xb66c258, cursor=...) at text/qtextcontrol.cpp:833 #12 0x075b6a7c in QTextEdit::setTextCursor (this=0xb3440a8, cursor=...) at widgets/qt
[Bug 259963] Wrong context menu in middle column
https://bugs.kde.org/show_bug.cgi?id=259963 Jonathan Marten changed: What|Removed |Added Status|NEW |RESOLVED Version Fixed In||4.9 Resolution||FIXED --- Comment #3 from Jonathan Marten 2012-03-02 15:25:04 --- Git commit f78438b6357c12803fdc976881339f25d98c47ea by Jonathan Marten. Committed on 02/03/2012 at 16:22. Pushed by marten into branch 'master'. Pop up the correct context menu over blank space in the middle column FIXED-IN:4.9 M +1-0kaddressbook/mainwidget.cpp http://commits.kde.org/kdepim/f78438b6357c12803fdc976881339f25d98c47ea -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259963] Wrong context menu in middle column
https://bugs.kde.org/show_bug.cgi?id=259963 --- Comment #2 from Jonathan Marten 2012-03-02 15:14:16 --- Git commit 24b0160e9497d3947726ec4185409c8205633cdc by Jonathan Marten. Committed on 02/03/2012 at 16:11. Pushed by marten into branch 'master'. Add EntityTreeView::setDefaultPopupMenu() Allows the context menu to be specified which is popped up when not over an entry (e.g. blank space) in the view. Over an entry, the type of the entry determines the menu as before. REVIEW:104132 FIXED-IN:4.9 M +16 -9akonadi/entitytreeview.cpp M +19 -0akonadi/entitytreeview.h http://commits.kde.org/kdepimlibs/24b0160e9497d3947726ec4185409c8205633cdc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295214] New: Edits to Image attachments from the Kmail composer window are not saved
https://bugs.kde.org/show_bug.cgi?id=295214 Summary: Edits to Image attachments from the Kmail composer window are not saved Product: kmail2 Version: 4.8 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer AssignedTo: kdepim-bugs@kde.org ReportedBy: p...@basilisk.ukfsn.org Version: 4.8 (using KDE 4.8.0) OS:Linux When composing an email with an image attatchment, if I edit the image, save and close, then re-open the image, the original pre-edit image is shown. Reproducible: Always Steps to Reproduce: 1. Start a new message in Kmail and attach an image file (PNG or JPEG) 2. Right-click the attachment and choose Edit. (Image file opens in Gwenview) 3. Make a change to the image in Gwenview (e.g. Flip the image) 4. Save and close the image 5. Re-open the attachment from the Kmail composer window Actual Results: The original image opens. Expected Results: The changed image opens Editing OpenOffice files and plain text files (using Kate) works as expected -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #78 from steve 2012-03-02 14:10:11 --- The bug is severe enough for me to be greatly hindered in using Kmail for my business, which I've been doing for years now. It is too much to hand select emails from 1500 clients. So yesterday I wiped my drive and installed Kubuntu 11.10 fresh. I went ahead and let it perform the first set of updates suggested by the system. I believe this updated from 4.7.3 to 4.7.4. I created a new personal contact book using akonadi, and populated it with Vcard import in Kontact. Autocomplete works flawlessly now. It seems something breaks in either Nepomuk feeder or Akonadi when upgrading to a new 'decade' of KDE. I am witholding implementing anymore system updates for now because this is a feature of Kmail I must have. I spent quite a while searching around for clues and found many people experiencing this bug who have yet to report it. I consider it a major bug. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295211] New: possibility to lock message list columns
https://bugs.kde.org/show_bug.cgi?id=295211 Summary: possibility to lock message list columns Product: kmail2 Version: 4.8 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: message list AssignedTo: kdepim-bugs@kde.org ReportedBy: silver.salo...@gmail.com Version: 4.8 (using KDE 4.8.0) OS:Linux I sometimes miss a correct spot when clicking with mouse, so I accidentally change sorting of the message list. As bug 227516 is still existent, it's especially annoying as for me it isn't just enough to click on another column to re-sort messages the way they were before - for an instance I have to first re-make visible the Sender-column, adjust the columns' sizes to the previous state and then go: Right click -> Sorting -> By Date/Time of Most Recent in Subtree. Reproducible: Always Steps to Reproduce: Click on column headers Actual Results: Messages get re-sorted by the column clicked on Expected Results: It would be nice if it was possible to lock the columns (eg. like it's possible to lock toolbars), so that it wouldn't be possible to re-sort messages, change the order of columns, resize columns etc. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293649] The openXchange resource interprets the birthday wrong
https://bugs.kde.org/show_bug.cgi?id=293649 --- Comment #4 from Allen Winter 2012-03-02 13:40:42 --- hmmm, I don't see the backport of this fix into the 4.8 branch -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293649] The openXchange resource interprets the birthday wrong
https://bugs.kde.org/show_bug.cgi?id=293649 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #3 from Allen Winter 2012-03-02 13:39:46 --- can we resolve this one now? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295204] Allow to store templates in Kwallet
https://bugs.kde.org/show_bug.cgi?id=295204 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution||WONTFIX --- Comment #1 from Laurent Montel 2012-03-02 13:27:49 --- No I will not add it in kwallet. Otherwise we can add all data in kwallet as account config for example :) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295205] Crash on calendar
https://bugs.kde.org/show_bug.cgi?id=295205 --- Comment #1 from Kevin Krammer 2012-03-02 12:45:51 --- Thanks for the report. Can you check https://bugs.kde.org/show_bug.cgi?id=294486#c4 for me as well? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295205] New: Crash on calendar
https://bugs.kde.org/show_bug.cgi?id=295205 Summary: Crash on calendar Product: Akonadi Version: 4.7 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: KResource compat bridges AssignedTo: kevin.kram...@gmx.at ReportedBy: overs...@gmail.com CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_kcal_resource (4.7) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.8.0 Operating System: Linux 3.2.7-1.fc16.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: I wasn't doing nothing in kontact (was using konsole) and i've received the crash. The crash can be reproduced some of the time. -- Backtrace: Application: Suporte of type KDE Calendar (traditional) (akonadi_kcal_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x00335b051cb4 in KCal::Incidence::relatedTo (this=0x43db080) at /usr/src/debug/kdepimlibs-4.7.4/kcal/incidence.cpp:518 #7 0x00335b0532c2 in KCal::Incidence::~Incidence (this=0xbf3140, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/kcal/incidence.cpp:201 #8 0x00335b0597e9 in KCal::Event::~Event (this=0xbf3140, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/kcal/event.cpp:79 #9 0x0041253a in release (this=0x41c3310) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:145 #10 ~shared_count (this=0x1a23400, __in_chrg=) at /usr/include/boost/smart_ptr/detail/shared_count.hpp:305 #11 ~shared_ptr (this=0x1a233f8, __in_chrg=) at /usr/include/boost/smart_ptr/shared_ptr.hpp:164 #12 ~Payload (this=0x1a233f0, __in_chrg=) at /usr/include/kde4/akonadi/itempayloadinternals_p.h:285 #13 Akonadi::Payload >::~Payload (this=0x1a233f0, __in_chrg=) at /usr/include/kde4/akonadi/itempayloadinternals_p.h:285 #14 0x00336831b1e6 in ~clone_ptr (this=0x3426360, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/item_p.h:48 #15 ~TypedPayload (this=0x3426360, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/item_p.h:119 #16 _Destroy (__pointer=0x3426360) at /usr/include/c++/4.6.2/bits/stl_construct.h:94 #17 __destroy (__last=0x3426370, __first=) at /usr/include/c++/4.6.2/bits/stl_construct.h:104 #18 _Destroy (__last=0x3426370, __first=) at /usr/include/c++/4.6.2/bits/stl_construct.h:127 #19 _Destroy (__last=0x3426370, __first=) at /usr/include/c++/4.6.2/bits/stl_construct.h:153 #20 ~vector (this=0x1a4d858, __in_chrg=) at /usr/include/c++/4.6.2/bits/stl_vector.h:350 #21 ~ItemPrivate (this=0x1a4d810, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/item_p.h:203 #22 Akonadi::ItemPrivate::~ItemPrivate (this=0x1a4d810, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/item_p.h:204 #23 0x00336827e57c in node_destruct (to=0x1a239e8, from=0x1a239e8, this=) at /usr/include/QtCore/qlist.h:431 #24 QList::free (this=, data=0x1a239d0) at /usr/include/QtCore/qlist.h:757 #25 0x003368332040 in ~ItemModifyJobPrivate (this=0x1a51a30, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/itemmodifyjob_p.h:30 #26 Akonadi::ItemModifyJobPrivate::~ItemModifyJobPrivate (this=0x1a51a30, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/itemmodifyjob_p.h:30 #27 0x003368336299 in Akonadi::Job::~Job (this=0x1a22ca0, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/job.cpp:254 #28 0x00336832e249 in Akonadi::ItemModifyJob::~ItemModifyJob (this=0x1a22ca0, __in_chrg=) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/itemmodifyjob.cpp:134 #29 0x003352591f48 in QObject::event (this=0x1a22ca0, e=) at kernel/qobject.cpp:1176 #30 0x003354dc9994 in notify_helper (e=0x4416b50, receiver=0x1a22ca0, this=0xa99e90) at kernel/qapplication.cpp:4550 #31 QApplicationPrivate::notify_helper (this=0xa99e90, receiver=0x1a22ca0, e=0x4416b50) at kernel/qapplication.cpp:4522 #32 0x003354dce813 in QApplication::notify (this=0x7fff431d15b0, receiver=0x1a22ca0, e=0x4416b50) at kernel/qapplication.cpp:4411 #33 0x003356c50766 in KApplication::notify (this=0x7fff431d15b0, receiver=0x1a22ca0, event=0x4416b50) at /usr/src/debug/kdelibs-4.7.4/kdeui/kernel/kapplication.cpp:311 #34 0x00335257904c in QCoreApplication::notifyInternal (this=0x7fff431d15b0, receiver=0x1a22ca0, event=0x4416b50) at kernel/qcoreapplication.cpp:876 #35 0x00335257cada in sendEvent (event=0x4416b50, receiver=0x1a22ca0) at kernel/qcoreapplication.h:231 #36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xa6c2e0) at kernel/qcoreapplication.cpp:1500 #37 0x0033525a7933 in sendPostedEvents () at kernel/qcoreapplication.h:236 #38 postEventSourceDispatch (s=0xa9da20) at kernel/qeventdispatcher_glib.cpp:279 #39 0x003346c44acd in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #40 0x003346c452c8 in ?? () from /lib64/libglib-2.0.so
[Bug 294623] akonadi-google google tasks are sent as top-level tasks always
https://bugs.kde.org/show_bug.cgi?id=294623 --- Comment #1 from Theo Chatzimichos 2012-03-02 12:13:28 --- According to http://www.progdan.cz/2011/09/akonadi-google-resource-tasks-support/ the bug is already known -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295204] New: Allow to store templates in Kwallet
https://bugs.kde.org/show_bug.cgi?id=295204 Summary: Allow to store templates in Kwallet Product: kmail2 Version: 1.99.0 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: composer AssignedTo: kdepim-bugs@kde.org ReportedBy: m.w...@web.de Version: 1.99.0 (using KDE 4.8.0) OS:Linux I use the templates (German: Textbausteine) partly for personal data, like account numbers, customer numbers and so on. Therefor it would be good, if Kmail would allow to store this information encrypted in Kwallet. Reproducible: Always Steps to Reproduce: see above Actual Results: see above Expected Results: see above OS: Linux (x86_64) release 3.2.0-17-generic Compiler: gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295203] New: akonadi crash after login - duplicate
https://bugs.kde.org/show_bug.cgi?id=295203 Summary: akonadi crash after login - duplicate Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Nepomuk Feeder Agents AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@wehrwein.de CC: vkra...@kde.org Application: akonadi_nepomuk_contact_feeder (0.1) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.2 Operating System: Linux 2.6.32-38-generic i686 Distribution: Ubuntu 10.04.4 LTS -- Information about the crash: running ksycoca4 --noincremental is not a solution. The crash can be reproduced some of the time. -- Backtrace: Application: Akonadi Agent (akonadi_nepomuk_contact_feeder), signal: Segmentation fault [KCrash Handler] #6 0x0030e126 in KMimeType::mimeType (_name=..., options=KMimeType::ResolveAliases) at ../../kdecore/services/kmimetype.cpp:159 #7 0x00a86db7 in Akonadi::MonitorPrivate::isMimeTypeMonitored (this=0x9e00160, msg=...) at ../../akonadi/monitor_p.h:200 #8 Akonadi::MonitorPrivate::isItemMonitored (this=0x9e00160, msg=...) at ../../akonadi/monitor_p.h:82 #9 Akonadi::MonitorPrivate::acceptNotification (this=0x9e00160, msg=...) at ../../akonadi/monitor_p.cpp:141 #10 0x00a87a27 in Akonadi::MonitorPrivate::slotNotify (this=0x9e00160, msgs=...) at ../../akonadi/monitor_p.cpp:287 #11 0x009f684e in Akonadi::ChangeRecorderPrivate::slotNotify(QList const&) () from /usr/lib/libakonadi-kde.so.4 #12 0x00a82ae0 in Akonadi::Monitor::qt_metacall (this=0x9e00238, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0xbf83e908) at ./monitor.moc:147 #13 0x009f398a in Akonadi::ChangeRecorder::qt_metacall (this=0x9e00238, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0xbf83e908) at ./changerecorder.moc:72 #14 0x00ca4c9a in QMetaObject::metacall (object=0x9e00238, cl=3213092608, idx=24, argv=0xbf83e908) at kernel/qmetaobject.cpp:237 #15 0x00cb33d5 in QMetaObject::activate (sender=0x9e00858, m=0xb34828, local_signal_index=0, argv=0xbf83e908) at kernel/qobject.cpp:3293 #16 0x00ad42b3 in OrgFreedesktopAkonadiNotificationManagerInterface::notify (this=0x9e00858, _t1=...) at notificationmanagerinterface.moc:85 #17 0x00ad431b in OrgFreedesktopAkonadiNotificationManagerInterface::qt_metacall (this=0x9e00858, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf83ea6c) at notificationmanagerinterface.moc:73 #18 0x00149b34 in QDBusConnectionPrivate::deliverCall (this=0x9d3ec40, object=0x9e00858, msg=..., metaTypes=..., slotIdx=5) at qdbusintegrator.cpp:904 #19 0x00154ea7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x9e5c9c0, object=0x9e00858) at qdbusintegrator_p.h:101 #20 0x00cb03fe in QObject::event (this=0x9e00858, e=0x9e5c9c0) at kernel/qobject.cpp:1248 #21 0x0116a4dc in QApplicationPrivate::notify_helper (this=0x9d0cdb8, receiver=0x9e00858, e=0x9e5c9c0) at kernel/qapplication.cpp:4300 #22 0x0117105e in QApplication::notify (this=0xbf83f340, receiver=0x9e00858, e=0x9e5c9c0) at kernel/qapplication.cpp:3704 #23 0x0073e40a in KApplication::notify (this=0xbf83f340, receiver=0x9e00858, event=0x9e5c9c0) at ../../kdeui/kernel/kapplication.cpp:302 #24 0x00c9fa3b in QCoreApplication::notifyInternal (this=0xbf83f340, receiver=0x9e00858, event=0x9e5c9c0) at kernel/qcoreapplication.cpp:704 #25 0x00ca2473 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9cf8fe8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9cf8fe8) at kernel/qcoreapplication.cpp:1345 #27 0x00ca25dd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #28 0x00ccbadf in QCoreApplication::sendPostedEvents (s=0x9d0f110) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #29 postEventSourceDispatch (s=0x9d0f110) at kernel/qeventdispatcher_glib.cpp:276 #30 0x01c4b5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #31 0x01c4f2d8 in ?? () from /lib/libglib-2.0.so.0 #32 0x01c4f4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #33 0x00ccb5d5 in QEventDispatcherGlib::processEvents (this=0x9cf8b80, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #34 0x0122a135 in QGuiEventDispatcherGlib::processEvents (this=0x9cf8b80, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #35 0x00c9e059 in QEventLoop::processEvents (this=0xbf83f294, flags=) at kernel/qeventloop.cpp:149 #36 0x00c9e4aa in QEventLoop::exec (this=0xbf83f294, flags=...) at kernel/qeventloop.cpp:201 #37 0x00ca269f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #38 0x0116a577 in QApplication::exec () at kernel/qapplication.cpp:3579 #39 0x009d5868 in Akonadi::AgentBase::init (r=0x9ddb208) at ../../akonadi/agentbase.cpp:496 #40 0x0804efc3 in _start () This bug may be a duplicate of or related to bug 240981. Possible dupl
[Bug 295200] New: Kontact crash open HTML e-mail
https://bugs.kde.org/show_bug.cgi?id=295200 Summary: Kontact crash open HTML e-mail Product: kontact Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: fons...@gmail.com Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 "release 5" Qt Version: 4.8.0 Operating System: Linux 3.1.9-1.4-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was deleting a HTML e-mail with images (external references). When Kmail shows the e-mail in 10-15 seconds crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f7fe4355760 (LWP 31084))] Thread 9 (Thread 0x7f7fcb0cc700 (LWP 31085)): #0 0x7f7fdc1f0e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7fe0b7cc12 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f7fe0b7cc49 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f7fdc1ecf05 in start_thread () from /lib64/libpthread.so.0 #4 0x7f7fe186c63d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f7fca7b3700 (LWP 31086)): #0 0x7f7fe1863523 in poll () from /lib64/libc.so.6 #1 0x7f7fdbcdda98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7fdbcddf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7fe1fda956 in QEventDispatcherGlib::processEvents (this=0x7f7fc40008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f7fe1faa682 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f7fe1faa8d7 in QEventLoop::exec (this=0x7f7fca7b2e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f7fe1eab537 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f7fe1eae55b in QThreadPrivate::start (arg=0x820840) at thread/qthread_unix.cpp:298 #8 0x7f7fdc1ecf05 in start_thread () from /lib64/libpthread.so.0 #9 0x7f7fe186c63d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f7f77788700 (LWP 31125)): #0 0x7f7fdc1f11eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7fe1eae9cf in wait (time=3, this=0xeaa410) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x18900d8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f7fe1ea1ddf in QThreadPoolThread::run (this=0x1ae4350) at concurrent/qthreadpool.cpp:141 #4 0x7f7fe1eae55b in QThreadPrivate::start (arg=0x1ae4350) at thread/qthread_unix.cpp:298 #5 0x7f7fdc1ecf05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f7fe186c63d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f7f7cfdb700 (LWP 31149)): #0 0x7f7fdc1f11eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7fe1eae9cf in wait (time=3, this=0xcd2be0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0xcd2b88, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f7fe1ea1ddf in QThreadPoolThread::run (this=0xce6000) at concurrent/qthreadpool.cpp:141 #4 0x7f7fe1eae55b in QThreadPrivate::start (arg=0xce6000) at thread/qthread_unix.cpp:298 #5 0x7f7fdc1ecf05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f7fe186c63d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f7f74b01700 (LWP 31152)): #0 0x7f7fdc1f11eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7fe1eae9cf in wait (time=3, this=0x7f7f680060f0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x7f7f68006098, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f7fe1ea1ddf in QThreadPoolThread::run (this=0x7f7f68006340) at concurrent/qthreadpool.cpp:141 #4 0x7f7fe1eae55b in QThreadPrivate::start (arg=0x7f7f68006340) at thread/qthread_unix.cpp:298 #5 0x7f7fdc1ecf05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f7fe186c63d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f7f67fff700 (LWP 31153)): #0 0x7f7fdc1f11eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7fe1eae9cf in wait (time=3, this=0x7f7f680060f0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x7f7f68006098, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f7fe1ea1ddf in QThreadPoolThread::run (this=0x7f7f6800b9b0) at concurrent/qthreadpool.cpp:141 #4 0x7f7fe1eae55b in QThreadPrivate::start (arg=0x7f7f6800b9b0) at thread/qthread_unix.cpp:298 #5 0x7f7fdc1ecf05 in start_thread () from /lib64/libpthread.so.0 #6 0x7f7fe186c63d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f7f677fe700 (LWP 31156)): #0 0x7f7fdc1f11eb in pthread_cond_ti
[Bug 294441] kmail stays in offline mode, unable to send emails
https://bugs.kde.org/show_bug.cgi?id=294441 --- Comment #14 from wazyk 2012-03-02 09:15:25 --- (In reply to comment #9) > I even think the problem might be in "Hardware Integration Configuration with > Solid" (System settings -> Information sources). The network management > backend > does not correctly report the online status. Even when I start Kopete it > starts > in offline mode, even though I've set initial status as 'online'. Obviously it > detects that system is offline in the same way kmail detects that, and that is > through information sources or Solid... > > So I think this bug is not necessarily a bug in kmail, but a bug in system > settings/information sources->network management backend (i.e. Solid). When running: qdbus --system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.state I get result 70, which is correct value returned by NetworkManager given these specs : http://projects.gnome.org/NetworkManager/developers/api/09/spec.html#type-NM_STATE When running: qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status I get value 1 which is not good. Value 4 is expected. So I agree with Nena, Solid's network status is not correctly updated by NetworkManager, once the latter gets connected after kde has started. I'd suspect kded_networkstatus to be the problem ... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295193] New: Kontact crash on startup
https://bugs.kde.org/show_bug.cgi?id=295193 Summary: Kontact crash on startup Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: tsdg...@terra.es Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 Qt Version: 4.8.0 Operating System: Linux 3.2.0-17-generic x86_64 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: Started Kontact, then it crashed, have not been able to make it crash starting it again -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 [Current thread is 1 (Thread 0x7fb79e3507c0 (LWP 2296))] Thread 5 (Thread 0x7fb780e18700 (LWP 2307)): #0 0x7fb79b88234d in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fb795b9672f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb795b5bbfd in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb795b5c0d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb795b5c59a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb786584446 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7fb795b7d7d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fb796027e9a in start_thread (arg=0x7fb780e18700) at pthread_create.c:308 #8 0x7fb79b88f74d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 4 (Thread 0x7fb773b94700 (LWP 2321)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fb79ab5fddc in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb79ab5ff09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb796027e9a in start_thread (arg=0x7fb773b94700) at pthread_create.c:308 #4 0x7fb79b88f74d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7fb773293700 (LWP 2335)): #0 0x7fb79b883d93 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fb795b5c136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb795b5c264 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb79c003a76 in QEventDispatcherGlib::processEvents (this=0x7fb76c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fb79bfd32d2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fb79bfd3527 in QEventLoop::exec (this=0x7fb773292dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fb79bed2f97 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7fb79bed5fbb in QThreadPrivate::start (arg=0x8daf70) at thread/qthread_unix.cpp:298 #8 0x7fb796027e9a in start_thread (arg=0x7fb773293700) at pthread_create.c:308 #9 0x7fb79b88f74d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7fb719048700 (LWP 2583)): [KCrash Handler] #6 QMutex::lock (this=0x650072006361c8) at thread/qmutex.cpp:150 #7 0x7fb78fbf66a2 in lockInline (this=) at /usr/include/qt4/QtCore/qmutex.h:198 #8 QMutexLocker (m=, this=0x7fb719047450) at /usr/include/qt4/QtCore/qmutex.h:109 #9 Soprano::Error::ErrorCache::clearError (this=0x1e97880) at ../../soprano/error.cpp:238 #10 0x7fb78fbf6c58 in Soprano::Error::ErrorCache::setError (this=0x1e97880, error=...) at ../../soprano/error.cpp:225 #11 0x7fb78f98e10c in Soprano::Client::DBusModel::executeQuery (this=0x1e97870, query=..., language=, userQueryLanguage=...) at ../../client/dbus/dbusmodel.cpp:112 #12 0x7fb7941071dc in Nepomuk::MainModel::executeQuery (this=0x10112c0, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212 #13 0x7fb78fc063e7 in Soprano::FilterModel::executeQuery (this=0x1015000, query=..., language=, userQueryLanguage=...) at ../../soprano/filtermodel.cpp:164 #14 0x7fb7940fe257 in Nepomuk::ResourceData::load (this=0x7fb714001bd0) at ../../nepomuk/core/resourcedata.cpp:381 #15 0x7fb7940fea6c in Nepomuk::ResourceData::property (this=0x7fb714001bd0, uri=...) at ../../nepomuk/core/resourcedata.cpp:240 #16 0x7fb794112503 in Nepomuk::Resource::property (this=0x7fb719047cc0, uri=...) at ../../nepomuk/core/resource.cpp:301 #17 0x7fb71e6e5c5a in ?? () from /usr/lib/libmessagecore.so.4 #18 0x7fb79bec94e2 in QThreadPoolThread::run (this=0x17baf30) at concurrent/qthreadpool.cpp:107 #19 0x7fb79
