[kmail2] [Bug 483416] mixed folder icons colors in dark mode
https://bugs.kde.org/show_bug.cgi?id=483416 --- Comment #3 from Piotr Keplicz --- The solution was to install a proper version of plasma-integration, apparently apt didn't upgrade it to 6.0.2. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483416] mixed folder icons colors in dark mode
https://bugs.kde.org/show_bug.cgi?id=483416 Piotr Keplicz changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Piotr Keplicz --- It's likely to be a configuration problem on my machine, other theme settings don't fully work so it may be related. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 483416] New: mixed folder icons colors in dark mode
https://bugs.kde.org/show_bug.cgi?id=483416 Bug ID: 483416 Summary: mixed folder icons colors in dark mode Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: kepl...@cmc.pl Target Milestone: --- Created attachment 167086 --> https://bugs.kde.org/attachment.cgi?id=167086=edit folders list SUMMARY When using dark Plasma theme (Breeze Dark), some folder icons are light, some are dark. STEPS TO REPRODUCE 1. Switch to Plasma Breeze Dark theme OBSERVED RESULT Folder icons have mixed colors. EXPECTED RESULT Folder icons should have the same, light color on dark background as defined by the color scheme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon KDE Plasma Version: 6.0.2 Qt Version: 6.6 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 482352] New: I cannot send emails by gmail
https://bugs.kde.org/show_bug.cgi?id=482352 Bug ID: 482352 Summary: I cannot send emails by gmail Classification: Applications Product: kmail2 Version: Git (master) Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY When I try to send any email via my gmail account I get following: message: "Failed to transport message. SASL(-4): no mechanism available: No worthy mechs found " Authentication method in my account (IMAP) is “XOAuth”. And packages which are installed: $ dpkg -l | grep -i sasl ii libauthen-sasl-perl 2.1600-1.1 all Authen::SASL - SASL Authentication framework ii libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2 amd64 Cyrus SASL - authentication abstraction library ii libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2 amd64 Cyrus SASL - pluggable authentication modules ii libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2 amd64 Cyrus SASL - pluggable authentication modules (DB) ii libsasl2-modules-kdexoauth2 23.08.4+p22.04+vunstable+git20240220.1020-0 all Dummy transitional STEPS TO REPRODUCE 1. Start KMail 2. Click "New" 3. Fill all required fields 4. Click "Send" OBSERVED RESULT Reports error like: ""Failed to transport message. SASL(-4): no mechanism available: No worthy mechs found " EXPECTED RESULT Possibility to send email SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I use Neon Unstable Edition I reported issue here, but no reply: https://discuss.kde.org/t/kmail-receives-emails-but-wont-send-emails/328 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 470788] KMail. Tree with folder structure scrolls on top when try to drop email on any folder
https://bugs.kde.org/show_bug.cgi?id=470788 Piotr Mierzwinski changed: What|Removed |Added Summary|Tree with folder structure |KMail. Tree with folder |scrolls on top when try to |structure scrolls on top |drop email on any folder|when try to drop email on ||any folder CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473615] New: Crash after moving email
https://bugs.kde.org/show_bug.cgi?id=473615 Bug ID: 473615 Summary: Crash after moving email Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: piotr.mierzwin...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.24.40 (23.11.40)) Qt Version: 6.6.0 Frameworks Version: 5.240.0 Operating System: Linux 6.2.0-26-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.27.80 [CoredumpBackend] -- Information about the crash: I just moved email from one folder to another. In result appeared crash. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/11/bits/atomic_base.h:486 #7 QAtomicOps::loadRelaxed (_q_value=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #8 QBasicAtomicInteger::loadRelaxed (this=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 [...] #10 QByteArray::QByteArray (a=..., this=0x7f2d9d7f93e0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbytearray.h:525 #11 Akonadi::Protocol::PartMetaData::PartMetaData (this=0x7f2d9d7f93e0) at ./obj-x86_64-linux-gnu/src/private/protocol_gen.h:171 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473615] Crash after moving email in KMail
https://bugs.kde.org/show_bug.cgi?id=473615 Piotr Mierzwinski changed: What|Removed |Added Summary|Crash after moving email|Crash after moving email in ||KMail CC||piotr.mierzwin...@gmail.com Keywords||qt6, wayland -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473615] Crash after moving email
https://bugs.kde.org/show_bug.cgi?id=473615 --- Comment #1 from Piotr Mierzwinski --- Created attachment 161099 --> https://bugs.kde.org/attachment.cgi?id=161099=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472861] Crash after click onto folders in Kmail
https://bugs.kde.org/show_bug.cgi?id=472861 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Keywords||wayland -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472861] Crash after click onto folders in Kmail
https://bugs.kde.org/show_bug.cgi?id=472861 --- Comment #1 from Piotr Mierzwinski --- Created attachment 160659 --> https://bugs.kde.org/attachment.cgi?id=160659=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 472861] New: Crash after click onto folders in Kmail
https://bugs.kde.org/show_bug.cgi?id=472861 Bug ID: 472861 Summary: Crash after click onto folders in Kmail Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: piotr.mierzwin...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.24.40 (23.11.40)) Qt Version: 6.6.0 Frameworks Version: 5.240.0 Operating System: Linux 5.19.0-50-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.27.80 [CoredumpBackend] -- Information about the crash: I clicked onto folders in KMail. I have 2 email boxes. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140594462582336) at ./nptl/pthread_kill.c:44 #7 __pthread_kill_internal (signo=6, threadid=140594462582336) at ./nptl/pthread_kill.c:78 #8 __GI___pthread_kill (threadid=140594462582336, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #9 0x7fdebc842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #10 0x7fdebc8287f3 in __GI_abort () at ./stdlib/abort.c:79 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 470788] New: Tree with folder structure scrolls on top when try to drop email on any folder
https://bugs.kde.org/show_bug.cgi?id=470788 Bug ID: 470788 Summary: Tree with folder structure scrolls on top when try to drop email on any folder Classification: Applications Product: kmail2 Version: Git (master) Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY I have two mailboxes configured in KMail. Iniside of them I have several folders and all of them are unfolded, so I need to scroll to reach folder from second mailbox. I scrolled tree to bottom and tried to move message to given folder, also at bottom unfortunately when I dragged message onto the tree then it scrolled automatically on top. When dragged message on very bottom to force scrolling in opposite happened nothing. In result I cannot move message this way. BTW. I cannot also move message by context menu because when I select last option (non local folder) the it immediately disappears. I will report separated bug report for this. STEPS TO REPRODUCE 1. add two mailboxes with several folders 2. unfold all folders in both mailboxes 3. scroll to bottom and try to move any message by drag and drop OBSERVED RESULT the tree scrolls on top automatically EXPECTED RESULT the tree should not scroll on top automatically SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.0 Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 465926] New: Possibility to go from notification into email in application
https://bugs.kde.org/show_bug.cgi?id=465926 Bug ID: 465926 Summary: Possibility to go from notification into email in application Classification: Applications Product: kmail2 Version: Git (master) Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY Would be nice to have possibility to go from notification about new email arrived into application where this not read yet email would be opened. Just to see whole this message. STEPS TO REPRODUCE 1. Arrives new notification or we look at the past notifications about arrived emails 2. We click into this email or button "View" placed on notification (similar it happens in Discover) 3. Email is opened in KMail OBSERVED RESULT Clicking into notification does nothing EXPECTED RESULT Email is opened in KMail SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Graphics Platform: X11 KMail: 5.22.40 alpha (23.03.40) -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 369382] Middle mouse click on article title behaves like left mouse button
https://bugs.kde.org/show_bug.cgi?id=369382 Piotr Sochocki changed: What|Removed |Added Version|5.3.0 |5.21.2 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 369382] Middle mouse click on article title behaves like left mouse button
https://bugs.kde.org/show_bug.cgi?id=369382 Piotr Sochocki changed: What|Removed |Added Platform|OpenSUSE|Archlinux Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Piotr Sochocki --- In Akregator version 5.21.2 (22.08.2) this behavior no longer occurs. Looks like it was fixed along the way. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429858] Problem with creating mbox files
https://bugs.kde.org/show_bug.cgi?id=429858 Piotr Piotrowski changed: What|Removed |Added CC||p...@poczta.onet.pl -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 --- Comment #7 from Piotr --- Workaround wasn't working for me: piorek@dreadnought ~ $ mysql_upgrade --socket=/tmp/akonadi-piorek.XX/mysql.socket Version check failed. Got the following error when calling the 'mysql' command line client ERROR 1049 (42000): Unknown database 'mysql' FATAL ERROR: Upgrade failed Had to create DB mysql first (CREATE DATABASE mysql;). This fixed the problem and upgrade succeeded. Looks like KMail is working fine so far. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Piotr Keplicz changed: What|Removed |Added CC||kepl...@cmc.pl -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 405922] New: Very frequent akonadi crash
https://bugs.kde.org/show_bug.cgi?id=405922 Bug ID: 405922 Summary: Very frequent akonadi crash Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: beln...@gmail.com Target Milestone: --- Application: akonadiserver (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: I can't reproduce it, but it happens few (10 - 20) times a day - since latest KDE frameworks update. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f60f4f59800 (LWP 12676))] Thread 16 (Thread 0x7f60397fa700 (LWP 13068)): #0 0x7f60f2bdabf9 in __GI___poll (fds=0x7f601c003ce0, nfds=1, timeout=85481) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f60efd7b539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f60efd7b64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f60f373515b in QEventDispatcherGlib::processEvents (this=0x7f601c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f60f36d664a in QEventLoop::exec (this=this@entry=0x7f60397f99a0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x564e71b5db41 in Akonadi::Server::Connection::handleIncomingData (this=0x564e73581ee0) at ./src/server/connection.cpp:212 #6 0x7f60f3714d04 in QtPrivate::QSlotObjectBase::call (a=0x7f60397f9a10, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #7 QSingleShotTimer::timerEvent (this=0x7f601c005a10) at kernel/qtimer.cpp:318 #8 0x7f60f370894b in QObject::event (this=0x7f601c005a10, e=) at kernel/qobject.cpp:1271 #9 0x7f60f36d8311 in doNotify (event=0x7f60397f9b50, receiver=0x7f601c005a10) at kernel/qcoreapplication.cpp:1151 #10 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1137 #11 QCoreApplication::notifyInternal2 (receiver=0x7f601c005a10, event=0x7f60397f9b50) at kernel/qcoreapplication.cpp:1061 #12 0x7f60f37345a9 in QTimerInfoList::activateTimers (this=0x7f601c005120) at kernel/qtimerinfo_unix.cpp:643 #13 0x7f60f3734d71 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #14 0x7f60efd7b387 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f60efd7b5c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f60efd7b64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f60f373513f in QEventDispatcherGlib::processEvents (this=0x7f601c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #18 0x7f60f36d664a in QEventLoop::exec (this=this@entry=0x7f60397f9da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #19 0x7f60f34fe41a in QThread::exec (this=) at thread/qthread.cpp:531 #20 0x7f60f34ffbc2 in QThreadPrivate::start (arg=0x7f606c047fd0) at thread/qthread_unix.cpp:361 #21 0x7f60f17386db in start_thread (arg=0x7f60397fa700) at pthread_create.c:463 #22 0x7f60f2be788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f6039ffb700 (LWP 12924)): #0 0x7f60f2bdabf9 in __GI___poll (fds=0x7f6028003ce0, nfds=1, timeout=2481) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f60efd7b539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f60efd7b64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f60f373515b in QEventDispatcherGlib::processEvents (this=0x7f6028000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f60f36d664a in QEventLoop::exec (this=this@entry=0x7f6039ffa9a0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x564e71b5db41 in Akonadi::Server::Connection::handleIncomingData (this=0x564e735fccd0) at ./src/server/connection.cpp:212 #6 0x7f60f3714d04 in QtPrivate::QSlotObjectBase::call (a=0x7f6039ffaa10, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #7 QSingleShotTimer::timerEvent (this=0x7f6028005a10) at kernel/qtimer.cpp:318 #8 0x7f60f370894b in QObject::event (this=0x7f6028005a10, e=) at kernel/qobject.cpp:1271 #9 0x7f60f36d8311 in doNotify (event=0x7f6039ffab50, receiver=0x7f6028005a10) at kernel/qcoreapplication.cpp:1151 #10 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1137 #11 QCoreApplication::notifyInternal2 (receiver=0x7f6028005a10, event=0x7f6039ffab50) at kernel/qcoreapplication.cpp:1061 #12
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Piotr Keplicz changed: What|Removed |Added CC||kepl...@cmc.pl -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402310] New: akonadi_maildir_resource crashes on bulk delete
https://bugs.kde.org/show_bug.cgi?id=402310 Bug ID: 402310 Summary: akonadi_maildir_resource crashes on bulk delete Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: kepl...@cmc.pl Target Milestone: --- SUMMARY akonadi_maildir_resource crashes sometimes after trying to delete multiple mails from a local folder. STEPS TO REPRODUCE 1. Select all the emails in a local folder 2. Press Delete 3. Some emails get deleted, some are visible in the folder (disappearing on akonadi restart) 3. Sometimes akonadi_maildir_resource crashes too. OBSERVED RESULT Application: akonadi_maildir_resource (akonadi_maildir_resource), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2e9c93d200 (LWP 23730))] Thread 4 (Thread 0x7f2e7f987700 (LWP 23774)): [KCrash Handler] #6 0x7f2e981bce97 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f2e981be801 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7f2e988138b7 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f2e98819a06 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f2e98819a41 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f2e98b8fd7b in qTerminate () at global/qglobal.cpp:3193 #12 0x7f2e98bbfc6b in QThreadPrivate::start (arg=0x55e986009ca0) at thread/qthread_unix.cpp:379 #13 0x7f2e9475e6db in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #14 0x7f2e9829f88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f2e80188700 (LWP 23772)): #0 0x7f2e98292bf9 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f2e929e3539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e929e364c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e98de504b in QEventDispatcherGlib::processEvents (this=0x7f2e78000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f2e98d8930a in QEventLoop::exec (this=this@entry=0x7f2e80187d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f2e98bb4bba in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f2e9a227e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f2e98bbfadb in QThreadPrivate::start (arg=0x7f2e9a49fd60) at thread/qthread_unix.cpp:367 #8 0x7f2e9475e6db in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f2e9829f88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f2e894f9700 (LWP 23736)): #0 0x7f2e98292bf9 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f2e953f9747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2e953fb36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2e8c4b9ed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f2e98bbfadb in QThreadPrivate::start (arg=0x55e985f9f090) at thread/qthread_unix.cpp:367 #5 0x7f2e9475e6db in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f2e9829f88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f2e9c93d200 (LWP 23730)): #0 0x7f2e98292bf9 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f2e929e3539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e929e364c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e98de504b in QEventDispatcherGlib::processEvents (this=0x55e985feb9d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f2e8c545761 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #5 0x7f2e98d8930a in QEventLoop::exec (this=this@entry=0x7ffdad010490, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f2e98d924d0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1336 #7 0x7f2e9b92870d in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #8 0x55e984307c51 in Akonadi::ResourceBase::init (argc=, argv=) at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:199 #9 0x7f2e9819fb97 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x55e984307ada in _start () EXPECTED RESULT Emails get deleted without akonadi crashing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 18.04 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53 Qt Version: 5.11.2 KDE PIM Version: 5.10 (KDE Applications 18.12) ADDITIONAL INFORMATION Similar crashes were observed in previous version of KDE PIM. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Piotr Keplicz <kepl...@cmc.pl> changed: What|Removed |Added CC||kepl...@cmc.pl --- Comment #9 from Piotr Keplicz <kepl...@cmc.pl> --- I wish I could remove this status bar too. I find this information completely irrelevant and distracting. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383404] The content pane does not respect the Breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=383404 Piotr Keplicz <kepl...@cmc.pl> changed: What|Removed |Added CC||kepl...@cmc.pl Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Piotr Keplicz <kepl...@cmc.pl> --- There are some themes for this pane in /usr/share/akregator/grantleetheme/5.2. One could edit them by hand and it sort of works... apart from obvious problems. * These changes will be overwritten on the next upgrade :) * When content changes, the pane flickers white. * Not sure whether there's a simple way to access system colors from the templates. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in
https://bugs.kde.org/show_bug.cgi?id=381929 --- Comment #27 from Piotr Keplicz <kepl...@cmc.pl> --- It happens in my setup: * up-to-date Neon User edition, * kontact is started using the session on login, * kontact sometimes crashes on logout (I'm unable to get the trace since DrKonqi quits when the session ends a couple of seconds after the crash), * on next login, kontact starts and akregator's feeds list is empty. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #78 from Piotr Keplicz <kepl...@cmc.pl> --- It happens in KMail 5.5.3 (KDE Neon) on a regular basis in a local folder for a mailing list. The mails are moved to this folder using a standard mailing list filter on incoming mail from a POP3 account. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Piotr Keplicz <kepl...@cmc.pl> changed: What|Removed |Added CC||kepl...@cmc.pl -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in
https://bugs.kde.org/show_bug.cgi?id=381929 Piotr Keplicz <kepl...@cmc.pl> changed: What|Removed |Added CC||kepl...@cmc.pl -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 373871] New mails are not inserted into the database
https://bugs.kde.org/show_bug.cgi?id=373871 Piotr Belniak <beln...@gmail.com> changed: What|Removed |Added CC||beln...@gmail.com --- Comment #1 from Piotr Belniak <beln...@gmail.com> --- I am not sure how to vote for the fix - so adding comment as it affects my kmail too. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 Piotr Keplicz <kepl...@cmc.pl> changed: What|Removed |Added CC|kepl...@cmc.pl | -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 369382] Middle mouse click on article title behaves like left mouse button
https://bugs.kde.org/show_bug.cgi?id=369382 Piotr Sochocki <piotr.p.socho...@gmail.com> changed: What|Removed |Added CC||piotr.p.socho...@gmail.com --- Comment #1 from Piotr Sochocki <piotr.p.socho...@gmail.com> --- Can confirm. Middle mouse button and left mouse button behave the same way in this scenario. Akregator version 5.3.0 To reproduce: 1. Settings => Browser 2. Set "Left mouse click" to "open in tab" 3. Set "Middle mouse click" to "open in external browser" 4. Save settings 5. Using left mouse button on a link opens given link in new akregator tab (correct) 6. Using middle mouse button on a link opens given link in new akregator tab (incorrect) now reverse: 1. Settings => Browser 2. Set "Left mouse click" to "open in external browser 3. Set "Middle mouse click" to "open in tab" 4. Save settings 5. Using left mouse button on a link opens given link in external browser (correct) 6. Using middle mouse button on a link opens given link in external browser (incorrect) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 288140] No visual feedback on the progress of moving folders
https://bugs.kde.org/show_bug.cgi?id=288140 --- Comment #3 from Piotr Golonka <piotr.golo...@cern.ch> --- Again, as with 287514, I'm not able to confirm it. In my recent attempts with kmail 5.3.0 (fedora 24), it took literally minutes to get the list of messages in the INBOX synced (and, indeed, progress bar was slowly progressing, yet I had not enough patience to wait for the list of messages to pop up)... Hence, please, close this one too as "unconfirmed" or "not reproducible". Being a KDE fan since versions 1.X, I'm looking forward to improvements to akonadi scalability/performance so that I could get back to use kmail again one day. with very best regards, Piotr -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 287514] mail check not working after hibernation of a laptop
https://bugs.kde.org/show_bug.cgi?id=287514 --- Comment #4 from Piotr Golonka <piotr.golo...@cern.ch> --- Unfortunatel I cannot confirm it anymore - I had to change my email client to be able to deal with a large mailbox (the decision was tearing my heart apart, as I was using kmail for more that a decade). Hence, from my perspective, this one could be closed as not reproducible... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363132] Mails in root folder
https://bugs.kde.org/show_bug.cgi?id=363132 --- Comment #2 from Piotr Budny <piotr.budny+bugs...@gmail.com> --- Version 5.1.3 Frameworks 5.22.0, Qt 5.5.1 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 363132] Mails in root folder
https://bugs.kde.org/show_bug.cgi?id=363132 Piotr Budny <piotr.budny+bugs...@gmail.com> changed: What|Removed |Added CC||piotr.budny+bugskde@gmail.c ||om -- 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
[kmail2] [Bug 362575] New: Cannot unsubscribe IMAP folder
https://bugs.kde.org/show_bug.cgi?id=362575 Bug ID: 362575 Summary: Cannot unsubscribe IMAP folder Product: kmail2 Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: piotr.budny+bugs...@gmail.com Isubscribing imap folder has no effect, it does not dissapear from folder list. Reproducible: Always Steps to Reproduce: 1. Right click on folder, manage local subscriptions 2. Uncheck folder you want not to subscribe 3. OK Actual Results: Folder is still subscribed Expected Results: Unsubscribe unsselected folders Checked also on freshly added IMAP account. -- 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
[kmail2] [Bug 334052] kmail should preserve the tabs with messages after re-start
https://bugs.kde.org/show_bug.cgi?id=334052 Piotr Budny <piotr.budny+bugs...@gmail.com> changed: What|Removed |Added CC||piotr.budny+bugskde@gmail.c ||om --- Comment #1 from Piotr Budny <piotr.budny+bugs...@gmail.com> --- Occurs in 5.0.3 also (framework 5.15.0, qt 54.2), kubuntu wily. What's the point of restoring empty view tabs? -- 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
[kmail2] [Bug 342508] New: IMAP based messages not being marked as read when reading done via web gui.
https://bugs.kde.org/show_bug.cgi?id=342508 Bug ID: 342508 Summary: IMAP based messages not being marked as read when reading done via web gui. Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: piotr.gbylic...@reconnix.com When using an IMAP account (Google mail) messages are not being synchronised to read state when they were viewed through web gui. Before update to Fedora 21 (KDE 4.14.3) reading message in either KMail or web gui resulted in that message being marked as read in the other one after short while. Right now reading message in KMail does mark them properly so they are marked read in web gui, but reading message in web gui does not result in it marked as read in KMail. I've tried to synchronize manually, but neither initiating Update Folder on specific forder nor Update folder and all it's subfolders on any of the folders above worked. Reproducible: Always Steps to Reproduce: 1. Read message via web interface 2. Wait for KMail to do automatic synchronization of the IMAP account. Actual Results: Messages read via web interface are not marked as read in KMail Expected Results: Messages read via web interface are marked as read in KMail -- 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
[kontact] [Bug 333725] Kontact crashed out of the blue
https://bugs.kde.org/show_bug.cgi?id=333725 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl --- Comment #3 from Piotr Keplicz kepl...@cmc.pl --- Application: kontact (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-24-generic x86_64 Distribution: Ubuntu 14.10 -- Information about the crash: - What I was doing when the application crashed: Kontact crashed suddenly, a couple of minutes after system startup. I wasn't doing anything in the Kontact at the moment. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f2b1ce7b8c0 (LWP 4587))] Thread 4 (Thread 0x7f2afc9b6700 (LWP 4651)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2b17b7581d in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f2b17b75859 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f2b1428f0a5 in start_thread (arg=0x7f2afc9b6700) at pthread_create.c:309 #4 0x7f2b1a3a084d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f2abc0b3700 (LWP 4665)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2b178b620d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f2b17ba4fd6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f2b1428f0a5 in start_thread (arg=0x7f2abc0b3700) at pthread_create.c:309 #4 0x7f2b1a3a084d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f2aa8b99700 (LWP 4715)): [KCrash Handler] #6 0x7f2b11a063ae in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #7 0x7f2b119fee02 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #8 0x7f2b119ff332 in dbus_message_unref () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #9 0x7f2b197187e9 in q_dbus_message_unref (message=optimized out) at qdbus_symbols_p.h:296 #10 ~QDBusArgumentPrivate (this=optimized out, __in_chrg=optimized out) at qdbusargument.cpp:66 #11 QDBusArgument::~QDBusArgument (this=0x16abc30, __in_chrg=optimized out) at qdbusargument.cpp:348 #12 0x7f2b196f565e in qMetaTypeDeleteHelperQDBusArgument (t=0x3462840) at ../../include/QtCore/../../src/corelib/kernel/qmetatype.h:134 #13 0x7f2b1ab19143 in clear (d=0x10bb5e0) at kernel/qvariant.cpp:290 #14 0x7f2b196e4b5c in node_destruct (this=optimized out, to=0x1ce0398, from=0x1ce0398) at ../../include/QtCore/../../src/corelib/tools/qlist.h:431 #15 free (this=optimized out, data=0x1ce0380) at ../../include/QtCore/../../src/corelib/tools/qlist.h:757 #16 QListQVariant::~QList (this=optimized out, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qlist.h:732 #17 0x7f2b196f8daf in QDBusMessage::~QDBusMessage (this=0x16abc30, __in_chrg=optimized out) at qdbusmessage.cpp:537 #18 0x7f2b196f5bb6 in ~QDBusCallDeliveryEvent (this=0x31f0390, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #19 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x31f0390, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #20 0x7f2b1aaf8f4a in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x16ac1d0) at kernel/qcoreapplication.cpp:1593 #21 0x7f2b1aaf93d3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #22 0x7f2b1ab22ed3 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #23 postEventSourceDispatch (s=0x7f2aa40012e0) at kernel/qeventdispatcher_glib.cpp:287 #24 0x7f2b13da9c5d in g_main_dispatch (context=0x7f2aa40009a0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #25 g_main_context_dispatch (context=context@entry=0x7f2aa40009a0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #26 0x7f2b13da9f48 in g_main_context_iterate (context=context@entry=0x7f2aa40009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #27 0x7f2b13da9ffc in g_main_context_iteration (context=0x7f2aa40009a0, may_block=1) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3842 #28 0x7f2b1ab23031 in QEventDispatcherGlib::processEvents (this=0x7f2aa40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:434 #29 0x7f2b1aaf44f1 in QEventLoop::processEvents (this=this@entry=0x7f2aa8b98d20, flags=...) at kernel/qeventloop.cpp:149 #30 0x7f2b1aaf4805 in QEventLoop::exec
[kontact] [Bug 340277] New: Kontact crashed on startup (~CacheLocker)
https://bugs.kde.org/show_bug.cgi?id=340277 Bug ID: 340277 Summary: Kontact crashed on startup (~CacheLocker) Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: kepl...@cmc.pl Application: kontact (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-23-generic x86_64 Distribution: Ubuntu 14.10 -- Information about the crash: - What I was doing when the application crashed: Kontact crashed with SIGSEGV on startup (when restoring KDE session). -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fc5a449f8c0 (LWP 3026))] Thread 3 (Thread 0x7fc583fda700 (LWP 3079)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc59f19981d in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc59f199859 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc59b8b30a5 in start_thread (arg=0x7fc583fda700) at pthread_create.c:309 #4 0x7fc5a19c484d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fc5436d7700 (LWP 3110)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc59eeda20d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc59f1c8fd6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc59b8b30a5 in start_thread (arg=0x7fc5436d7700) at pthread_create.c:309 #4 0x7fc5a19c484d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fc5a449f8c0 (LWP 3026)): [KCrash Handler] #6 0x7fc59b8bc838 in _xend () at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:33 #7 __lll_unlock_elision (lock=0x7fc5881fb008, private=128) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29 #8 0x7fc5a26b35b2 in unlock (this=0xc67f80) at ../../kdecore/util/kshareddatacache.cpp:1245 #9 ~CacheLocker (this=synthetic pointer, __in_chrg=optimized out) at ../../kdecore/util/kshareddatacache.cpp:1317 #10 KSharedDataCache::find (this=0xc4b120, key=..., destination=destination@entry=0x7fff3ac05d90) at ../../kdecore/util/kshareddatacache.cpp:1608 #11 0x7fc5a37fd826 in KIconLoaderPrivate::findCachedPixmapWithPath (this=0xc4b5d0, key=..., data=..., path=...) at ../../kdeui/icons/kiconloader.cpp:854 #12 0x7fc5a37fdbec in KIconLoader::loadIcon (this=0xc27b80, _name=..., group=KIconLoader::Small, size=16, state=0, overlays=..., path_store=0x0, canReturnNull=false) at ../../kdeui/icons/kiconloader.cpp:1149 #13 0x7fc5a37fefff in SmallIcon (name=..., force_size=force_size@entry=0, state=state@entry=0, overlays=...) at ../../kdeui/icons/kiconloader.cpp:1556 #14 0x7fc53a9df42d in MessageList::Core::Manager::Manager (this=this@entry=0x1482c40) at ../../messagelist/core/manager.cpp:87 #15 0x7fc53a9e0384 in MessageList::Core::Manager::registerWidget (pWidget=pWidget@entry=0xd75c50) at ../../messagelist/core/manager.cpp:150 #16 0x7fc53aa1d3fa in MessageList::Core::Widget::Widget (this=0xd75c50, pParent=optimized out) at ../../messagelist/core/widgetbase.cpp:127 #17 0x7fc53aa3fb6c in MessageList::Widget::Widget (this=0xd75c50, parent=optimized out) at ../../messagelist/widget.cpp:85 #18 0x7fc53aa36cf9 in MessageList::Pane::createNewTab (this=this@entry=0x158b0c0) at ../../messagelist/pane.cpp:720 #19 0x7fc53aa393a8 in MessageList::Pane::readConfig (this=this@entry=0x158b0c0, restoreSession=restoreSession@entry=false) at ../../messagelist/pane.cpp:1087 #20 0x7fc53aa3a0c1 in MessageList::Pane::Pane (this=0x158b0c0, restoreSession=optimized out, model=optimized out, selectionModel=optimized out, parent=optimized out) at ../../messagelist/pane.cpp:170 #21 0x7fc53b68604d in CollectionPane::CollectionPane (this=0x158b0c0, restoreSession=optimized out, model=optimized out, selectionModel=optimized out, parent=optimized out) at ../../kmail/widgets/collectionpane.cpp:32 #22 0x7fc53b64b079 in KMMainWidget::createWidgets (this=this@entry=0x144eee0) at ../../kmail/kmmainwidget.cpp:993 #23 0x7fc53b65abf1 in KMMainWidget::KMMainWidget (this=0x144eee0, parent=optimized out, aGUIClient=0x100ac00, actionCollection=optimized out, config=...) at ../../kmail/kmmainwidget.cpp:267 #24 0x7fc53b9e3ed1 in KMailPart::KMailPart (this=this@entry=0x100abd0, parentWidget=parentWidget@entry=0xc8b6b0, parent=parent@entry=0xc8b6b0, __in_chrg=optimized out, __vtt_parm=optimized out) at
[kmail2] [Bug 292399] Kmail message list does not show attachment icons
https://bugs.kde.org/show_bug.cgi?id=292399 Piotr Budny piotr.budny+bugs...@gmail.com changed: What|Removed |Added CC||piotr.budny+bugskde@gmail.c ||om -- 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
[kmail2] [Bug 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- 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
[kontact] [Bug 332672] New: Kontact crashed when enabling/disabling modules
https://bugs.kde.org/show_bug.cgi?id=332672 Bug ID: 332672 Summary: Kontact crashed when enabling/disabling modules Classification: Unclassified Product: kontact Version: 4.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kepl...@cmc.pl Application: kontact (4.12.3) KDE Platform Version: 4.12.3 Qt Version: 4.8.6 Operating System: Linux 3.11.0-18-generic i686 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: I opened the Kontact's configuration dialog, enabled KNotes, disabled KNode and finally disabled Knotes - and Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb16ad740 (LWP 2516))] Thread 5 (Thread 0xaee39b40 (LWP 2560)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb31ce84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a49bc in __pthread_cond_wait (cond=0xb5825d90 WTF::pageheap_memory+20720, mutex=0xb5825d78 WTF::pageheap_memory+20696) at forward.c:149 #3 0xb4faba7c in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4fabacf in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb31cad78 in start_thread (arg=0xaee39b40) at pthread_create.c:311 #6 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 4 (Thread 0xae518b40 (LWP 2586)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb31ce84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a49bc in __pthread_cond_wait (cond=0xae5867dc, mutex=0xae5867c4) at forward.c:149 #3 0xb4fdaae3 in WTF::ThreadCondition::wait(WTF::Mutex) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4cb6744 in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb4fc1866 in WTF::threadEntryPoint(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #6 0xb4fda459 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #7 0xb31cad78 in start_thread (arg=0xae518b40) at pthread_create.c:311 #8 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 3 (Thread 0xa9a7cb40 (LWP 4487)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb6087a0b in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb30fba4b in poll (__timeout=__timeout@entry=3968, __nfds=__nfds@entry=1, __fds=__fds@entry=0xa9102160) at /usr/include/i386-linux-gnu/bits/poll2.h:46 #3 g_poll (fds=fds@entry=0xa9102160, nfds=nfds@entry=1, timeout=timeout@entry=3968) at /build/buildd/glib2.0-2.38.1/./glib/gpoll.c:132 #4 0xb30ecb68 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0xa9102160, timeout=3968, context=0xa91004e0) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:4006 #5 g_main_context_iterate (context=context@entry=0xa91004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3707 #6 0xb30ecca8 in g_main_context_iteration (context=0xa91004e0, may_block=1) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3773 #7 0xb63eb9ef in QEventDispatcherGlib::processEvents (this=0xa9100468, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #8 0xb63ba813 in QEventLoop::processEvents (this=this@entry=0xa9a7c258, flags=...) at kernel/qeventloop.cpp:149 #9 0xb63bab39 in QEventLoop::exec (this=this@entry=0xa9a7c258, flags=...) at kernel/qeventloop.cpp:204 #10 0xb62a721d in QThread::exec (this=this@entry=0xa264bc0) at thread/qthread.cpp:537 #11 0xb62a736b in QThread::run (this=0xa264bc0) at thread/qthread.cpp:604 #12 0xb62a9b4f in QThreadPrivate::start (arg=0xa264bc0) at thread/qthread_unix.cpp:349 #13 0xb31cad78 in start_thread (arg=0xa9a7cb40) at pthread_create.c:311 #14 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xabbdbb40 (LWP 4771)): #0 0xb771f424 in __kernel_vsyscall () #1 0xb31ce84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a49bc in __pthread_cond_wait (cond=0xac16f8d0, mutex=0xac16f8b8) at forward.c:149 #3 0xac06cc72 in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4 #4 0xac06ccbf in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4 #5 0xb31cad78 in start_thread (arg=0xabbdbb40) at pthread_create.c:311 #6 0xb609701e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb16ad740 (LWP 2516)): [KCrash Handler] #7 ref (this=0x320fc0) at
[kmail2] [Bug 270275] Flickering context menu on folder updates
https://bugs.kde.org/show_bug.cgi?id=270275 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- 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
[kmail2] [Bug 323536] displaying mail, marking as read is slow
https://bugs.kde.org/show_bug.cgi?id=323536 --- Comment #3 from Piotr Keplicz kepl...@cmc.pl --- It seems that removing some broken maildir resources and recreating akonadi db fixed the problem here. -- 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
[kmail] [Bug 220608] Kmail does not suggest/complete adresses from (external) adress books for new mails
https://bugs.kde.org/show_bug.cgi?id=220608 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- 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
[kmail2] [Bug 301448] Only email addresses are saved to Recent Addresses, full names are not
https://bugs.kde.org/show_bug.cgi?id=301448 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- 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
[kmail2] [Bug 323536] displaying mail, marking as read is slow
https://bugs.kde.org/show_bug.cgi?id=323536 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl --- Comment #2 from Piotr Keplicz kepl...@cmc.pl --- There's a similar problem on Ubuntu with the latest 4.11 packages - it takes ages to display a message or process it in any way. Kontact, akonadiserver and mysqld processes utilize up to 100% of CPU. Debugger in akonadiconsole is being flooded with messages similar to the one below, looping for all the folders: kontact-1223398355 (0xa07ba78) * 224 51 (NAME INBOX MIMETYPE (message/rfc822 inode/directory) REMOTEID /INBOX REMOTEREVISION RESOURCE akonadi_imap_resource_3 VIRTUAL 0 CACHEPOLICY (INHERIT true INTERVAL 60 CACHETIMEOUT -1 SYNCONDEMAND true LOCALPARTS (ENVELOPE HEAD RFC822)) ENTITYDISPLAY (\Skrzynka odbiorcza\ \mail-folder-inbox\ \\ ()) uidnext 93137 collectionflags \\Answered \\Flagged \\Draft \\Deleted \\Seen $MDNSent Junk NonJunk $Forwarded $Label4 $Label1 $Label2 $Label3 $Label5 NotJunk JunkRecorded KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $TODO $WATCHED $IGNORED receipt-handled $has_cal $ATTACHMENT $REPLIED $JUNK $SIGNED $NOTJUNK \\* uidvalidity 1087477203 collectionquota 65810432 30720 imapacl cyrus lrswipcda % XXX lrswipcda %% collectionannotations /vendor/cmu/cyrus-imapd/condstore false % /vendor/cmu/cyrus-imapd/duplicatedeliver false % /vendor/cmu/cyrus-imapd/lastpop 18-Mar-2011 09:50:14 +0100 % /vendor/cmu/cyrus-imapd/partition default % /vendor/cmu/cyrus-imapd/pop3newuidl true % /vendor/cmu/cyrus-imapd/sharedseen false % /vendor/cmu/cyrus-imapd/size 54435965 % /vendor/kolab/folder-test true imapquota user/X STORAGE % 30 STORAGE % 64268 AccessRights wcdCD timestamp 1376597391) -- 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
[kontact] [Bug 323565] New: kontact crashed when akonadiconsole started akonadiserver
https://bugs.kde.org/show_bug.cgi?id=323565 Bug ID: 323565 Summary: kontact crashed when akonadiconsole started akonadiserver Classification: Unclassified Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kepl...@cmc.pl Application: kontact (4.11) KDE Platform Version: 4.11.00 Qt Version: 4.8.4 Operating System: Linux 3.8.0-28-generic i686 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: 1. Stopped all the Akonadi services and Kontact. 2. Started akonadiconsole. 3. akonadiconsole complained about PIM services not running and started them. 4. A message about kontact crashing appeared. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb1638740 (LWP 2480))] Thread 4 (Thread 0xaee5bb40 (LWP 2946)): #0 0xb777e424 in __kernel_vsyscall () #1 0xb314184b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a9d7c in __pthread_cond_wait (cond=0xb581ad70 WTF::pageheap_memory+20720, mutex=0xb581ad58 WTF::pageheap_memory+20696) at forward.c:149 #3 0xb4f59ae5 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4f59b1f in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb313dd78 in start_thread (arg=0xaee5bb40) at pthread_create.c:311 #6 0xb609c3de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 3 (Thread 0xae53ab40 (LWP 3056)): #0 0xb777e424 in __kernel_vsyscall () #1 0xb314184b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60a9d7c in __pthread_cond_wait (cond=0xae5a87dc, mutex=0xae5a87c4) at forward.c:149 #3 0xb4f8af63 in WTF::ThreadCondition::wait(WTF::Mutex) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4c69b1b in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb4f6f982 in WTF::threadEntryPoint(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #6 0xb4f8ab12 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #7 0xb313dd78 in start_thread (arg=0xae53ab40) at pthread_create.c:311 #8 0xb609c3de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xabc29b40 (LWP 4394)): #0 0xb777e424 in __kernel_vsyscall () #1 0xb608cdcb in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb30742db in poll (__timeout=179, __nfds=1, __fds=0xab202160) at /usr/include/i386-linux-gnu/bits/poll2.h:46 #3 g_poll (fds=0xab202160, nfds=1, timeout=179) at /build/buildd/glib2.0-2.36.0/./glib/gpoll.c:132 #4 0xb30656d0 in g_main_context_poll (n_fds=1, fds=0xab202160, timeout=optimized out, context=0xab2004e0, priority=optimized out) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3995 #5 g_main_context_iterate (context=context@entry=0xab2004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3696 #6 0xb3065831 in g_main_context_iteration (context=0xab2004e0, may_block=1) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3762 #7 0xb63f4c3f in QEventDispatcherGlib::processEvents (this=0xab200468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #8 0xb63c13ec in QEventLoop::processEvents (this=this@entry=0xabc29258, flags=...) at kernel/qeventloop.cpp:149 #9 0xb63c16e1 in QEventLoop::exec (this=this@entry=0xabc29258, flags=...) at kernel/qeventloop.cpp:204 #10 0xb62acfec in QThread::exec (this=this@entry=0x93f6a70) at thread/qthread.cpp:542 #11 0xb62ad14b in QThread::run (this=0x93f6a70) at thread/qthread.cpp:609 #12 0xb62afb18 in QThreadPrivate::start (arg=0x93f6a70) at thread/qthread_unix.cpp:338 #13 0xb313dd78 in start_thread (arg=0xabc29b40) at pthread_create.c:311 #14 0xb609c3de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb1638740 (LWP 2480)): [KCrash Handler] #7 0xace8461d in size (this=optimized out) at /usr/include/qt4/QtCore/qlist.h:98 #8 count (this=optimized out) at /usr/include/qt4/QtCore/qlist.h:280 #9 size (this=optimized out) at ../../kmail/undostack.h:52 #10 KMMainWidget::updateMessageActionsDelayed (this=0x97eacb0) at ../../kmail/kmmainwidget.cpp:3997 #11 0xace84ea2 in KMMainWidget::updateMessageActions (this=0x97eacb0, fast=fast@entry=false) at ../../kmail/kmmainwidget.cpp:3829 #12 0xace860d9 in KMMainWidget::initializeFilterActions (this=this@entry=0x97eacb0) at ../../kmail/kmmainwidget.cpp:4336 #13 0xace9d1ce in
[kontact] [Bug 323565] kontact crashed when akonadiconsole started akonadiserver
https://bugs.kde.org/show_bug.cgi?id=323565 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added Version|unspecified |4.11.0 -- 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
[kmail2] [Bug 316249] New: kmail does not remember sieve user password
https://bugs.kde.org/show_bug.cgi?id=316249 Bug ID: 316249 Summary: kmail does not remember sieve user password Classification: Unclassified Product: kmail2 Version: 4.10 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-bugs@kde.org Reporter: piotr.budny+bugs...@gmail.com kmail does not saves username and password (even with the checkbox checked) when alternative url is set up Reproducible: Always Steps to Reproduce: 1. check server uses sieve in account setting, filtering tab 2. pass alternate url address for sieve (e.g. sieve://172.168...:4190) 3. try to manage sieve scripts (enter user password, check remember) 4. quit kmail 5. open kmail Actual Results: kmail does not remember sieve user password asks for username and password every run Expected Results: does not ask for user/pass kubuntu precise 4.10 rc3 also affected -- 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
[kmail] [Bug 230635] KMail doesn't preserve date when syncing with Gmail
https://bugs.kde.org/show_bug.cgi?id=230635 Piotr Suwara peter_de_sow...@o2.pl changed: What|Removed |Added CC||peter_de_sow...@o2.pl --- Comment #3 from Piotr Suwara peter_de_sow...@o2.pl --- I confirm it, KDE 4.10.00, Arch Linux, updated today. This is not only problem with GMail IMAP, but IMAP alone. KMail should send the time it wishes to set as an INTERNALDATE in the APPEND command, as specified in http://tools.ietf.org/html/rfc3501#section-6.3.11 , as Andy wrote before. Now, copying any mails from other mailboxes to an IMAP account results in broken internal dates. Although this is not seen in KMail, which relies on the message headers, it makes quite a problem when managing copied mails in webclients. Using IMAP one usually expects it to work gladly in both cases. IMHO the bug is quite annoying, there are some complains about it on the Internet, and still no solution (going through Thunderbird is not a KDE solution): https://www.google.pl/search?q=kmail+gmail+timestamps -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 307140] New: Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=307140 Bug ID: 307140 Severity: crash Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashed on exit Classification: Unclassified OS: Linux Reporter: kepl...@cmc.pl Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.1) KDE Platform Version: 4.9.1 Qt Version: 4.8.2 Operating System: Linux 3.2.0-30-generic i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I logged in and while session was starting (including Kontact), I immediately opened the main panel menu and clicked Reboot. Kontact crashed during KDE's shutdown sequence. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb771e9c0 (LWP 5480))] Thread 3 (Thread 0xb5680b40 (LWP 5536)): #0 0x0097a416 in __kernel_vsyscall () #1 0x008ed96b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0x037313dc in __pthread_cond_wait (cond=0x6c5da30, mutex=0x6c5da18) at forward.c:139 #3 0x0652c263 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x6c58940) at wtf/FastMalloc.cpp:2495 #4 0x0652c37f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x6c58940) at wtf/FastMalloc.cpp:1618 #5 0x008e9d4c in start_thread (arg=0xb5680b40) at pthread_create.c:308 #6 0x03723ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb4d57b40 (LWP 5537)): #0 0x019c1dcd in __GI_clock_gettime (clock_id=1, tp=0xb4d57008) at ../sysdeps/unix/clock_gettime.c:116 #1 0x04eeb3b5 in do_gettime (frac=0xb4d57000, sec=0xb4d56ff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x04fd56f6 in QTimerInfoList::updateCurrentTime (this=0xb4402074) at kernel/qeventdispatcher_unix.cpp:343 #4 0x04fd5a4a in QTimerInfoList::timerWait (this=0xb4402074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0x04fd42f3 in timerSourcePrepareHelper (src=optimized out, timeout=0xb4d570ec) at kernel/qeventdispatcher_glib.cpp:136 #6 0x018a4872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x018a4faf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x018a5201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x04fd4db7 in QEventDispatcherGlib::processEvents (this=0xb4400468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x04fa067d in QEventLoop::processEvents (this=0xb4d57270, flags=...) at kernel/qeventloop.cpp:149 #11 0x04fa0919 in QEventLoop::exec (this=0xb4d57270, flags=...) at kernel/qeventloop.cpp:204 #12 0x04e899ec in QThread::exec (this=0x8981248) at thread/qthread.cpp:501 #13 0x04e89adb in QThread::run (this=0x8981248) at thread/qthread.cpp:568 #14 0x04e8ce80 in QThreadPrivate::start (arg=0x8981248) at thread/qthread_unix.cpp:307 #15 0x008e9d4c in start_thread (arg=0xb4d57b40) at pthread_create.c:308 #16 0x03723ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb771e9c0 (LWP 5480)): [KCrash Handler] #7 0x010b0dc4 in operator QItemSelectionModel* (this=error reading variable: Cannot access memory at address 0x5) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:78 #8 QAbstractItemView::selectionModel (this=0x1) at itemviews/qabstractitemview.cpp:766 #9 0x04ad6a46 in MailCommon::FolderTreeWidget::selectedCollections (this=0x1) at ../../mailcommon/foldertreewidget.cpp:244 #10 0x042c26f5 in KMMainWidget::updateFolderMenu (this=0x8e896d0) at ../../kmail/kmmainwidget.cpp:4131 #11 0x042dab36 in KMMainWidget::qt_static_metacall (_o=0x8e896d0, _c=QMetaObject::InvokeMetaMethod, _id=121, _a=0xbff80200) at ./kmmainwidget.moc:458 #12 0x04fb8b81 in QMetaObject::activate (sender=0x918d4d0, m=0x50feed8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3547 #13 0x04fc1b25 in QSingleShotTimer::timeout (this=0x918d4d0) at .moc/release-shared/qtimer.moc:97 #14 0x04fc1c0c in QSingleShotTimer::timerEvent (this=0x918d4d0) at kernel/qtimer.cpp:317 #15 0x04fbcf94 in QObject::event (this=0x918d4d0, e=0xbff8070c) at kernel/qobject.cpp:1157 #16 0x00b02df4 in notify_helper (e=0xbff8070c, receiver=0x918d4d0, this=0x883e170) at kernel/qapplication.cpp:4556 #17 QApplicationPrivate::notify_helper (this=0x883e170, receiver=0x918d4d0, e=0xbff8070c) at kernel/qapplication.cpp:4528 #18 0x00b0815d in QApplication::notify (this=0xbff8070c, receiver=0x918d4d0, e=0xbff8070c) at kernel/qapplication.cpp:4285 #19 0x003132a1 in KApplication::notify (this=0xbff81314, receiver=0x918d4d0, event=0xbff8070c) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x04fa1dde in QCoreApplication::notifyInternal (this=0xbff81314, receiver=0x918d4d0,
[Bug 301261] New: Lost email while moving the folder from local to imap
https://bugs.kde.org/show_bug.cgi?id=301261 Bug ID: 301261 Severity: critical Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Lost email while moving the folder from local to imap Classification: Unclassified OS: Linux Reporter: piotr.golo...@cern.ch Hardware: Fedora RPMs Status: UNCONFIRMED Component: folders Product: kmail2 I dragged one of my local email folder to my IMAP folder (I decided that I want to have it in IMAP, not locally any longer). This blocked the kontact's IMAP folders (greyed out), and I restarted akonadi in a meantime (typical way to workaround the problems with akonadi when changing a network connections, already reported by many people) After I started again, the local folder was already empty and the target folder (in IMAP) was empty as well. Looks like my emails documenting 3 years of work in a collaboration are lost... Reproducible: Always Steps to Reproduce: Would not even dare to repeat it again... -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 296795] New: Contact crashes when trying to display IMAP folder content
https://bugs.kde.org/show_bug.cgi?id=296795 Bug ID: 296795 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Contact crashes when trying to display IMAP folder content Classification: Unclassified OS: Linux Reporter: beln...@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-17-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I have 2 IMAP accounts configured in Kontact - gmail + other account. Since I upgraded KDE to version 4.8 when I try do switch folders in kontact it crashes very frequently. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fe77b4097c0 (LWP 22887))] Thread 6 (Thread 0x7fe75f953700 (LWP 22888)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fe777c40c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fe777c40d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fe77340defc in start_thread (arg=0x7fe75f953700) at pthread_create.c:304 #4 0x7fe77895059d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 5 (Thread 0x7fe75f03a700 (LWP 22889)): #0 0x7fe778944473 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fe772f3bf68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe772f3c429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe7790bec26 in QEventDispatcherGlib::processEvents (this=0xeffd70, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe77908e402 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe77908e657 in QEventLoop::exec (this=0x7fe75f039dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe778f8e067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fe778f9108b in QThreadPrivate::start (arg=0xeff3f0) at thread/qthread_unix.cpp:298 #8 0x7fe77340defc in start_thread (arg=0x7fe75f03a700) at pthread_create.c:304 #9 0x7fe77895059d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 4 (Thread 0x7fe711718700 (LWP 22897)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7fe7788ed62f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fe7788eb9c1 in __GI___libc_free (mem=0x7fe778c091c0) at malloc.c:3736 #3 0x7fe77421eaed in cleanup (pointer=0x1590130) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #4 ~QScopedPointer (this=0x1590078, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #5 QHostAddress::~QHostAddress (this=0x1590078, __in_chrg=optimized out) at kernel/qhostaddress.cpp:563 #6 0x7fe77423e15d in QAbstractSocketPrivate::~QAbstractSocketPrivate (this=0x158ff50, __in_chrg=optimized out) at socket/qabstractsocket.cpp:495 #7 0x7fe774244421 in ~QTcpSocketPrivate (this=0x158ff50, __in_chrg=optimized out) at socket/qtcpsocket_p.h:61 #8 QTcpSocketPrivate::~QTcpSocketPrivate (this=0x158ff50, __in_chrg=optimized out) at socket/qtcpsocket_p.h:61 #9 0x7fe7790a8350 in cleanup (pointer=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #10 ~QScopedPointer (this=0x158ff00, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #11 QObject::~QObject (this=0x158fef8, __in_chrg=optimized out) at kernel/qobject.cpp:817 #12 0x7fe77424f03f in ~QLocalUnixSocket (this=0x158fef8, __in_chrg=optimized out) at socket/qlocalsocket_p.h:79 #13 ~QLocalSocketPrivate (this=0x158fe10, __in_chrg=optimized out) at socket/qlocalsocket_p.h:114 #14 QLocalSocketPrivate::~QLocalSocketPrivate (this=0x158fe10, __in_chrg=optimized out) at socket/qlocalsocket_p.h:114 #15 0x7fe7790a8350 in cleanup (pointer=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #16 ~QScopedPointer (this=0x158fc18, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #17 QObject::~QObject (this=0x158fc10, __in_chrg=optimized out) at kernel/qobject.cpp:817 #18 0x7fe774246989 in QLocalSocket::~QLocalSocket (this=0x158fc10, __in_chrg=optimized out) at socket/qlocalsocket.cpp:353 #19 0x7fe76cd75d60 in ?? () from /usr/lib/libsopranoclient.so.1 #20 0x7fe76cd75df9
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292806] New: kontact crashes after start
https://bugs.kde.org/show_bug.cgi?id=292806 Summary: kontact crashes after start Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: kepl...@cmc.pl Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 Qt Version: 4.7.4 Operating System: Linux 3.0.0-15-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I closed Kontact and restarted it. It worked for a couple of seconds and crashed. I tried to start it again and it crashed - again. -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0xb77b1730 (LWP 15221))] Thread 5 (Thread 0xb68a8b70 (LWP 15222)): #0 0x00110416 in __kernel_vsyscall () #1 0x00f80a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x00e20cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0x04183883 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x489f340) at wtf/FastMalloc.cpp:2495 #4 0x0418399f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x489f340) at wtf/FastMalloc.cpp:1618 #5 0x00f7cd31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x00e130ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 4 (Thread 0xb5f7fb70 (LWP 15223)): #0 0x00a72251 in size (this=0x8417d34) at ../../include/QtCore/../../src/corelib/tools/qlist.h:94 #1 count (this=0x8417d34) at ../../include/QtCore/../../src/corelib/tools/qlist.h:267 #2 socketNotifierSourceCheck (source=0x8417d00) at kernel/qeventdispatcher_glib.cpp:83 #3 0x01deaf24 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x01deb8f0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x01debc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0x00a72b37 in QEventDispatcherGlib::processEvents (this=0x8417228, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x00a431dd in QEventLoop::processEvents (this=0xb5f7f2c0, flags=...) at kernel/qeventloop.cpp:149 #8 0x00a43421 in QEventLoop::exec (this=0xb5f7f2c0, flags=...) at kernel/qeventloop.cpp:201 #9 0x0094690b in QThread::exec (this=0x8416d38) at thread/qthread.cpp:498 #10 0x009469fb in QThread::run (this=0x8416d38) at thread/qthread.cpp:565 #11 0x009497b3 in QThreadPrivate::start (arg=0x8416d38) at thread/qthread_unix.cpp:331 #12 0x00f7cd31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #13 0x00e130ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 3 (Thread 0xb4e21b70 (LWP 15231)): #0 0x00110416 in __kernel_vsyscall () #1 0x00f83619 in __lll_lock_wait () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x00f80b36 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #3 0x00e20cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #4 0x009485b3 in QMutexPrivate::wait (this=0x8ecc680, timeout=-1) at thread/qmutex_unix.cpp:84 #5 0x009447ca in QMutex::lock (this=0x8963cdc) at thread/qmutex.cpp:167 #6 0x07bc8560 in ?? () from /usr/lib/libsopranoclient.so.1 #7 0x07bc86d2 in ?? () from /usr/lib/libsopranoclient.so.1 #8 0x07bc8703 in ?? () from /usr/lib/libsopranoclient.so.1 #9 0x009478db in QThreadStorageData::set (this=0x98a1758, p=0xb563d2d0) at thread/qthreadstorage.cpp:165 #10 0x07bc5d08 in ?? () from /usr/lib/libsopranoclient.so.1 #11 0x07bc5d8f in ?? () from /usr/lib/libsopranoclient.so.1 #12 0x07bc5096 in Soprano::Client::LocalSocketClient::isConnected() const () from /usr/lib/libsopranoclient.so.1 #13 0x07402d3f in init (forced=optimized out, this=optimized out) at ../../nepomuk/core/nepomukmainmodel.cpp:97 #14 model (this=0x8bcacf0) at ../../nepomuk/core/nepomukmainmodel.cpp:115 #15 Nepomuk::MainModel::executeQuery (this=0x8bcab88, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212 #16 0x0233d703 in Soprano::FilterModel::executeQuery(QString const, Soprano::Query::QueryLanguage, QString const) const () from /usr/lib/libsoprano.so.4 #17 0x073f15a1 in Nepomuk::ResourceData::load (this=0x9a3e2a8) at ../../nepomuk/core/resourcedata.cpp:409 #18 0x073f1910 in Nepomuk::ResourceData::property (this=0x9a3e2a8, uri=...) at ../../nepomuk/core/resourcedata.cpp:240 #19 0x07407bc1 in Nepomuk::Resource::property (this=0xb4e2128c, uri=...) at ../../nepomuk/core/resource.cpp:301 #20 0x04f98c11 in MessageCore::NepomukResourceRetrieverRunnable::run (this=0x9660a68) at ../../messagecore/asyncnepomukresourceretriever.cpp:47 #21 0x0093d651 in QThreadPoolThread::run (this=0x8c54bc0) at concurrent/qthreadpool.cpp:106 #22
[Bug 292806] kontact crashes after start
https://bugs.kde.org/show_bug.cgi?id=292806 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID --- Comment #1 from Piotr Keplicz keplicz cmc pl 2012-01-29 23:05:02 --- Actually, this might have been a result of an overheating. The guilty was probably the Nepomuk indexer rebuilding its database. Removed the broken Nepomuk's db, disabled the indexers and Kontact works fine. -- 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 290247] New: Nepomuk email feeder crashed on logout
https://bugs.kde.org/show_bug.cgi?id=290247 Summary: Nepomuk email feeder crashed on logout Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Nepomuk Feeder Agents AssignedTo: kdepim-bugs@kde.org ReportedBy: kepl...@cmc.pl CC: vkra...@kde.org Application: akonadi_nepomuk_email_feeder (4.7) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-14-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: KMail2 (Nepomuk email feeder) crashed when logging out of a KDE session. -- Backtrace: Application: Obsługa e-maili dla Nepomuka (akonadi_nepomuk_email_feeder), signal: Aborted [KCrash Handler] #7 0x00c32416 in __kernel_vsyscall () #8 0x034d8c8f in raise () from /lib/i386-linux-gnu/libc.so.6 #9 0x034dc2b5 in abort () from /lib/i386-linux-gnu/libc.so.6 #10 0x0350edfc in ?? () from /lib/i386-linux-gnu/libc.so.6 #11 0x03519bc2 in ?? () from /lib/i386-linux-gnu/libc.so.6 #12 0x0351bcf3 in ?? () from /lib/i386-linux-gnu/libc.so.6 #13 0x0351d498 in malloc () from /lib/i386-linux-gnu/libc.so.6 #14 0x08715e0b in qMalloc (size=12) at global/qmalloc.cpp:55 #15 0x0873aa53 in QHashData::allocateNode (this=0x8c44750, nodeAlign=4) at tools/qhash.cpp:175 #16 0x00a7cec4 in createNode (anextNode=optimized out, akey=@0x9c16a34, ah=162677592, this=optimized out, avalue=optimized out) at /usr/include/qt4/QtCore/qhash.h:541 #17 insert (avalue=optimized out, this=0xbf8e6110, akey=@0x9c16a34) at /usr/include/qt4/QtCore/qhash.h:761 #18 insert (value=@0x9c16a34, this=0xbf8e6110) at /usr/include/qt4/QtCore/qset.h:176 #19 QListNepomuk::ResourceData*::toSet (this=0xbf8e610c) at /usr/include/qt4/QtCore/qset.h:309 #20 0x00a7aa8b in Nepomuk::ResourceManagerPrivate::cleanupCache (this=0x8babaf8, num=-1) at ../../nepomuk/core/resourcemanager.cpp:185 #21 0x00a7af3a in Nepomuk::ResourceManager::clearCache (this=0x8b9db90) at ../../nepomuk/core/resourcemanager.cpp:461 #22 0x00a7af68 in Nepomuk::ResourceManager::~ResourceManager (this=0x8b9db90, __in_chrg=optimized out) at ../../nepomuk/core/resourcemanager.cpp:294 #23 0x00a7b062 in Nepomuk::ResourceManager::~ResourceManager (this=0x8b9db90, __in_chrg=optimized out) at ../../nepomuk/core/resourcemanager.cpp:302 #24 0x0882b841 in QObjectPrivate::deleteChildren (this=0x8aa5980) at kernel/qobject.cpp:1955 #25 0x08830439 in QObject::~QObject (this=0xbf8e62e0, __in_chrg=optimized out) at kernel/qobject.cpp:946 #26 0x0881a648 in QCoreApplication::~QCoreApplication (this=0xbf8e62e0, __in_chrg=optimized out) at kernel/qcoreapplication.cpp:671 #27 0x06797943 in QApplication::~QApplication (this=0xbf8e62e0, __in_chrg=optimized out) at kernel/qapplication.cpp:1093 #28 0x007e4668 in KApplication::~KApplication (this=0xbf8e62e0, __in_chrg=optimized out) at ../../kdeui/kernel/kapplication.cpp:894 #29 0x080553f1 in Akonadi::AgentBase::initAkonadi::NepomukEMailFeeder (argc=3, argv=0xbf8e63b4) at /usr/include/akonadi/agentbase.h:334 #30 0x0805307b in main (argc=3, argv=0xbf8e63b4) at ../../nepomuk_email_feeder/nepomukemailfeeder.cpp:133 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 289607] New: KMail2 crashed on logout
https://bugs.kde.org/show_bug.cgi?id=289607 Summary: KMail2 crashed on logout Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Mail Dispatcher Agent AssignedTo: kdepim-bugs@kde.org ReportedBy: kepl...@cmc.pl CC: vkra...@kde.org Application: akonadi_maildispatcher_agent (4.7) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-14-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I logged out of KDE and KMail2 (one of the Akonadi agents) crashed. I experienced a similar crash before, in both cases the computer was put to sleep, losing network connectivity. -- Backtrace: Application: Agent przyjmowania poczty (akonadi_maildispatcher_agent), signal: Segmentation fault [KCrash Handler] #7 deref (this=0x790061) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132 #8 QString::operator= (this=0x920caa6, other=...) at tools/qstring.cpp:1359 #9 0x046cd203 in KWallet::Wallet::readPassword (this=0x9262aa8, key=..., value=...) at ../../kdeui/util/kwallet.cpp:1256 #10 0x001d6fe1 in MailTransport::Transport::readPassword (this=0x920ca18) at ../../mailtransport/transport.cpp:311 #11 0x001d780c in MailTransport::Transport::password (this=0x920ca18) at ../../mailtransport/transport.cpp:68 #12 0x001e64e2 in MailTransport::SmtpJob::startSmtpJob (this=0x9262c88) at ../../mailtransport/smtpjob.cpp:169 #13 0x001e8157 in MailTransport::SmtpJob::doStart (this=0x9262c88) at ../../mailtransport/smtpjob.cpp:130 #14 0x001e4040 in MailTransport::TransportJob::start (this=0x9262c88) at ../../mailtransport/transportjob.cpp:129 #15 0x0805c253 in SendJob::Private::doTraditionalTransport (this=0x9201ab8) at ../../../agents/maildispatcher/sendjob.cpp:201 #16 0x0805cb65 in SendJob::Private::doTransport (this=0x9201ab8) at ../../../agents/maildispatcher/sendjob.cpp:130 #17 0x0805d487 in SendJob::qt_metacall (this=0x9210290, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0x91670b8) at ./sendjob.moc:85 #18 0x00542b7d in metacall (argv=0x91670b8, idx=26, cl=QMetaObject::InvokeMetaMethod, object=0x9210290) at kernel/qmetaobject.cpp:237 #19 QMetaObject::metacall (object=0x9210290, cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0x91670b8) at kernel/qmetaobject.cpp:232 #20 0x0054d685 in QMetaCallEvent::placeMetaCall (this=0x918dfb8, object=0x9210290) at kernel/qobject.cpp:535 #21 0x00554b52 in QObject::event (this=0x9210290, e=0x918dfb8) at kernel/qobject.cpp:1217 #22 0x05ae4d54 in notify_helper (e=0x918dfb8, receiver=0x9210290, this=0x90447e8) at kernel/qapplication.cpp:4486 #23 QApplicationPrivate::notify_helper (this=0x90447e8, receiver=0x9210290, e=0x918dfb8) at kernel/qapplication.cpp:4458 #24 0x05aea103 in QApplication::notify (this=0x918dfb8, receiver=0x9210290, e=0x918dfb8) at kernel/qapplication.cpp:3886 #25 0x04581971 in KApplication::notify (this=0xbfae56a0, receiver=0x9210290, event=0x918dfb8) at ../../kdeui/kernel/kapplication.cpp:311 #26 0x0053c19e in QCoreApplication::notifyInternal (this=0xbfae56a0, receiver=0x9210290, event=0x918dfb8) at kernel/qcoreapplication.cpp:787 #27 0x0053ff93 in sendEvent (event=optimized out, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #28 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x902a468) at kernel/qcoreapplication.cpp:1428 #29 0x005400ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321 #30 0x0056a6a4 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #31 postEventSourceDispatch (s=0x9046b00) at kernel/qeventdispatcher_glib.cpp:277 #32 0x00d5125f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #33 0x00d51990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #34 0x00d51c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #35 0x0056aada in QEventDispatcherGlib::processEvents (this=0x902b3a0, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #36 0x05b9ce3a in QGuiEventDispatcherGlib::processEvents (this=0x902b3a0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #37 0x0053b1dd in QEventLoop::processEvents (this=0xbfae5604, flags=...) at kernel/qeventloop.cpp:149 #38 0x0053b421 in QEventLoop::exec (this=0xbfae5604, flags=...) at kernel/qeventloop.cpp:201 #39 0x0054019d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #40 0x05ae28f4 in QApplication::exec () at kernel/qapplication.cpp:3760 #41 0x009b7471 in Akonadi::AgentBase::init (r=0x9127540) at ../../akonadi/agentbase.cpp:564 #42 0x0805215f in Akonadi::AgentBase::initMailDispatcherAgent (argc=3, argv=0xbfae5774) at /usr/include/KDE/Akonadi/../../akonadi/agentbase.h:342
[Bug 288140] New: No visual feedback on the progress of moving folders
https://bugs.kde.org/show_bug.cgi?id=288140 Summary: No visual feedback on the progress of moving folders Product: kmail2 Version: 4.7 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders AssignedTo: kdepim-bugs@kde.org ReportedBy: piotr.golo...@cern.ch Version: 4.7 (using KDE 4.7.3) OS:Linux I recently moved to KDE-4.7, from previously used 4.5. What I hoped was that all the features of previously included (excellent!) KMail are also available in this new version... Apparently this is not the case: The problem I want to report is that many operations that have previously been done by KMail itself, are now done with Akonadi, and since then we have no proper visual feedback of their progress. For instance, when I command to move the folder to another folder (ie. right-click on a folder and select move folder to), the operation sometimes takes long (tens of seconds for large folders), and during that time there is no visual feedback that my command was accepted - the folder does not appear in the new place, the number of email messages in the old folder do not change, no progress bar either... This is very confusing. So far, the only way I have found to trace that kmail/akonadi actually does someting was to start akonadi from a konsole (or, to be more precise, do akonadictl restart), and then watch the debug messages coming... Reproducible: Always Steps to Reproduce: Try to move a folder, in particular if it contains ~1000 messages and a couple of tens of megabytes of data... Try to move it from KMail-Import to Local Folders, for instance. Or between the local storage and a IMAP resource Actual Results: No visual feedback! Expected Results: I'd expect to have the behaviour of kmail from before akonadi. Namely: * the progress bar (in the bottom-right of kmail) shows the progress of operation * the folder pops up in the new place immediately, and while the messages are being moved you could see the message counter (in the folder list) being updated - you see that messages disappear from one place and appear in the other. * the messages that have been moved to the new location, should be immediately available in the new folder: if I clicked on any of them, I could immediately read it. OS: Linux (x86_64) release 3.1.2-1.fc16.x86_64 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 287514] New: mail check not working after hibernation of a laptop
https://bugs.kde.org/show_bug.cgi?id=287514 Summary: mail check not working after hibernation of a laptop Product: kmail2 Version: 4.7 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: piotr.golo...@cern.ch Version: 4.7 (using KDE 4.7.3) OS:Linux I upgraded from Fedora 14 to 16 on my laptop, and this is the first time akonadi is used as KMail's backend. I freeze my laptop (suspend), and then wake it up. All the KDE session seems OK. However, kmail does not refresh any folder, and I do not see the new emails in my IMAP resource. Even when I click on an existing message in a list, I cannot see its content. the method I found to get the things working back again was to 1) stop kmail 2) restart akonadi completely using akonadictl restart in commandline 3) start kmail again if I don't stop kmail before restarting akonadi, I get strange artifacts such as only a part of messages being visinle Reproducible: Always Steps to Reproduce: 1) have kmail running, with IMAP resource 2) hibernate, and then unfreeze your laptop Actual Results: folders do not refresh; refresh folder doesn't do anything Expected Results: After unfreezing and checking an email, I should see new emails in my mailbox OS: Linux (x86_64) release 3.1.1-2.fc16.x86_64 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 281649] Kontact crash on shutting down.
https://bugs.kde.org/show_bug.cgi?id=281649 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 281649] Kontact crash on shutting down.
https://bugs.kde.org/show_bug.cgi?id=281649 --- Comment #6 from Piotr Keplicz keplicz cmc pl 2011-11-21 09:55:47 --- Created an attachment (id=65898) -- (http://bugs.kde.org/attachment.cgi?id=65898) New crash information added by DrKonqi kontact (4.7.3) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4 - What I was doing when the application crashed: Kontact crashed when shutting down (after File-Quit). I've seen similar crashes several times ever since I upgraded to KMail2. Doesn't happen every time though. My desktop is fully upgraded to KDE 4.7.3 (on Kubuntu 11.10). -- Backtrace (Reduced): #7 0x057015d6 in QTabWidget::currentWidget (this=0x9d89000) at widgets/qtabwidget.cpp:624 #8 0x04565b46 in MessageList::Pane::currentMessage (this=0x9d89000) at ../../messagelist/pane.cpp:565 #9 0x047e9749 in KMMainWidget::updateListFilterAction (this=0x9da8c18) at ../../kmail/kmmainwidget.cpp:2247 #10 0x047f5cac in KMMainWidget::updateMessageActionsDelayed (this=0x9da8c18) at ../../kmail/kmmainwidget.cpp:3663 #11 0x04808099 in KMMainWidget::qt_metacall (this=0x9da8c18, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xbff514c4) at ./kmmainwidget.moc:360 -- 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 278020] KMail cannot send e-mail via SMTP
https://bugs.kde.org/show_bug.cgi?id=278020 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl --- Comment #26 from Piotr Keplicz keplicz cmc pl 2011-10-14 22:03:36 --- Same here on KMail 4.7.2. Scenario: 1. Activated VPN connection that restricted SMTP. 2. Tried to send a mail which got stuck in the outbox. 3. Disabled VPN. 4. Sent a couple of mails only to notice that they were still in the outbox. Send mail from the queue, restarting Kontact and/or akonadi, restarting KDE didn't help. Just as in comment 16, I had to manually edit the dispatcher config file and restart akonadi. -- 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 283741] list view for favorite folders [regression]
https://bugs.kde.org/show_bug.cgi?id=283741 --- Comment #3 from Piotr Keplicz keplicz cmc pl 2011-10-11 08:10:11 --- Thanks. -- 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 282063] kmail2 - filters don't work on local maildir
https://bugs.kde.org/show_bug.cgi?id=282063 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl --- Comment #5 from Piotr Keplicz keplicz cmc pl 2011-10-10 18:25:49 --- Got similar problem with KMail 4.7.2. I have an IMAP account defined with sent mail saved to a local folder. I set up filters to distribute this mail to proper folders, but it doesn't seem to work ever since I upgraded to KMail2 from KMail1 4.4.10. Manually applying the filter with Ctrl+J in the sent-mail folder works. When sending mail - filters don't work, there's no info in the log either. -- 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 259105] Unread message count in favourite list difficult to read
https://bugs.kde.org/show_bug.cgi?id=259105 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 283741] New: list view for favorite folders [regression]
https://bugs.kde.org/show_bug.cgi?id=283741 Summary: list view for favorite folders [regression] Product: kmail2 Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders AssignedTo: kdepim-bugs@kde.org ReportedBy: kepl...@cmc.pl Version: 4.7 (using KDE 4.7.1) OS:Linux In Kmail1 favorite folders were displayed as a list that could be sorted or ordered manually. In Kmail2 favorites are shown as cluttered icons shown in no particular order. Please restore the old view or give an option to choose the view type and change folders order. Currently it's a usability regression compared to previous Kmail versions. Reproducible: Always Steps to Reproduce: Add some folders to favorites. Watch them appear in a random order in the favorites view. Expected Results: A user should be able to switch the view from icons to a list. Also it should be possible to arrange the icons (automatic or manual sorting). Just like in Kmail1. -- 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 283741] list view for favorite folders [regression]
https://bugs.kde.org/show_bug.cgi?id=283741 --- Comment #1 from Piotr Keplicz keplicz cmc pl 2011-10-10 21:42:22 --- Created an attachment (id=64397) -- (http://bugs.kde.org/attachment.cgi?id=64397) One picture is worth a thousand words. -- 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 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #9 from Piotr Budny piotr budny+bugskde gmail com 2011-10-05 11:52:01 --- mysql-5.5.15-3.x86_64 akonadi-1.6.2-1.x86_64 kde4-kdepim-4.7.2-0.1.x86_64 kde4-kdepim-runtime-4.7.2-0.1.x86_64 kde4-kdepim-libs-4.7.2-0.1.x86_64 But as I said, internal mysqld server is working (connected to it with console) -- 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 283334] New: After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 Summary: After suspend to ram KMail does not work, akonadi says MySQL server has gone away. Product: Akonadi Version: 1.6.0 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: piotr.bu...@gmail.com Version: 1.6.0 (using KDE 4.7.1) OS:Linux After suspend to ram, kmail2 seems like not reading mails content, not fetching new mails etc. Akonadi logs says: MySQL server has gone away. I'm using default akonadi config Reproducible: Always Steps to Reproduce: suspend to ram Actual Results: kmail does not shows messages, does not fetches new mails Expected Results: show messages, fetches new mails akonadictl restart after resuming helps (it is preferred, to close kmail2 first) -- 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 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #2 from Piotr Budny piotr budny gmail com 2011-10-04 19:31:00 --- As I said: I'm using default akonadi config, yes, default is to use internal server -- 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 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #4 from Piotr Budny piotr budny gmail com 2011-10-04 19:44:36 --- That line is already in. Uncommented. -- 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 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #6 from Piotr Budny piotr budny gmail com 2011-10-04 20:18:02 --- Yes, and that mysqld is operate e.g. I've connected to it with a socket, showed databased, selected something), logs from akonadictl restart runned from console: [22:12 vip@prime:~/.local/share/akonadi]% Error during executing query SELECT PimItemTable.id, PimItemTable.remoteId, MimeTypeTable.name, ResourceTable.name, PartTable.name, PartTable.datasize FROM PimItemTable INNER JOIN MimeTypeTable ON ( PimItemTable.mimeTypeId = MimeTypeTable.id ) INNER JOIN CollectionTable ON ( PimItemTable.collectionId = CollectionTable.id ) INNER JOIN ResourceTable ON ( CollectionTable.resourceId = ResourceTable.id ) LEFT JOIN PartTable ON ( PimItemTable.id = PartTable.pimItemId AND PartTable.name IN ( :0 ) AND substr(PartTable.name, 1, 4 ) = ( :1 ) ) WHERE ( collectionId = :2 AND ResourceTable.name ( :3 ) ) ORDER BY PimItemTable.id ASC : MySQL server has gone away QMYSQL: Unable to execute query Error during selection of all records from table CollectionTable MySQL server has gone away QMYSQL: Unable to execute query Error during selection of all records from table CollectionTable MySQL server has gone away QMYSQL: Unable to execute query -- 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 273190] New: Highlighted feed doesn't update it's feeds if it get updated
https://bugs.kde.org/show_bug.cgi?id=273190 Summary: Highlighted feed doesn't update it's feeds if it get updated Product: akregator Version: 1.6.6 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kontact plugin AssignedTo: kdepim-bugs@kde.org ReportedBy: piotrek.juzw...@gmail.com Version: 1.6.6 (using KDE 4.6.2) OS:Linux When i minimized kontakt with a feed highlighted (last selected) and when it gets updated it doesn't show new content, i need to switch to other feeds in order to see the earlier feed's content. Maybe in other words, in the Feeds list i have feed A selected, while it is highlighted the new fetched feeds won't show up until i switch to feed B and back to A... Reproducible: Always Steps to Reproduce: Read details Actual Results: New content is not seen unless switching to another feed and then back to the new updated one. Expected Results: The new content should be seen immediately after fetching new content. -- 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 273190] Highlighted feed doesn't update it's content if it get updated
https://bugs.kde.org/show_bug.cgi?id=273190 Piotr piotrek.juzw...@gmail.com changed: What|Removed |Added Summary|Highlighted feed doesn't|Highlighted feed doesn't |update it's feeds if it get |update it's content if it |updated |get updated -- 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 273190] Highlighted feed doesn't update it's content if it get updated
https://bugs.kde.org/show_bug.cgi?id=273190 Piotr piotrek.juzw...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||UPSTREAM --- Comment #1 from Piotr piotrek juzwiak gmail com 2011-05-13 13:17:14 --- Looks to me that it has been fixed in the 1.7.0 version. Setting this as resolved should suffice? -- 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 270261] [Metabug] KDEPIM 4.6 release blockers
https://bugs.kde.org/show_bug.cgi?id=270261 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 268520] New: Automatically switch to kmail when clicking kmail icon in system tray icon
https://bugs.kde.org/show_bug.cgi?id=268520 Summary: Automatically switch to kmail when clicking kmail icon in system tray icon Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: piotrek.juzw...@gmail.com Version: unspecified OS:Linux There is an option when configuring kmail in kontact to show the tray icon when there is new mail. Clicking that will only turn up kontact and not kmail. What is the point in showing kmail tray icon and clicking it if clicking it will turn up anything else? Wouldn't it be logical to automatically switch to kmail when clicking kmail's tray icon ? Reproducible: Didn't try Steps to Reproduce: Set kmail to show a tray icon when new mail arrives, when new mail arrives click the kmail's tray icon, it will show up whatever was last selected in kontact. Actual Results: It will show up kontact and whatever module was active last time Expected Results: It should automatically switch to kmail as a logical expectation from a user! -- 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 268520] Automatically switch to kmail when clicking kmail icon in system tray icon
https://bugs.kde.org/show_bug.cgi?id=268520 Piotr piotrek.juzw...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE --- Comment #1 from Piotr piotrek juzwiak gmail com 2011-03-14 21:40:02 --- *** This bug has been marked as a duplicate of bug 174977 *** -- 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 174977] clicking on system tray icon doesn't open the relevant kontact part
https://bugs.kde.org/show_bug.cgi?id=174977 Piotr piotrek.juzw...@gmail.com changed: What|Removed |Added CC||piotrek.juzw...@gmail.com --- Comment #22 from Piotr piotrek juzwiak gmail com 2011-03-14 21:40:02 --- *** Bug 268520 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 261593] Frequent plasma-desktop crashes [KCalCore::IncidenceBase::isReadOnly, CalendarSupport::Calendar::Private::dataChanged]
https://bugs.kde.org/show_bug.cgi?id=261593 --- Comment #26 from Piotr Keplicz keplicz cmc pl 2011-03-05 23:51:43 --- Has this bug been fixed? In 4.6.0 plasma used to crash on every login, no such case ever since I upgraded to 4.6.1. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 266595] New: Kmail imap crash when applying filter on imap message
https://bugs.kde.org/show_bug.cgi?id=266595 Summary: Kmail imap crash when applying filter on imap message Product: kmail2 Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: piotr.bu...@gmail.com Application: kmail (1.13.6) KDE Platform Version: 4.6.00 (4.6.0) Qt Version: 4.7.1 Operating System: Linux 2.6.37_pae-4 i686 Distribution: PLD Linux -- Information about the crash: - What I was doing when the application crashed: clicked apply all filters on selected imap message, which probably is already being processed. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #7 0xb6d67b4d in ?? () from /usr/lib/libkmailprivate.so.4 #8 0xb6f71a88 in ?? () from /usr/lib/libkmailprivate.so.4 #9 0xb6f75c9d in ?? () from /usr/lib/libkmailprivate.so.4 #10 0xb5eaf87e in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #11 0xb5ebdb73 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #12 0xb739c811 in KJob::processedSize (this=0x9eda0f0, _t1=0x9eda0f0, _t2=32768) at /usr/src/debug/kdelibs-4.6.0/build/kdecore/kjob.moc:243 #13 0xb739d0c9 in KJob::setProcessedAmount (this=0x9eda0f0, unit=KJob::Bytes, amount=32768) at /usr/src/debug/kdelibs-4.6.0/kdecore/jobs/kjob.cpp:267 #14 0xb54a1889 in KIO::TransferJob::sendAsyncData (this=0x9eda0f0, dataForSlave=...) at /usr/src/debug/kdelibs-4.6.0/kio/kio/job.cpp:1139 #15 0xb54a34b4 in KIO::TransferJob::slotDataReq (this=0x9eda0f0) at /usr/src/debug/kdelibs-4.6.0/kio/kio/job.cpp:1199 #16 0xb54aa696 in KIO::TransferJob::qt_metacall (this=0x9eda0f0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0xbfbebb3c) at /usr/src/debug/kdelibs-4.6.0/build/kio/jobclasses.moc:369 #17 0xb5eaf87e in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #18 0xb5ebdb73 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #19 0xb554b353 in KIO::SlaveInterface::dataReq (this=0x8760460) at /usr/src/debug/kdelibs-4.6.0/build/kio/slaveinterface.moc:152 #20 0xb554e275 in KIO::SlaveInterface::dispatch (this=0x8760460, _cmd=101, rawdata=...) at /usr/src/debug/kdelibs-4.6.0/kio/kio/slaveinterface.cpp:164 #21 0xb554ad6f in KIO::SlaveInterface::dispatch (this=0x8760460) at /usr/src/debug/kdelibs-4.6.0/kio/kio/slaveinterface.cpp:89 #22 0xb553dcbd in KIO::Slave::gotInput (this=0x8760460) at /usr/src/debug/kdelibs-4.6.0/kio/kio/slave.cpp:348 #23 0xb553e3bb in KIO::Slave::qt_metacall (this=0x8760460, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0xbfbebe3c) at /usr/src/debug/kdelibs-4.6.0/build/kio/slave.moc:82 #24 0xb5eaf87e in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #25 0xb5ebdb73 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #26 0xb546f7a1 in KIO::Connection::readyRead (this=0x88cc3b0) at /usr/src/debug/kdelibs-4.6.0/build/kio/connection.moc:92 #27 0xb546ff1c in KIO::ConnectionPrivate::dequeue (this=0x88cc418) at /usr/src/debug/kdelibs-4.6.0/kio/kio/connection.cpp:82 #28 0xb546ffb9 in KIO::Connection::qt_metacall (this=0x88cc3b0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x98b3438) at /usr/src/debug/kdelibs-4.6.0/build/kio/connection.moc:79 #29 0xb5eaf87e in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #30 0xb5eb9614 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4 #31 0xb5ebd6d0 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #32 0xb6102bc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #33 0xb610740c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #34 0xb76cae7a in KApplication::notify (this=0xbfbec730, receiver=0x88cc3b0, event=0x954b370) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311 #35 0xb5ea996e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #36 0xb5ead228 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #37 0xb5ead35b in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #38 0xb5ed4869 in ?? () from /usr/lib/libQtCore.so.4 #39 0xb405560a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #40 0xb4055d8f in ?? () from /usr/lib/libglib-2.0.so.0 #41 0xb4056011 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #42 0xb5ed49b9 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #43
[Bug 245993] New: Wish for field 'name day' in KAddressbook
https://bugs.kde.org/show_bug.cgi?id=245993 Summary: Wish for field 'name day' in KAddressbook Product: kaddressbook Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: peter_de_sow...@o2.pl CC: to...@kde.org Version: unspecified (using KDE 4.4.5) OS:Linux I wonder if there was a possibility of adding a field to address book named Name day similar to Birthday, so that one may see it also in KOrganizer for example. Name day, according to Wikipedia, is celebrated in quite a lot of countries. It would also be great to include name day calendars specific to different countries, so that one may just write down somebody's name and then choose the appropriate day (for most of the names there are several different name days, but of course one person celebrates only one of them). Reproducible: Didn't try -- 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 240662] Kontact crashes when disabling checking of one of imap folders
https://bugs.kde.org/show_bug.cgi?id=240662 --- Comment #2 from Piotr deszynski red-sky pl 2010-06-06 23:34:32 --- Ok, I've installed kdepim-dbg pakage, here are missing lines from stack trace: #7 0xb435d2fb in KMail::FolderDialogGeneralTab::save (this=0xa75c8d0) at ../../kmail/kmfolderdialog.cpp:680 #8 0xb4362004 in KMail::FolderDialogTab::accept (this=0xa75c8d0) at ../../kmail/kmfolderdialog.h:104 #9 0xb4351d5c in KMFolderDialog::slotOk (this=0xa70ca30) at ../../kmail/kmfolderdialog.cpp:244 #10 0xb4351c40 in KMFolderDialog::qt_metacall (this=0xa70ca30, _c=QMetaObject::InvokeMetaMethod, _id=76, _a=0xbf9ef21c) at ./kmfolderdialog.moc:429 -- 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 240662] Kontact crashes when disabling checking of one of imap folders
https://bugs.kde.org/show_bug.cgi?id=240662 --- Comment #3 from Piotr deszynski red-sky pl 2010-06-06 23:35:36 --- Created an attachment (id=47759) -- (http://bugs.kde.org/attachment.cgi?id=47759) Full stack trace with kdepim -- 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 240662] Kontact crashes when disabling checking of one of imap folders
https://bugs.kde.org/show_bug.cgi?id=240662 --- Comment #4 from Piotr deszynski red-sky pl 2010-06-06 23:36:13 --- Created an attachment (id=47760) -- (http://bugs.kde.org/attachment.cgi?id=47760) Full stack trace with kdepim -- 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 240662] Kontact crashes when disabling checking of one of imap folders
https://bugs.kde.org/show_bug.cgi?id=240662 Piotr deszyn...@red-sky.pl changed: What|Removed |Added Attachment #47760|Full stack trace with |Full backtrace with kdepim description|kdepim | -- 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 240662] Kontact crashes when disabling checking of one of imap folders
https://bugs.kde.org/show_bug.cgi?id=240662 Piotr deszyn...@red-sky.pl changed: What|Removed |Added Attachment #47759|Full stack trace with |Full backtrace with kdepim description|kdepim | -- 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 240662] New: Kontact crashes when disabling checking of one of imap folders
https://bugs.kde.org/show_bug.cgi?id=240662 Summary: Kontact crashes when disabling checking of one of imap folders Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: deszyn...@red-sky.pl Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Always when trying to disable checking of one of the folders from checking or reporting of new elements kontact crashes. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb77f4990 (LWP 19751))] Thread 2 (Thread 0xb12d2b70 (LWP 19765)): #0 0x00110422 in __kernel_vsyscall () #1 0x00a98b86 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0x048b24eb in g_poll () from /lib/libglib-2.0.so.0 #3 0x048a50ac in ?? () from /lib/libglib-2.0.so.0 #4 0x048a54b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x00f5e60f in QEventDispatcherGlib::processEvents (this=0x8bffc48, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #6 0x00f31059 in QEventLoop::processEvents (this=0xb12d2270, flags=) at kernel/qeventloop.cpp:149 #7 0x00f314aa in QEventLoop::exec (this=0xb12d2270, flags=...) at kernel/qeventloop.cpp:201 #8 0x00e2d5a8 in QThread::exec (this=0x8b92c30) at thread/qthread.cpp:487 #9 0x00f10c1b in QInotifyFileSystemWatcherEngine::run (this=0x8b92c30) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x00e3032e in QThreadPrivate::start (arg=0x8b92c30) at thread/qthread_unix.cpp:248 #11 0x07f2596e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #12 0x00aa6a4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb77f4990 (LWP 19751)): [KCrash Handler] #6 QLineEdit::text (this=0x12) at widgets/qlineedit.cpp:377 #7 0xb438b2fb in ?? () from /usr/lib/libkmailprivate.so.4 #8 0xb4390004 in ?? () from /usr/lib/libkmailprivate.so.4 #9 0xb437fd5c in ?? () from /usr/lib/libkmailprivate.so.4 #10 0xb437fc40 in ?? () from /usr/lib/libkmailprivate.so.4 #11 0x00f37c9a in QMetaObject::metacall (object=0x8c4f688, cl=3030192116, idx=76, argv=0xbf84e63c) at kernel/qmetaobject.cpp:237 #12 0x00f463d5 in QMetaObject::activate (sender=0x8c4f688, m=0x70bb04, local_signal_index=9, argv=0x0) at kernel/qobject.cpp:3293 #13 0x004a7e27 in KDialog::okClicked (this=0x8c4f688) at ./kdialog.moc:258 #14 0x004aa438 in KDialog::slotButtonClicked (this=0x8c4f688, button=4) at ../../kdeui/dialogs/kdialog.cpp:862 #15 0x004ac559 in KDialog::qt_metacall (this=0x8c4f688, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbf84e868) at ./kdialog.moc:190 #16 0x0058986a in KPageDialog::qt_metacall (this=0x8c4f688, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbf84e868) at ./kpagedialog.moc:70 #17 0xb437fc1a in ?? () from /usr/lib/libkmailprivate.so.4 #18 0x00f37c9a in QMetaObject::metacall (object=0x8c4f688, cl=3030192116, idx=69, argv=0xbf84e868) at kernel/qmetaobject.cpp:237 #19 0x00f463d5 in QMetaObject::activate (sender=0x8bf1198, m=0x10450f8, local_signal_index=0, argv=0xbf84e868) at kernel/qobject.cpp:3293 #20 0x00f4bb13 in QSignalMapper::mapped (this=0x8bf1198, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:101 #21 0x00f4cd8d in QSignalMapper::map (this=0x8bf1198, sender=0x8b92b18) at kernel/qsignalmapper.cpp:266 #22 0x00f4cf6e in QSignalMapper::map (this=0x8bf1198) at kernel/qsignalmapper.cpp:257 #23 0x00f4d03b in QSignalMapper::qt_metacall (this=0x8bf1198, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf84ea08) at .moc/release-shared/moc_qsignalmapper.cpp:87 #24 0x00f37c9a in QMetaObject::metacall (object=0x8bf1198, cl=3030192116, idx=8, argv=0xbf84ea08) at kernel/qmetaobject.cpp:237 #25 0x00f463d5 in QMetaObject::activate (sender=0x8b92b18, m=0x6b3d8c4, local_signal_index=2, argv=0xbf84ea08) at kernel/qobject.cpp:3293 #26 0x0692d479 in QAbstractButton::clicked (this=0x8b92b18, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #27 0x0660cea9 in QAbstractButtonPrivate::emitClicked (this=0x8c4f8a0) at widgets/qabstractbutton.cpp:546 #28 0x0660dcf4 in QAbstractButtonPrivate::click (this=0x8c4f8a0) at widgets/qabstractbutton.cpp:539 #29 0x0660dfae in QAbstractButton::mouseReleaseEvent (this=0x8b92b18, e=0xbf84f140) at widgets/qabstractbutton.cpp:1121 #30 0x062607f8 in QWidget::event (this=0x8b92b18, event=0xbf84f140) at kernel/qwidget.cpp:7998 #31 0x0660cd4e in QAbstractButton::event (this=0x8b92b18, e=0xbf84e4d8) at widgets/qabstractbutton.cpp:1080 #32 0x066b71f2 in QPushButton::event (this=0x8b92b18, e=0xbf84f140) at widgets/qpushbutton.cpp:679 #33 0x062024dc in QApplicationPrivate::notify_helper (this=0x8248f10, receiver=0x8b92b18, e=0xbf84f140) at
[Bug 185820] kMail does not terminate after quitting it
https://bugs.kde.org/show_bug.cgi?id=185820 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl --- Comment #3 from Piotr Keplicz keplicz cmc pl 2009-11-18 21:51:37 --- This bug can be still experienced on KDE 4.3.3 (and earlier 4.3 versions). After quitting Kontact, there are some processes left: kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket kdeinit4: kio_imap4 [kdeinit] imaps local:/tmp/ksocket kdeinit4: kio_pop3 [kdeinit] pop3 local:/tmp/ksocket One cannot start Kontact again without killall kontact first. -- 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 204840] New: auto adjust column size
https://bugs.kde.org/show_bug.cgi?id=204840 Summary: auto adjust column size Product: kmail Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: el...@wp.pl Version:(using KDE 4.3.0) OS:Linux Installed from:Unlisted Binary Package Right clicking on columns in message view has adjust column size option, but it should be checkbox, and on every window size change, the option should automatically adjust columns on size change. Try to open small window of kmail, adjust, close it, open again and you've to adjust again. It is quite annoying. -- 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 196597] New: While clicking the image in akregator screenshot preview, to close it whole kontact application crashed.
https://bugs.kde.org/show_bug.cgi?id=196597 Summary: While clicking the image in akregator screenshot preview, to close it whole kontact application crashed. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: beln...@gmail.com Application that crashed: kontact Version of the application: 4.3.0 pre KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-13-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: Steps to reproduce the crash: 1. Open akregator within the kontact 2. I have subscribed kde-look news feeds 3. mark any article and klick details 4. Click zoom on preview link 5. Click on the opened preview image ( in browser it closes it) - crash System details: Kubuntu 9.04, 32 bit KDE 4.2.4 from repository: deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu jaunty main All other updates aplied. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb5b7047a in QObjectPrivate::cleanConnectionLists () from /usr/lib/libQtCore.so.4 #7 0xb5b75f8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #8 0xb5b760e0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #9 0xb5b7616b in QObject::destroyed () from /usr/lib/libQtCore.so.4 #10 0xb5b76fa9 in QObject::~QObject () from /usr/lib/libQtCore.so.4 #11 0xb70ac11e in KParts::Part::~Part () from /usr/lib/libkparts.so.4 #12 0xb70ac44a in KParts::ReadOnlyPart::~ReadOnlyPart () from /usr/lib/libkparts.so.4 #13 0xb79f9117 in KHTMLPart::~KHTMLPart () from /usr/lib/libkhtml.so.5 #14 0xb5b6eb25 in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4 #15 0xb5b703cb in QObject::event () from /usr/lib/libQtCore.so.4 #16 0xb603fe9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #17 0xb604819e in QApplication::notify () from /usr/lib/libQtGui.so.4 #18 0xb6c65e8d in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb5b5fa3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #20 0xb5b60695 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #21 0xb5b6088d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #22 0xb5b8b7ef in ?? () from /usr/lib/libQtCore.so.4 #23 0xb4c25b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb4c290eb in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb4c29268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb5b8b438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #27 0xb60e1365 in ?? () from /usr/lib/libQtGui.so.4 #28 0xb5b5e06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #29 0xb5b5e4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #30 0xb5b60959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #31 0xb603fd17 in QApplication::exec () from /usr/lib/libQtGui.so.4 #32 0x0804bfef in _start () Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 178949] kontact crash on logout
https://bugs.kde.org/show_bug.cgi?id=178949 --- Comment #3 from Piotr Keplicz keplicz cmc pl 2009-03-09 18:06:14 --- Created an attachment (id=31952) -- (http://bugs.kde.org/attachment.cgi?id=31952) kontact crash backtrace I get similar crashes here with KDE 4.2.1, Kontact 1.4.1, Qt 4.4.3 on Ubuntu 8.10. -- 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 178949] kontact crash on logout
https://bugs.kde.org/show_bug.cgi?id=178949 Piotr Keplicz kepl...@cmc.pl changed: What|Removed |Added CC||kepl...@cmc.pl -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
