[kmail2] [Bug 368060] Replying to html email that has a PDF attachment creates junk in the reply
https://bugs.kde.org/show_bug.cgi?id=368060 Ianchanged: What|Removed |Added Resolution|LATER |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368060] Replying to html email that has a PDF attachment creates junk in the reply
https://bugs.kde.org/show_bug.cgi?id=368060 Ianchanged: What|Removed |Added Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED --- Comment #2 from Ian --- closing account so closing bugs -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |LATER -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359862] Duplication of emails
https://bugs.kde.org/show_bug.cgi?id=359862 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |LATER --- Comment #6 from Ian --- closing, not sure if its been looked at but its ongoing and is known about -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362813] View of Unread count column not viewed very well
https://bugs.kde.org/show_bug.cgi?id=362813 Ianchanged: What|Removed |Added Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED --- Comment #6 from Ian --- closing, not sure if its been looked at but have changed versions since this was logged -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359946] "Filter Actions" list box badly presented
https://bugs.kde.org/show_bug.cgi?id=359946 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Ian --- closing, not sure if its been looked at but have changed versions since this was logged -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 332522] Using Cut and Paste changes format of email
https://bugs.kde.org/show_bug.cgi?id=332522 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Ian --- closing, not sure if its been looked at but have changed versions since this was logged -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 --- Comment #6 from Ian--- No news as far as i know, can't even tell if anyone has looked at it -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368016] Kmail2 (v5.3.0) Crash at will on startup
https://bugs.kde.org/show_bug.cgi?id=368016 Ianchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Ian --- closing, not sure if its been looked at but have changed versions since this was logged -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368016] Kmail2 (v5.3.0) Crash at will on startup
https://bugs.kde.org/show_bug.cgi?id=368016 Ianchanged: What|Removed |Added Severity|crash |grave -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 --- Comment #3 from Ian--- More crashes opensuse:tumbleweed:20160917; Qt: 5.6.1; KDE Frameworks: 5.26.0; KDE Plasma: 5.7.95 kwin5-5.7.95-154.1.x86_64; kmail5-16.08.1-82.2.x86_64; Kernel: 4.7.3-1-default; Nouveau: 1.0.12_1.4 ~> kmail Pass a valid window to KWallet::Wallet::openWallet(). void AdblockManager::reloadConfig() false AdBlock::AdblockManager(0x1836340) this does not work on a KActionCollection containing actions! org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: Subtree: 2 QSet(5, 4, 3, 2, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6) org.kde.akonadi.ETM: collection: "inbox" org.kde.akonadi.ETM: Fetch job took 295 msec org.kde.akonadi.ETM: was collection fetch job: collections: 14 org.kde.akonadi.ETM: first fetched collection: "Local Folders" org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 342 msec org.kde.akonadi.ETM: was collection fetch job: collections: 2 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 153 msec org.kde.akonadi.ETM: was item fetch job: items: 12 org.kde.akonadi.ETM: Fetch job took 167 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: collection: "opensuse.kde" org.kde.akonadi.ETM: Fetch job took 82 msec org.kde.akonadi.ETM: was item fetch job: items: 445 org.kde.akonadi.ETM: collection: "opensuse.org" org.kde.akonadi.ETM: Fetch job took 312 msec org.kde.akonadi.ETM: was item fetch job: items: 4042 org.kde.akonadi.ETM: collection: "KDE PIM" org.kde.akonadi.ETM: Fetch job took 263 msec org.kde.akonadi.ETM: was item fetch job: items: 3107 org.kde.akonadi.ETM: collection: "Hardware" org.kde.akonadi.ETM: Fetch job took 58 msec org.kde.akonadi.ETM: was item fetch job: items: 53 org.kde.akonadi.ETM: collection: "KDE" org.kde.akonadi.ETM: Fetch job took 67 msec org.kde.akonadi.ETM: was item fetch job: items: 156 org.kde.akonadi.ETM: collection: "Tumbleweed Factory" org.kde.akonadi.ETM: Fetch job took 244 msec org.kde.akonadi.ETM: was item fetch job: items: 2913 Invalid address sonnet.core: deleting 0x40f51c0 for "en_GB" sonnet.core: Unhandled script 126 sonnet.core: Unhandled script 127 sonnet.core: Unhandled script 128 sonnet.core: Unhandled script 129 sonnet.core: Unhandled script 130 sonnet.core: deleting 0x4b13c00 for "en_GB" sonnet.core: deleting 0x4b1dd68 for "en_GB" sonnet.core: deleting 0x4e81f50 for "en_GB" sonnet.core: deleting 0x4e82348 for "en_GB" sonnet.core: deleting 0x4b1c450 for "en_GB" sonnet.core: deleting 0x4b1e588 for "en_GB" sonnet.core: deleting 0x4b193e0 for "en_GB" sonnet.core: deleting 0x4e81da8 for "en_GB" *** KMail got signal 11 (Exiting) *** Dead letters dumped. KCrash: Application 'kmail' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1004/kdeinit5__0 Unable to start Dr. Konqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 --- Comment #2 from Ian--- More crashes ~> kmail Pass a valid window to KWallet::Wallet::openWallet(). void AdblockManager::reloadConfig() false AdBlock::AdblockManager(0x1684610) this does not work on a KActionCollection containing actions! org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: Subtree: 2 QSet(9, 8, 7, 6, 5, 4, 3, 2, 15, 14, 13, 12, 11, 10) org.kde.akonadi.ETM: collection: "inbox" org.kde.akonadi.ETM: Fetch job took 310 msec org.kde.akonadi.ETM: was collection fetch job: collections: 14 org.kde.akonadi.ETM: first fetched collection: "Local Folders" org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 363 msec org.kde.akonadi.ETM: was collection fetch job: collections: 2 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 179 msec org.kde.akonadi.ETM: was item fetch job: items: 12 org.kde.akonadi.ETM: Fetch job took 117 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: collection: "Tumbleweed Factory" org.kde.akonadi.ETM: Fetch job took 272 msec org.kde.akonadi.ETM: was item fetch job: items: 2914 void AdblockManager::reloadConfig() false AdBlock::AdblockManager(0x2dc4d80) this does not work on a KActionCollection containing actions! Invalid address sonnet.core: deleting 0x1b28870 for "en_GB" sonnet.core: Unhandled script 126 sonnet.core: Unhandled script 127 sonnet.core: Unhandled script 128 sonnet.core: Unhandled script 129 sonnet.core: Unhandled script 130 sonnet.core: deleting 0x3515930 for "en_GB" sonnet.core: deleting 0x352fee8 for "en_GB" sonnet.core: deleting 0x7ffd094b12c0 for "en_GB" sonnet.core: deleting 0x7ffd094b10a0 for "en_GB" sonnet.core: deleting 0x7ffd094b1120 for "en_GB" sonnet.core: deleting 0x7ffd094b10e0 for "en_GB" sonnet.core: deleting 0x7ffd094b1160 for "en_GB" sonnet.core: deleting 0x2e14570 for "en_GB" sonnet.core: deleting 0x2e18fe8 for "en_GB" sonnet.core: deleting 0x352c800 for "en_GB" sonnet.core: deleting 0x3530bc8 for "en_GB" org.kde.akonadi.ETM: collection: "opensuse.org" org.kde.akonadi.ETM: Fetch job took 386 msec org.kde.akonadi.ETM: was item fetch job: items: 4044 *** KMail got signal 11 (Exiting) *** Dead letters dumped. [0920/103726:ERROR:gles2_cmd_decoder.cc(12615)] [GroupMarkerNotSet(crbug.com/242999)!:380014B4C27F]GL ERROR :GL_OUT_OF_MEMORY : glTexStorage2DEXT: [0920/103726:FATAL:scoped_file.cc(29)] Check failed: 0 == IGNORE_EINTR(close(fd)). : Bad file descriptor Unable to start Dr. Konqi Unable to start Dr. Konqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368445] New: kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 Bug ID: 368445 Summary: kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Been running kmail from the cli (as it doesn't seem to crash as much)and when i click on a folder to read an unread email, it crashes - not every time but a heck of a lot of times, and the this message "[warn] epoll_wait: Bad file descriptor" is repeatedly displayed on konsole when it crashes. There are so many of these messages i can't scroll back to the point where i launched kmail to see if there is a more important message that caused the crash. Reproducible: Sometimes Steps to Reproduce: 1. run kmail2 2. click on folder with unread emails 3. Actual Results: kmail2 crashes out, sometimes it loads drkonqi and sometimes it just crashes Expected Results: not to crash Qt: 5.6.1 KDE Frameworks: 5.25.0 kf5-config: 1.0 KDE Plasma: 5.7.4 Kwin5: 5.7.4-152.2 Kernel: 4.7.2-2-default opensuse:tumbleweed:20160905 Nouveau: 1.0.12-1.4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368060] New: Replying to html email that has a PDF attachment creates junk in the reply
https://bugs.kde.org/show_bug.cgi?id=368060 Bug ID: 368060 Summary: Replying to html email that has a PDF attachment creates junk in the reply Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Received an email that is in HTML and had a PDF attached. I pressed reply, and it took a while to create the reply window that eventually contained the original text plus a whole load of garbage which i assume is a dump of the PDF attachment Reproducible: Always Steps to Reproduce: 1. Reply to html email with PDF attached (make sure "Prefer HTML to plain text" is NOT set 2. 3. Actual Results: creates a reply window containing the original text plus a whole load of garbage which i assume is a dump of the PDF attachment Expected Results: Create a reply window only containing the original text -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368016] Kmail2 (v5.3.0) Crash at will on startup
https://bugs.kde.org/show_bug.cgi?id=368016 --- Comment #1 from Ian--- *** Bug 367632 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 Ianchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #7 from Ian --- duplicate of 368016 *** This bug has been marked as a duplicate of bug 368016 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368016] New: Kmail2 (v5.3.0) Crash at will on startup
https://bugs.kde.org/show_bug.cgi?id=368016 Bug ID: 368016 Summary: Kmail2 (v5.3.0) Crash at will on startup Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160812) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: All i had done was load kmail2 and it displayed everything as normal, i didn;t have chance to click on anything The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fceca853940 (LWP 4257))] Thread 34 (Thread 0x7fcdb1cac700 (LWP 4350)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fceb3960129 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fceb3960840 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fceb3960a10 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fceb395d5cd in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcebd488474 in start_thread (arg=0x7fcdb1cac700) at pthread_create.c:333 #6 0x7fcec75fa3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7fce33dab700 (LWP 4343)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fceae425fc4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fceae426009 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fcebd488474 in start_thread (arg=0x7fce33dab700) at pthread_create.c:333 #4 0x7fcec75fa3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 32 (Thread 0x7fce34e10700 (LWP 4331)): #0 0x7fcec75f1a1d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcebcc65036 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcebcc6514c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcec8134aeb in QEventDispatcherGlib::processEvents (this=0x7fce4c002b40, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fcec80dc76a in QEventLoop::exec (this=this@entry=0x7fce34e0fc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fcec7f023b3 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fcec7f072d8 in QThreadPrivate::start (arg=0x3378800) at thread/qthread_unix.cpp:341 #7 0x7fcebd488474 in start_thread (arg=0x7fce34e10700) at pthread_create.c:333 #8 0x7fcec75fa3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 31 (Thread 0x7fce3583b700 (LWP 4320)): #0 0x7fff433c4989 in ?? () #1 0x7fff433c4c61 in clock_gettime () #2 0x7fcec76070a6 in __GI___clock_gettime (clock_id=1, tp=tp@entry=0x7fce3583a9e0) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fcec7fb2d96 in qt_clock_gettime (ts=0x7fce3583a9e0, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0x7fcec8132699 in QTimerInfoList::updateCurrentTime (this=this@entry=0x32da540) at kernel/qtimerinfo_unix.cpp:84 #7 0x7fcec8132c45 in QTimerInfoList::timerWait (this=0x32da540, tm=...) at kernel/qtimerinfo_unix.cpp:381 #8 0x7fcec8133fde in timerSourcePrepareHelper (timeout=0x7fce3583aab4, src=) at kernel/qeventdispatcher_glib.cpp:126 #9 timerSourcePrepare (source=, timeout=0x7fce3583aab4) at kernel/qeventdispatcher_glib.cpp:159 #10 0x7fcebcc64589 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #11 0x7fcebcc64f5b in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x7fcebcc6514c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x7fcec8134aeb in QEventDispatcherGlib::processEvents (this=0x32da390, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #14 0x7fcec80dc76a in QEventLoop::exec (this=this@entry=0x7fce3583ac80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x7fcec7f023b3 in QThread::exec (this=) at thread/qthread.cpp:500 #16 0x7fcec7f072d8 in QThreadPrivate::start (arg=0x32d7140) at thread/qthread_unix.cpp:341 #17 0x7fcebd488474 in start_thread (arg=0x7fce3583b700) at pthread_create.c:333 #18 0x7fcec75fa3ed in clone
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 --- Comment #6 from Ian--- (In reply to Denis Kurz from comment #5) > The crash happens deep down in some OpenGL context in the nouveau driver. > Does this still happen if you use the nvidia driver instead of the nouveau > one? Also, which version of nouveau do you use when this crash occurs? Can > you test it with another version? Which version of Qt do you have installed? > I assume you are on openSuSE Tumbleweed? I've not used nvidia blob since i've been on Tumbleweed now but i will give it a go later today and update this bug report. My current releases are:- Nouveau 1.0.12-1.3-x86_64 Qt: 5.6.1 KDE Frameworks: 5.25.0 kf5-config: 1.0 KDE Plasma: 5.7.3 Kernel: 4.7.1-1-default "openSUSE Tumbleweed (20160822) (x86_64)" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 364220] Crash after downloading mails
https://bugs.kde.org/show_bug.cgi?id=364220 --- Comment #4 from Ian--- (In reply to wurfbaum from comment #3) > had the same problems after updating to the newest packages of opensuse > tumbleweed. > Akonadiserver always restarts with the following message: > Database "akonadi" opened using driver "QMYSQL" > Executing search "searchUpdate-1472078875" > searchUpdateResultsAvailable 270 0 results > Got 0 results, out of which 0 are already in the collection > Added 0 > Search done "searchUpdate-1472078875" (without remote search) > Search update finished > All results: 0 > Removed results: 0 > Executing search "searchUpdate-1472078875" > log_akonadiplugin_indexer: unknown term "attachment" > "[\n0: akonadiserver() [0x574fe6]\n1: akonadiserver() [0x575300]\n2: > /lib64/libc.so.6(+0x349f0) [0x7f7589a619f0]\n3: [0x7f7560050030]\n]\n" > ProcessControl: Application 'akonadiserver' returned with exit code 255 > (Unknown error) > > > So i thougt it might have to do something with email Search. > I went to Kontact Search Folder and deleted the folder "last search". This > brings Kontact to crash. But after starting Kontact again the problem with > akonadiserver restart was gone. > > To verify i did again in Kontact a search, after this i had the same > behaviour. Akonadiserver begins to restart again. After delete the last > search folder again akonadiserver is stable. > > Regards, > Thomas Cheers Thomas, that seems to work for me as well. kmail still crashes for other reasons though -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 364220] Crash after downloading mails
https://bugs.kde.org/show_bug.cgi?id=364220 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #2 from Ian --- Just had pages and pages of this warning on kmail 5.3.0 using Qt: 5.6.1 KDE Frameworks: 5.25.0 kf5-config: 1.0 KDE Plasma: 5.7.3 Kernel: 4.7.1-1-default "openSUSE Tumbleweed (20160820) (x86_64)" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363085] kmail window fails to display/load on second start
https://bugs.kde.org/show_bug.cgi?id=363085 --- Comment #17 from Ian--- (In reply to Fred Wells from comment #16) > I'm having the same issue with Fedora (24) ... > KMail: 5.2.3 > KDE Frameworks: 5.25.0 > Qt 5.6.1 (built against 5.6.1) > KDE Plasma: 5.25.0 > Kernel: 4.6.6-300 untick "Empty Wastebin on Exit" as this causes the problem. Log out or run up System Activity and kill the kmail process. its fixed in 5.3.0 but 5.3.0 has more serious issues at the moment which may be related to something else -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 --- Comment #4 from Ian--- Also getting this in the journal at times when kmail crashes Process 5497 (QtWebEngineProc) of user 1040 dumped core. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359862] Duplication of emails
https://bugs.kde.org/show_bug.cgi?id=359862 --- Comment #5 from Ian--- Still happening in kmail 5.3.0 Qt: 5.6.1 KDE Frameworks: 5.25.0 KDE Plasma: 5.7.3 Kernel: 4.7.0-2-default "openSUSE Tumbleweed (20160818) (x86_64)" -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 --- Comment #3 from Ian--- kmail-20160822-112036.kcrash.txt - -what i was doing to create this file - load kmail2, open mailing list folder, highlight duplicate email, press "move to wastebin" then crash -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 --- Comment #2 from Ian--- Created attachment 100707 --> https://bugs.kde.org/attachment.cgi?id=100707=edit kmail devel info after crash -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #18 from Ian --- i've got akonadi restarting itself when feels like as well and kmail2 also crashes with seg fault 11 but i don;t know if they are related. I've only had this issue since kmail2 ver 5.3.0 was downloaded and installed. i've logged it here https://bugs.kde.org/show_bug.cgi?id=367632 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 --- Comment #1 from Ian--- If i use journalctl, i get these messages more or less at the time of failure (but not always) Process 3243 (akonadiserver) of user 1004 dumped core. Process 1580 (akonadiserver) of user 1004 dumped core. Process 2580 (QtWebEngineProc) of user 1004 dumped core. Process 2257 (akonadiserver) of user 1004 dumped core. Process 3270 (kmail) of user 1004 dumped core. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367632] New: Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 Bug ID: 367632 Summary: Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk It just crashes at will, no consistency as to when it happens or what you are doing at the time. i've had it crash when its downloading and filtering the emails to correct folders at start up, when i've clicked on one to open it, just scrolling down the email list etc etc. I cant even get teh crash handler to help as it hangs up getting debug symbols and when you cancel that, it also crashes and drkonqi seg faults 11 as well Reproducible: Always Steps to Reproduce: 1. run kmail2 Ver 5.3.0 2. Just wait or read some emails or just scan the folders 3. Actual Results: crashes either in a way where you can restart the program or it locks the desktop completely and you need to reboot the pc Expected Results: be able to read/write emails without crashing I did install kmail2-debuginfo but that seems of no use as the crash handler crashes -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362499] Kmail2 does not empty wastebin on exit when config option set on.
https://bugs.kde.org/show_bug.cgi?id=362499 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ian --- Fixed in 5.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #10 from Ian--- thanks -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 363085] kmail window fails to display/load on second start
https://bugs.kde.org/show_bug.cgi?id=363085 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #15 from Ian --- kmail 5.2.3 still not loading GUI after a quit with "Empty Wastebin on Exit" set to on Qt: 5.6.1 KDE Frameworks: 5.24.0 KDE Plasma: 5.7.1 Kernel: 4.6.3-1-default "openSUSE Tumbleweed (20160712) (x86_64)" seems bugs 361679, 358216 are duplicates -- 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 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #8 from Ian --- (In reply to Jonathan Marten from comment #7) > Possible duplicates: bug 363085, bug 361679. I'd agree with duplicates kmail 5.2.3 still not loading GUI after a quit with "Empty Wastebin on Exit" set to on Qt: 5.6.1 KDE Frameworks: 5.24.0 KDE Plasma: 5.7.1 Kernel: 4.6.3-1-default "openSUSE Tumbleweed (20160712) (x86_64)" -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #20 from Ian--- (In reply to Ian from comment #19) > kmail 5.2.3 still unable to reload unless you go into System Activity and > first kill the kmail instance that is still running. (Still does not empty > wastebin on exit) > > Qt: 5.6.1 > KDE Frameworks: 5.24.0 > KDE Plasma: 5.7.1 > Kernel: 4.6.3-1-default > "openSUSE Tumbleweed (20160712) (x86_64)" Sorry, it doesn't crash on exit, its the failure to reload on restarting kmail2 - I'll check for another bug report for it and create on if i can't find one. -- 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 362499] Kmail2 does not empty wastebin on exit when config option set on.
https://bugs.kde.org/show_bug.cgi?id=362499 --- Comment #3 from Ian--- Still does not empty wastebin in kmail 5.2.3 Qt: 5.6.1 KDE Frameworks: 5.24.0 KDE Plasma: 5.7.1 Kernel: 4.6.3-1-default "openSUSE Tumbleweed (20160712) (x86_64)" -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #19 from Ian--- kmail 5.2.3 still unable to reload unless you go into System Activity and first kill the kmail instance that is still running. (Still does not empty wastebin on exit) Qt: 5.6.1 KDE Frameworks: 5.24.0 KDE Plasma: 5.7.1 Kernel: 4.6.3-1-default "openSUSE Tumbleweed (20160712) (x86_64)" -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #17 from Ian--- (In reply to Laurent Montel from comment #16) > yep it's still empty trash on exit I've got this bug open https://bugs.kde.org/show_bug.cgi?id=362499 about trash not being emptied on exit with kmail 5.22. Tried it again today and it still doesn't so i'll keep it open until i've checked 5.23 which i hope will be soon. thanks 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
[kmail2] [Bug 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #15 from Ian--- (In reply to Laurent Montel from comment #14) > Git commit 544f8cd337d7179cf51cd908f012431243760ad1 by Montel Laurent. > Committed on 30/06/2016 at 18:42. > Pushed by mlaurent into branch 'Applications/16.04'. > > Fix Bug 358679 - kmail5 crash on reload when config to empty trash on exit > > FIXED-IN: 5.2.3 > > M +1-6kmail/kmkernel.cpp > > http://commits.kde.org/kdepim/544f8cd337d7179cf51cd908f012431243760ad1 Great, thanks. Does that also mean that trash is emptied on exit as well? -- 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 362499] Kmail2 does not empty wastebin on exit when config option set on.
https://bugs.kde.org/show_bug.cgi?id=362499 --- Comment #2 from Ian--- Still does not empty wastebin in kmail 5.2.2 KDE Frameworks 5.23.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system -- 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 359946] "Filter Actions" list box badly presented
https://bugs.kde.org/show_bug.cgi?id=359946 --- Comment #1 from Ian--- No change in kmail 5.2.2 KDE Frameworks 5.23.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system -- 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 359862] Duplication of emails
https://bugs.kde.org/show_bug.cgi?id=359862 --- Comment #4 from Ian--- Still happening in kmail 5.22 KDE Frameworks 5.23.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system but running "akonadictl vacuum" and "akonadictl fsck" seem to clear it up for a few days -- 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 362813] View of Unread count column not viewed very well
https://bugs.kde.org/show_bug.cgi?id=362813 --- Comment #5 from Ian--- Still the same in kmail 5.22 KDE Frameworks 5.23.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system -- 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 348817] New Mail notify message appears when no messages retrieved
https://bugs.kde.org/show_bug.cgi?id=348817 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ian --- Seems to have been fixed -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 361174] Kmail crash while viewing
https://bugs.kde.org/show_bug.cgi?id=361174 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Ian --- No worries, wasn't logged in -- 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 358682] Kontact 5
https://bugs.kde.org/show_bug.cgi?id=358682 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #13 from Ian--- Still happens with Version 5.2.2, KDE Frameworks 5.23.0, QT 5.6.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
[Akonadi] [Bug 309474] akonadictl fsck : item has no RID
https://bugs.kde.org/show_bug.cgi?id=309474 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #1 from Ian --- Still happening in 2016 with the latest software -- 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 362813] View of Unread count column not viewed very well
https://bugs.kde.org/show_bug.cgi?id=362813 --- Comment #3 from Ian--- (In reply to Maurice Batey from comment #2) > Have found that if now Disable the Unread Column, Unread counts are > appearing after folder names. > > (They didn't *before* I enabled the Unread Column) I never had a problem with that, i always had the counts after the folder names without the Unread column, I'm sure that is the default view after initial installation, -- 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 362813] New: View of Unread count column not viewed very well
https://bugs.kde.org/show_bug.cgi?id=362813 Bug ID: 362813 Summary: View of Unread count column not viewed very well Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk If i right click "Name" and click Unread to show the Unread column, the new column is not visible until i widen the view after setting the option. If i widen the folder view to allow space to show the Unread column before i set the option on, it is still not visible, you have to widen the view again after setting it on. Reproducible: Always Steps to Reproduce: 1. right click "Name" and click Unread to show the Unread column 2. You have to re-size the folder view to show the column. 3. Actual Results: Unread column does not show until you resize the folder view. I can resize the folder view to cover 75% of the width of the screen and then set the option on Unread, it still will not show until you resize the view again. The problem is that you can only see the column after resizing the view, once you know this is the case, its not a problem, Expected Results: Right click "Name" and click Unread to show the Unread column. Unread column should be shown so you know it is active even if its not cosmetically to your liking at first showing. When you eventually see the column, the unread numbers are so far to the right they bump right up against the message pane separator, it would be better either centred or left justified. Kmail 5.2.0, KDE Frameworks 5.21.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system openSUSE Tumbleweed (20160504) (x86_64) -- 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 362787] Unread option seems to work in the opposite way
https://bugs.kde.org/show_bug.cgi?id=362787 --- Comment #3 from Ian--- (In reply to Laurent Montel from comment #2) > nope it works it creates a new column with unread value. > Resize header to show it yes, thanks for the email about it last night. -- 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 362787] Unread option seems to work in the opposite way
https://bugs.kde.org/show_bug.cgi?id=362787 --- Comment #1 from Ian--- Kmail 5.2.0, KDE Frameworks 5.21.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system openSUSE Tumbleweed (20160504) (x86_64) -- 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 362787] New: Unread option seems to work in the opposite way
https://bugs.kde.org/show_bug.cgi?id=362787 Bug ID: 362787 Summary: Unread option seems to work in the opposite way Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Right click "Name" above the folders and select "Unread", it no longer dispays an Unread count next to each folder. Reproducible: Always Steps to Reproduce: 1. Right click "Name" above the folders 2. select "Unread" in "View Columns" popup 3. Actual Results: This removes teh unread emails count next to the folders Expected Results: display count of unread emails in a folder Default is unset but it displays the count. -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #12 from Ian--- Created attachment 98705 --> https://bugs.kde.org/attachment.cgi?id=98705=edit strace of failure to reload kmail This is the trace of failure of rerunning kmail after kmail was quit previously when "Emprty wastebin on exit" is set. -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #11 from Ian--- I've logged the wastebin not emptying as Bug 362499 -- 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 362499] New: Kmail2 does not empty wastebin on exit when config option set on.
https://bugs.kde.org/show_bug.cgi?id=362499 Bug ID: 362499 Summary: Kmail2 does not empty wastebin on exit when config option set on. Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk If you set the config to empty wastebin on exit, then exit the program. When you manage to reload kmail2 (see Bug 358679 ), the wastebin folder is still full. The menu option to empty the wastebin works fine, but the folder does not get emptied on program exit. kmail 5.2.0, KDE Frameworks 5.21.0, Qt 5.5.1 (built against 5.5.1), The xcb windowing system, openSUSE Tumbleweed (20160422) (x86_64) Reproducible: Always Steps to Reproduce: 1. Select Setting/Configure Kmail/Misc 2. Set "Empty local wastebin folder on program exit" 3. Exit program. Actual Results: 1. Restart kmail (if you don't log out first, you will have to kill kmail as you cannot reload it until there is no instance sitting in memory - see Bug 358679 ) 2. Wastebin folder still full of emails Expected Results: 1. An empty wastebin folder This action also causes Bug 358679 on my Tumbleweed system -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #10 from Ian--- Problem still exists in 5.2.0. Waste bin is not emptied on exit Unable to reload kmail unless you go into System Activity and first kill the kmail instance that is still running. Can anyone give me a way to create some relevant info for the developers as this error does not crash with any messages even if i run kmail from the cli -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #9 from Ian--- How do i get a backtrace if drkonqi doesn;t come up? -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #7 from Ian--- This seems totally reproducable if you have "Empty wastebin on exit" set on. -- 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 361748] Kmail2 crashes upon opening of Mails by double-click
https://bugs.kde.org/show_bug.cgi?id=361748 --- Comment #3 from Ian--- (In reply to Robby Engelmann from comment #2) > after installing new package kdepim-addons the crash is gone and all works > fine again. thanks. i installed it yesterday for a different reason i.e missing View/Headers options. Seems a strange resolution where an addon fixes something that should work in its basic form. -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #6 from Ian--- (In reply to Laurent Montel from comment #5) > backtrace please as it's too different bug as first comment > Thanks It doesn;t crash in a way that i can get a back trace any more so i guess the failure is different. if i reload kmail, it shows it is loading on the taskbar then it disappears and nothing happens. if i call up System Activity with ctrl-esc, and filter the display by inputting kmail, it shows kmail is still loaded with 5 copies of "file.so" under kdeinit5. if i kill kmail via SystemActivity, i can then successfully reload kmail but the wastebin is still not emptied -- 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 361793] View/Headers menu does not show choices
https://bugs.kde.org/show_bug.cgi?id=361793 --- Comment #2 from Ian--- (In reply to Laurent Montel from comment #1) > Install kdepim-addons too. > Regards I've never had to do this before, is this new? -- 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 361793] New: View/Headers menu does not show choices
https://bugs.kde.org/show_bug.cgi?id=361793 Bug ID: 361793 Summary: View/Headers menu does not show choices Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Empty menu when selecting "View/Headers" Reproducible: Always Steps to Reproduce: 1. Click "View" menu 2. Click "Headers" from View menu 3. Actual Results: nothing gets displayed even though the ">" indicates there should be some options for Headers Expected Results: No choices displayed openSUSE Tumbleweed (20160412) kmail 5.1.90 rc KDE Frameworks 5.21.0 Qt 5.5.1 (built against 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #4 from Ian--- (In reply to Ian from comment #3) > Still an issue with kmail 5.1.90rc additional info openSUSE Tumbleweed (20160412) KDE Frameworks 5.21.0 Qt 5.5.1 (built against 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
[kontact] [Bug 357243] Crash during exit
https://bugs.kde.org/show_bug.cgi?id=357243 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Ian --- Closing this as its old and unloved -- 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 361639] Kmail Crashes when double clicking on message in the message list
https://bugs.kde.org/show_bug.cgi?id=361639 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #1 from Ian --- Agreed but i was using the version supplied by opensuse RPMs and "zypper dup" -- 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 361748] Kmail2 crashes upon opening of Mails by double-click
https://bugs.kde.org/show_bug.cgi?id=361748 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #1 from Ian --- I agree with this error and it is a duplicate of 361639 -- 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 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #3 from Ian--- Still an issue with kmail 5.1.90rc -- 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 361174] New: Kmail crash while viewing
https://bugs.kde.org/show_bug.cgi?id=361174 Bug ID: 361174 Summary: Kmail crash while viewing Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Application: kmail (5.1.3) Qt Version: 5.5.1 Frameworks Version: 5.20.0 Operating System: Linux 4.5.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160117) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: i had opened kmail, most of teh emails had been filtered off to other folders. i deleted the couple of spam emails left in the inbox and viewed the remaining "boucing emails" message. i then viewed some emails and marked threads as read in two of the other folders. i was just about to read the emails in the third folder when kmail crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff4722e1940 (LWP 1893))] Thread 19 (Thread 0x7ff44d088700 (LWP 1894)): #0 0x7ff46f31b43d in poll () from /lib64/libc.so.6 #1 0x7ff462348432 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7ff46234a007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7ff44edb0dd9 in QXcbEventReader::run (this=0x23a6440) at qxcbconnection.cpp:1229 #4 0x7ff46fc2190f in QThreadPrivate::start (arg=0x23a6440) at thread/qthread_unix.cpp:331 #5 0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0 #6 0x7ff46f323d8d in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7ff446ae3700 (LWP 1899)): #0 0x7ff46f31741d in read () from /lib64/libc.so.6 #1 0x7ff4651cf290 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff46518cdc4 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff46518d238 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff46518d39c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7ff46fe464db in QEventDispatcherGlib::processEvents (this=0x7ff448c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7ff46fdf05ca in QEventLoop::exec (this=this@entry=0x7ff446ae2c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7ff46fc1cadc in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7ff46fc2190f in QThreadPrivate::start (arg=0x246f230) at thread/qthread_unix.cpp:331 #9 0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0 #10 0x7ff46f323d8d in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7ff445c5e700 (LWP 1900)): #0 0x7ff46f31b43d in poll () from /lib64/libc.so.6 #1 0x7ff46518d294 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff46518d39c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff46fe464db in QEventDispatcherGlib::processEvents (this=0x7ff4380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff46fdf05ca in QEventLoop::exec (this=this@entry=0x7ff445c5dc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff46fc1cadc in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff46fc2190f in QThreadPrivate::start (arg=0x2507690) at thread/qthread_unix.cpp:331 #7 0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0 #8 0x7ff46f323d8d in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7ff44545d700 (LWP 1901)): #0 0x7ff4651d0554 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7ff46518d15d in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff46518d39c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff46fe464db in QEventDispatcherGlib::processEvents (this=0x7ff43c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff46fdf05ca in QEventLoop::exec (this=this@entry=0x7ff44545cc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff46fc1cadc in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff46fc2190f in QThreadPrivate::start (arg=0x2405c30) at thread/qthread_unix.cpp:331 #7 0x7ff4656aa454 in start_thread () from /lib64/libpthread.so.0 #8 0x7ff46f323d8d in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7ff444c5c700 (LWP 1904)): #0 0x7ff46f31741d in read () from /lib64/libc.so.6 #1 0x7ff4651cf290 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff46518cdc4 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff46518d238 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff46518d39c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7ff46fe464db in QEventDispatcherGlib::processEvents (this=0x7ff438c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7ff46fdf05ca in
[kmail2] [Bug 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 Ianchanged: What|Removed |Added Summary|kmail5 crash on reload |kmail5 crash on reload when ||config to empty trash on ||exit -- 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 359946] "Filter Actions" list box badly presented
https://bugs.kde.org/show_bug.cgi?id=359946 Ianchanged: What|Removed |Added Severity|wishlist|normal CC||ianse...@yahoo.co.uk -- 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 359946] New: "Filter Actions" list box badly presented
https://bugs.kde.org/show_bug.cgi?id=359946 Bug ID: 359946 Summary: "Filter Actions" list box badly presented Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk The "Filter Actions" list box always displays the list but its always the blank line at the bottom of the list that is shown by default, i would have thought the list should start at the top. I think "Move to Folder" would be the most used choice on a filter and should be at the top of the list, It also looks wrong with the last item in a selection list being highlighted. Reproducible: Always Steps to Reproduce: 1. Configure Filters 2. Create new filter 3. Set up Filter Criteria 4. Click on "Please select an action" Actual Results: The blank line at the bottom of the list is highlighted Expected Results: List presented with the first line at the top -- 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 359862] Duplication of emails
https://bugs.kde.org/show_bug.cgi?id=359862 --- Comment #2 from Ian--- Created attachment 97582 --> https://bugs.kde.org/attachment.cgi?id=97582=edit 2nd snapshot of folder with duplicates -- 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 359862] Duplication of emails
https://bugs.kde.org/show_bug.cgi?id=359862 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #1 from Ian --- Created attachment 97581 --> https://bugs.kde.org/attachment.cgi?id=97581=edit Snapshot of folder containing duplicates -- 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 359862] New: Duplication of emails
https://bugs.kde.org/show_bug.cgi?id=359862 Bug ID: 359862 Summary: Duplication of emails Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk I'm suffering an increase of duplicate emails in latest kmail on tumbleweed. It seems to fluctuate between quite a bit and a few duplications. I uses filters on incoming messages to file them in the correct folders. I get duplications of on first run of kmail of the day and repeated duplications of the same messages as well as new ones during later runs of kmail. Reproducible: Always Steps to Reproduce: 1. run kmail 2. check message folders after all emails downloaded and filtered 3. identify duplicates Actual Results: Ranges from a zero to quite a few and duplicates of duplicates Expected Results: No duplicates -- 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 359698] Wastebin does not get emptied when config set to empty on exit
https://bugs.kde.org/show_bug.cgi?id=359698 --- Comment #3 from Ian--- (In reply to RJVB from comment #1) > You should upload a backtrace for the crash, either through DrKonqi (which > *should* appear when a KDE application crashes) or else by running kmail > from within a debugger (type `gdb --args /usr/bin/kmail --nofork` or > something like that in a terminal, and then `bt` [without the quotes] when > the crash occurs) I did the backtrace from the error dialog that pops up -- 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 359698] Wastebin does not get emptied when config set to empty on exit
https://bugs.kde.org/show_bug.cgi?id=359698 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #2 from Ian --- Created attachment 97377 --> https://bugs.kde.org/attachment.cgi?id=97377=edit Backtrace for kmail2 crash on reload if i set Empty wastebin on exit, exited and reloaded. i get this error but kmail2 loads as usual and seems to work fine. -- 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 359698] New: Wastebin does not get emptied when config set to empty on exit
https://bugs.kde.org/show_bug.cgi?id=359698 Bug ID: 359698 Summary: Wastebin does not get emptied when config set to empty on exit Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk kmail2 Version 5.1.2 KDE Frameworks 5.19.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system Reproducible: Always Steps to Reproduce: 1. Set mkail config/misc/empty wastebin on exit to yes 2. Exit kmail2 3. Reload kmail2 4. check wastebin Actual Results: Kmail2 closes and does not empty wastebin, kmail2 will then crash on reload with this error "Executable: kmail PID: 22596 Signal: Segmentation fault (11) Time: 23/02/2016 11:44:41" but it still loads and is usable Expected Results: Empty wastebin on exit kmail2 not to crash on reload -- 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 359018] New: Pressing cancel does not undo changes made to "Empty local wastebin..." kmail2 v 5.1.1.
https://bugs.kde.org/show_bug.cgi?id=359018 Bug ID: 359018 Summary: Pressing cancel does not undo changes made to "Empty local wastebin..." kmail2 v 5.1.1. Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Set "Empty local wastebin folder on program exit" to on, Press "Cancel" button Reload "Configure Kmail/Misc" and selection is still set on instead of reverting to previous setting. -- 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 358679] kmail5 crash on reload
https://bugs.kde.org/show_bug.cgi?id=358679 Ianchanged: What|Removed |Added Severity|crash |major -- 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 358679] kmail5 crash on reload
https://bugs.kde.org/show_bug.cgi?id=358679 Ianchanged: What|Removed |Added CC||ianse...@yahoo.co.uk -- 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 348752] Kmail2 4.18.4 - does not get mail on startup as it used to.
https://bugs.kde.org/show_bug.cgi?id=348752 Ianchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |MOVED -- 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 358682] New: Kontact 5
https://bugs.kde.org/show_bug.cgi?id=358682 Bug ID: 358682 Summary: Kontact 5 Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Application: kontact (5.1.1) Qt Version: 5.5.1 Operating System: Linux 4.4.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20160117) (x86_64)" -- Information about the crash: i had been reconfiguring elements of this new update from kontact to kontact5 such as email layout, knotes, summary up and coming dates then i pressed exit via the menu -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc7ba2cd900 (LWP 15627))] Thread 40 (Thread 0x7fc79be38700 (LWP 15628)): #0 0x7fc7b6f4324d in poll () from /lib64/libc.so.6 #1 0x7fc7b06b8432 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fc7b06ba007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fc79df86e29 in QXcbEventReader::run (this=0x1e4bf00) at qxcbconnection.cpp:1229 #4 0x7fc7b784b94f in QThreadPrivate::start (arg=0x1e4bf00) at thread/qthread_unix.cpp:331 #5 0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6 Thread 39 (Thread 0x7fc798ec8700 (LWP 15629)): #0 0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc7b4ae53bb in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fc7b4ae53f9 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6 Thread 38 (Thread 0x7fc74ffd2700 (LWP 15630)): #0 0x7fc7afabc4d4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fc7afa78cd9 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7fc7afa79208 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc7afa7936c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fc7b7a7052b in QEventDispatcherGlib::processEvents (this=0x7fc7480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fc7b7a1a63a in QEventLoop::exec (this=this@entry=0x7fc74ffd1cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fc7b7846b1c in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fc7b784b94f in QThreadPrivate::start (arg=0x1f594e0) at thread/qthread_unix.cpp:331 #8 0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6 Thread 37 (Thread 0x7fc744054700 (LWP 15631)): #0 0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc74eade133 in cnd_wait (mtx=0x2013950, cond=0x2013978) at ../../../../include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0x2013950) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 thread_function (init_data=init_data@entry=0x20138a8) at lp_rast.c:805 #4 0x7fc74eaddfb7 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6 Thread 36 (Thread 0x7fc743853700 (LWP 15632)): #0 0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc74eade133 in cnd_wait (mtx=0x2013ab8, cond=0x2013ae0) at ../../../../include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0x2013ab8) at ../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 thread_function (init_data=init_data@entry=0x2013a10) at lp_rast.c:805 #4 0x7fc74eaddfb7 in impl_thrd_routine (p=) at ../../../../include/c11/threads_posix.h:87 #5 0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6 Thread 35 (Thread 0x7fc74237b700 (LWP 15633)): #0 0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc7b47f3764 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fc7b4b14441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7fc741b5b700 (LWP 15634)): #0 0x7fc7b029a07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc7b47f4793 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fc7b4b14441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fc7b02944a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fc7b6f4bbdd in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7fc72feff700 (LWP 15636)): #0
[kmail2] [Bug 358679] New: kmail5 crash on reload
https://bugs.kde.org/show_bug.cgi?id=358679 Bug ID: 358679 Summary: kmail5 crash on reload Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Application: kmail (5.1.1) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160117) (x86_64)" -- Information about the crash: I had been using newly installed kmail5, i change config to empty trash on exit, saved it, exited via File menu. It crashed on reloading. i relaoded to check teh trash was beiung emptied -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd1b08ab940 (LWP 32054))] Thread 11 (Thread 0x7fd18b675700 (LWP 32055)): #0 0x7fd1ad8e024d in poll () from /lib64/libc.so.6 #1 0x7fd1a0916432 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fd1a0918007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fd18d39de29 in QXcbEventReader::run (this=0x1067450) at qxcbconnection.cpp:1229 #4 0x7fd1ae1e894f in QThreadPrivate::start (arg=0x1067450) at thread/qthread_unix.cpp:331 #5 0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fd18936d700 (LWP 32068)): #0 0x7fd1ad8e024d in poll () from /lib64/libc.so.6 #1 0x7fd1a375b264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd1a375b36c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd1ae40d52b in QEventDispatcherGlib::processEvents (this=0x7fd17c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fd1ae3b763a in QEventLoop::exec (this=this@entry=0x7fd18936cc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd1ae1e3b1c in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fd1ae1e894f in QThreadPrivate::start (arg=0x10ea510) at thread/qthread_unix.cpp:331 #7 0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fd16d30f700 (LWP 32091)): #0 0x7fd1a3c7e07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd19e7813bb in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fd19e7813f9 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fd114a0d700 (LWP 32099)): #0 0x7fd1a3c7e07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd19e48f764 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fd19e7b0441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fd107fff700 (LWP 32100)): #0 0x7fd1a3c7e07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd19e490793 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fd19e7b0441 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fd10519e700 (LWP 32122)): #0 0x7fd1a379e4b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fd1a375a2d0 in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd1a375b135 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd1a375b36c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fd1ae40d52b in QEventDispatcherGlib::processEvents (this=0x7fd0f8007400, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fd1ae3b763a in QEventLoop::exec (this=this@entry=0x7fd10519dc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fd1ae1e3b1c in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fd1ae1e894f in QThreadPrivate::start (arg=0x1716540) at thread/qthread_unix.cpp:331 #8 0x7fd1a3c784a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fd1ad8e8bdd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fd10599f700 (LWP 32124)): #0 0x7ffe801ce999 in ?? () #1 0x7ffe801cecc5 in clock_gettime () #2 0x7fd1ad8f57d6 in clock_gettime () from /lib64/libc.so.6 #3 0x7fd1ae2941a6 in qt_clock_gettime (ts=0x7fd10599ea40, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0x7fd1ae40b0e9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x1559cc0) at
[kmail2] [Bug 358679] kmail5 crash on reload
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #1 from Ian--- kmail5 does actually load even though it gives this message. it seems to load okay if you logout but if you try to reload kmail5 in the same session it gives the error. if i unset the empty trash on exit, it doesn't seem to give this error. it might be that the error is happening trying to empty the trash. -- 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 358679] kmail5 crash on reload
https://bugs.kde.org/show_bug.cgi?id=358679 --- Comment #2 from Ian--- It doesn't empty the trash on exit even when set. It also says its kmail2 on the prompt for kwallet access and the bug reporter also logs it as kmail2 even though the help menu says Version 5.1.1 using: KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- 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 357243] New: Crash during exit
https://bugs.kde.org/show_bug.cgi?id=357243 Bug ID: 357243 Summary: Crash during exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Application: kontact (4.14.10) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.3-1-default x86_64 Distribution: "openSUSE Tumbleweed (20151124) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I had read a few emails without opening them (via message pane), updated the details of one contact, went back to email and changed folder to read some more unread emails, noticed there was a duplicate so i deleted it. then selected Exit -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6428e8f900 (LWP 3003))] Thread 4 (Thread 0x7f640a419700 (LWP 3004)): #0 0x7f642029007f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6425550de6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f6425550e19 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f642028a4a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6426331bdd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f63c9afe700 (LWP 3005)): #0 0x7f642029007f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f64252ba5e9 in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f64255788f6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f642028a4a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6426331bdd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f63b61f6700 (LWP 3053)): #0 0x7f642632924d in poll () from /lib64/libc.so.6 #1 0x7f641fcc1264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f641fcc136c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f6426b2526e in QEventDispatcherGlib::processEvents (this=0x7f63b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f6426af53e1 in QEventLoop::processEvents (this=this@entry=0x7f63b61f5ce0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6426af56f5 in QEventLoop::exec (this=this@entry=0x7f63b61f5ce0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f64269eea59 in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7f64269f123c in QThreadPrivate::start (arg=0x2719f00) at thread/qthread_unix.cpp:352 #8 0x7f642028a4a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f6426331bdd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f6428e8f900 (LWP 3003)): [KCrash Handler] #6 operator QItemSelectionModel* (this=) at ../../src/corelib/kernel/qpointer.h:78 #7 QAbstractItemView::selectionModel (this=0x5065676100343932) at itemviews/qabstractitemview.cpp:766 #8 0x7f63bb39bf8c in MailCommon::FolderTreeWidget::selectedCollections (this=) at /usr/src/debug/kdepim-4.14.10/mailcommon/folder/foldertreewidget.cpp:243 #9 0x7f63bba46ca0 in KMMainWidget::updateFolderMenu (this=0x2b4c610) at /usr/src/debug/kdepim-4.14.10/kmail/kmmainwidget.cpp:3928 #10 0x7f63bbb470ca in KMMainWidget::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffd96852c30) at /usr/src/debug/kdepim-4.14.10/build/kmail/moc_kmmainwidget.cpp:461 #11 0x7f6426b09f60 in QMetaObject::activate (sender=0x2b4c850, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3576 #12 0x7f6426b0f973 in QObject::event (this=0x2b4c850, e=) at kernel/qobject.cpp:1262 #13 0x7f642750ef1c in QApplicationPrivate::notify_helper (this=this@entry=0x243c390, receiver=receiver@entry=0x2b4c850, e=e@entry=0x7ffd96853030) at kernel/qapplication.cpp:4565 #14 0x7f64275159ec in QApplication::notify (this=this@entry=0x7ffd96853c50, receiver=receiver@entry=0x2b4c850, e=e@entry=0x7ffd96853030) at kernel/qapplication.cpp:4351 #15 0x7f642824165a in KApplication::notify (this=0x7ffd96853c50, receiver=0x2b4c850, event=0x7ffd96853030) at /usr/src/debug/kdelibs-4.14.14/kdeui/kernel/kapplication.cpp:311 #16 0x7f6426af6a1d in QCoreApplication::notifyInternal (this=0x7ffd96853c50, receiver=0x2b4c850, event=event@entry=0x7ffd96853030) at kernel/qcoreapplication.cpp:955 #17 0x7f6426b275cf in sendEvent (event=0x7ffd96853030, receiver=) at kernel/qcoreapplication.h:231 #18 QTimerInfoList::activateTimers (this=0x2447cf0) at kernel/qeventdispatcher_unix.cpp:636 #19 0x7f6426b248f1 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:193 #20 0x7f641fcc1097 in g_main_context_dispatch () from
[kmail2] [Bug 356634] New: Kmail Randomly Hangs On Email Deletion
https://bugs.kde.org/show_bug.cgi?id=356634 Bug ID: 356634 Summary: Kmail Randomly Hangs On Email Deletion Product: kmail2 Version: 4.14.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: i...@pairowoodies.com When deleting emails in my message list window, Kmail will frequently just "hang" on "moving messages" and will just remain on that. Sometimes, it's after deleting only three messages while other times I can delete a much larger number before it happens. When it does occur, the only resolution is to reboot my computer before I can do anything again with Kmail. Reproducible: Sometimes Steps to Reproduce: 1. Open Kmail 2. Delete some emails Actual Results: Kmail hangs on "Moving Message" and Kmail become unusable. Other messages cannot even be read. Expected Results: Kmail should just delete messages and there should be no performance issues. I have been using Kmail and KDE since 2001. This latest issue which happens regularly is causing me to unfortunately have to consider another email application as this is totally unusable for me. If there is some performance tweaks I can make and try, am willing to do so. I'm using OpenSuse Tumbleweed. -- 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 356634] Kmail Randomly Hangs On Email Deletion
https://bugs.kde.org/show_bug.cgi?id=356634 Ianchanged: What|Removed |Added CC||i...@pairowoodies.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs