[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 mark changed: What|Removed |Added CC||m...@markpreston.me -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 462023] Akonadi and KWin crashed when launching "icons" system settings
https://bugs.kde.org/show_bug.cgi?id=462023 Mark A Stevens changed: What|Removed |Added CC||marxtev...@netscape.net --- Comment #2 from Mark A Stevens --- I had this happen on 03 December 2022. I was restarting Firefox, which I run up to 9 Activities, with multiple tabs each. It had crashed overnight. GKRELLM crashed about the same time. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379509] Message not found
https://bugs.kde.org/show_bug.cgi?id=379509 --- Comment #2 from Mark Stanton --- I'm very pleased that it appears someone is now attending to reported bugs, but, as I said in my other report that has just been looked at, I was looking for an answer for this five years ago so, after not receiving a response for a long time, I simply stopped using KMail and therefore cannot reproduce the issue any more. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363400] Akonadi elements stop working with only slightly low memory
https://bugs.kde.org/show_bug.cgi?id=363400 --- Comment #2 from Mark Stanton --- Since the "while" you refer to is over six years, no, I can't reproduce this because, in frustration, I simply stopped using software that uses Akonadi. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 --- Comment #4 from Mark Fairbairn --- I too am seeing this on KMail 5.16.2 -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 Mark Fairbairn changed: What|Removed |Added CC||farcu...@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #89 from Mark Stanton --- This still doesn't work? Wow, I (too) reported this months ago. At risk of another "me too" reply, yes, me too. Evolution works just fine under KDE, with GoogleMail, and has address book and calendar, as the K-suite has, and doesn't have Akonadi, which is also a great plus. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412150] New: kmail2: Wrong "Expire unread messages after"-date
https://bugs.kde.org/show_bug.cgi?id=412150 Bug ID: 412150 Summary: kmail2: Wrong "Expire unread messages after"-date Product: kmail2 Version: 5.12.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: mark+...@nowiasz.de Target Milestone: --- SUMMARY When I added a new IMAP folder I wanted to set the expire date for "Expire unread messages after" to 90 days. After saving the value and checking again, I suddenly had a value of 21926 days. Checking my other folders this wrong value was set, too - at least something near it, like 22034 or so. There seems to be another problem with the expire settings - the folder where expired messsages should be stored are gone after saving the value, too. STEPS TO REPRODUCE 1. Set a New "Expire unread messages after"-Date (I think more than 30 days) 2. Save 3. Check the value again OBSERVED RESULT A ridiculous value, around 22000 days. EXPECTED RESULT The value I entered SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.5 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #39 from Mark Stanton --- It's "simply" Google's new API implementation, but no, I don't know why access hasn't been organised for KMail. Evolution has access to GMail. an ex-KMail user, due to this issue being the final straw. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #16 from Mark Stanton --- (In reply to Wolfgang Bauer from comment #13) > *** Bug 410027 has been marked as a duplicate of this bug. *** I am not convinced this (ie my bug entry 410027 being recorded as a duplicate of this bug) is correct. I am not trying to set up a new account. The account has been set up for years, and KMail has been functioning perfectly well accessing it until recently. It may be that the cause is the same, though. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410195] New: Archive fails
https://bugs.kde.org/show_bug.cgi?id=410195 Bug ID: 410195 Summary: Archive fails Product: kmail2 Version: 5.11.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@stantoncentral.co.uk Target Milestone: --- SUMMARY Mail archiving halts at first "message not found" warning (warning, not "error") and the whole of the rest of the archive is not made. STEPS TO REPRODUCE 1. Attempt folder archive on folder container a "message not found" message 2. 3. OBSERVED RESULT Only a small subset of the requested folder (& perhaps its sub-folders) is archived. EXPECTED RESULT All requested folders are archived. "Missing messages" might be noted, but should not stop the rest of the archive proceeding. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION These "message missing" messages are continually generated in my KMail (Kontact) setup, hence, waiting until the faulty message is pruned doesn't work as a strategy. I have never (four years of KMail use?) managed to get a full folder archive either from the menu or the automatic folder archiving. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 410030] Tags
https://bugs.kde.org/show_bug.cgi?id=410030 Mark Stanton changed: What|Removed |Added Product|kmail2 |kontact Component|misc|contacts -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410030] New: Tags
https://bugs.kde.org/show_bug.cgi?id=410030 Bug ID: 410030 Summary: Tags Product: kmail2 Version: 5.11.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: m...@stantoncentral.co.uk Target Milestone: --- SUMMARY Tags are difficult to use! There are several problems. 1. Creating a new tag from the tags dialog on a person's contact dialog. After creating the tag and returning to the list of tags, the newly created tag is not present. The dialog must be closed and re-opened to be used. 2. After creating a new tag, it is not present in the dropdown list of tags available from the tag text box above the list of contacts. Kontact must be closed and re-opened for the tag to be used. 3. It is difficult to use tags as a filter. On first use, every tag is set in the dropdown from the tag text box above the list of contacts. Selecting just one requires clicking every other one to unselect them. Although "All" is the initial state, there is no single click way to re-generate it, nor to "clear all". SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410027] Fails to connect to GMail - "disabled for this app"
https://bugs.kde.org/show_bug.cgi?id=410027 Mark Stanton changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 410027] New: Fails to connect to GMail - "disabled for this app"
https://bugs.kde.org/show_bug.cgi?id=410027 Bug ID: 410027 Summary: Fails to connect to GMail - "disabled for this app" Product: kmail2 Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: m...@stantoncentral.co.uk Target Milestone: --- SUMMARY Kmail (from Kontact) fails to connect to GMail account. Google reports Sign in with Google temporarily disabled for this app This app has not yet been verified by Google in order to use Google Sign in. STEPS TO REPRODUCE 1. Attempt to connect to GMail account 2. 3. OBSERVED RESULT Dialog with error message as above. EXPECTED RESULT Should connect and show email. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION Stopped working 17/7, I believe. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 --- Comment #3 from Mark Nowiasz --- > Where does it takes this ID from then? > How can I fix this so thath my KMail starts working again? Downgrading mariadb from 10.4.6 to 10.3.x provided a workaround for me - after downgrading kmail works again, so I guess kmail/akonadi is currently incompatible with mariadb 10.4. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 --- Comment #2 from Mark Nowiasz --- Could be related to mariadb 10.4.6, https://bugs.gentoo.org/688746 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224
--- Comment #1 from Mark Nowiasz ---
Same here - since upgrade to 5.11.2 kmail stopped getting new mail via IMAP, I
basically stopped working at all :-/
Using a different mailclient on the same IMAP acccount, everything is fine.
So, how can we make this work again? Right now kmail is dead in the water :-/
019-06-27T16:54:51 [CRITICAL] org.kde.pim.akonadiserver: Error code: "1452"
2019-06-27T16:54:51 [CRITICAL] org.kde.pim.akonadiserver: DB error: "Cannot
add or update a child row: a foreign key constraint fails
(`akonadi`.`pimitemflagrelation`, CONSTRAINT `pimitemflagrelation_ibfk_1`
FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE
ON UPDATE CASCADE)"
2019-06-27T16:54:51 [CRITICAL] org.kde.pim.akonadiserver: Error text: "Cannot
add or update a child row: a foreign key constraint fails
(`akonadi`.`pimitemflagrelation`, CONSTRAINT `pimitemflagrelation_ibfk_1`
FOREIGN KEY (`PimItem_id`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE
ON UPDATE CASCADE) QMYSQL3: Unable to execute statement"
2019-06-27T16:54:51 [CRITICAL] org.kde.pim.akonadiserver: Values: QMap((":0",
QVariant(qlonglong, 935132))(":1", QVariant(qlonglong, 1)))
2019-06-27T16:54:51 [CRITICAL] org.kde.pim.akonadiserver: Query: "INSERT INTO
PimItemFlagRelation (PimItem_id, Flag_id) VALUES (:0, :1)"
2019-06-27T16:54:51 [WARN ] org.kde.pim.akonadiserver: Failed to append flag
"\\SEEN" to Items (QVariant(qlonglong, 935132))
2019-06-27T16:54:51 [WARN ] org.kde.pim.akonadiserver: Error while handling
command CreateItem on connection akonadi_imap_resource_0 (0x562e30f4ba60)
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 409224] kmail not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Mark Nowiasz changed: What|Removed |Added CC||mark+...@nowiasz.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405340] Email template created in wrong place and not removable
https://bugs.kde.org/show_bug.cgi?id=405340 --- Comment #4 from Mark Stanton --- Deleted and reconfigured? No, not at all. I've been running this setup has been running for 3 or 4 years now without any major change. Is the "set the template folder" option new? All my accounts have it set as "Local Folders". I certainly haven't set them to that. I don't remember being aware of this setting, but it's possible I've just forgotten. This *might* be the first time I've attempted to use a template. Thanks for the deletion info -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405340] Email template created in wrong place and not removable
https://bugs.kde.org/show_bug.cgi?id=405340 --- Comment #2 from Mark Stanton --- Fair point. I'd forgotten that it is configurable. Thank you. Setting it as I want does make it work the way I want. However, those messages/templates in the "Local folders" folder still can't be deleted or moved (whereas those in the templates folder [the place I picked] can be). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405340] New: Email template created in wrong place and not removable
https://bugs.kde.org/show_bug.cgi?id=405340 Bug ID: 405340 Summary: Email template created in wrong place and not removable Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Target Milestone: --- SUMMARY a) Templates are incorrectly created in the "Local Folders" folder rather than "Templates" b) Templates in this folder cannot be deleted/moved. This used to work in the expected way. STEPS TO REPRODUCE 1. Create an email 2. Save as template 3. OBSERVED RESULT Template created in "Local Folders" folder EXPECTED RESULT Template created in "templates" folder SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Version 5.10.2, or is that Kontact. -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 388478] Could not create key pair: No agent running
https://bugs.kde.org/show_bug.cgi?id=388478 Mark N Carpenter Jr changed: What|Removed |Added CC||mcarpen...@smtcorp.com --- Comment #5 from Mark N Carpenter Jr --- So I can verify this on a recent install where all of the self-checks return ok. Kleopatra fails with the same error if launched from a user's gui, but if launched from the terminal with sudo kleopatra indicates success, the certs do not show up for the user. -- You are receiving this mail because: 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
--- Comment #24 from Mark Gannon <m...@truenorth.nu> ---
Sorry. Its been a long time since I did any c++. I tried changing to:
+QScopedPointer f_list = m_mainWidget->allFeedsList();
+if (f_list.isNull()) {
+ return;
+}
+
And got the following error:
/var/tmp/portage/kde-apps/akregator-17.12.1/work/akregator-17.12.1/src/akregator_part.cpp:
In member function ‘void Akregator::Part::slotSaveFeedList()’:
/var/tmp/portage/kde-apps/akregator-17.12.1/work/akregator-17.12.1/src/akregator_part.cpp:529:65:
error: conversion from ‘QSharedPointer’ to non-scalar type
‘QScopedPointer’ requested
QScopedPointer f_list = m_mainWidget->allFeedsList();
~~^~
Perhaps I'm using it wrong?
--
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 #22 from Mark Gannon <m...@truenorth.nu> --- Created attachment 110511 --> https://bugs.kde.org/attachment.cgi?id=110511=edit Exit slotSaveFeedList() if feed is empty without writing anyfiles The last time slotSaveFeedList() was being called with an empty feed list. The attached patch checks to see if the feed is null, and if so, returns without writing any files. -- 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 #21 from Mark Gannon <m...@truenorth.nu> --- When I shutdown akregator (from gentoo's 17.12.1 package) I experience this problem and get the following output at the terminal: [1:1:0205/180714.662998:ERROR:broker_posix.cc(41)] Invalid node channel message [1:1:0205/180714.674483:ERROR:broker_posix.cc(41)] Invalid node channel message [1:1:0205/180714.686681:ERROR:broker_posix.cc(41)] Invalid node channel message [1:1:0205/180714.697479:ERROR:broker_posix.cc(41)] Invalid node channel message kf5.kxmlgui: 0x563be92f3b10 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1:1:0205/180714.727815:ERROR:broker_posix.cc(41)] Invalid node channel message [1:1:0205/180714.727927:ERROR:broker_posix.cc(41)] Invalid node channel message [1:1:0205/180714.728664:ERROR:broker_posix.cc(41)] Invalid node channel message [1:1:0205/180714.728952:ERROR:broker_posix.cc(41)] Invalid node channel message Perhaps its a different issue, but it does happen when I exit akregator (and when I start the feed has to be reimported). -- 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 Mark Gannon <m...@truenorth.nu> changed: What|Removed |Added CC||m...@truenorth.nu -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 385847] Kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=385847 Mark Stanton <m...@vowleyfarm.co.uk> changed: What|Removed |Added CC||m...@vowleyfarm.co.uk -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 385847] Kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=385847 --- Comment #1 from Mark Stanton <m...@vowleyfarm.co.uk> --- Created attachment 109983 --> https://bugs.kde.org/attachment.cgi?id=109983=edit New crash information added by DrKonqi kontact (5.7.0) using Qt 5.9.2 - What I was doing when the application crashed: Simply restarting - Unusual behavior I noticed: I'd closed contact because it was failing to show the contents of a message, but processor activity and memory usage hardly reduced at all. On restarting Kontact, the akonadiserver process is currently using 278Mb of memory with the associated mysql process using 160Mb of memory -- Backtrace (Reduced): #6 0x7ff831d3 in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::Callback const&, GURL*) () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f4445cfac61 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::Callback const&, GURL*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f4445e02697 in net::URLRequest::Start() () from /lib64/libQt5WebEngineCore.so.5 #9 0x7f44453231f0 in content::ResourceLoader::StartRequestInternal() () from /lib64/libQt5WebEngineCore.so.5 #10 0x7f44453232e8 in content::ResourceLoader::StartRequest() () from /lib64/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 --- Comment #16 from Mark Gannon <m...@truenorth.nu> --- Can you give a little more help on applying the patch on gentoo? I tried the patch (renamed as smtpsend.patch) in /etc/portage/patches/kde-apps/kmailtransport-17.12.0/ and /etc/portage/patches/kde-apps/kmail-17.12.0 and then ran ebuild prepare and it failed in both cases. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 Mark Gannon <m...@truenorth.nu> changed: What|Removed |Added CC||m...@truenorth.nu -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 384083] New: Kontact reports crash, but is in fact running
https://bugs.kde.org/show_bug.cgi?id=384083 Bug ID: 384083 Summary: Kontact reports crash, but is in fact running Product: kontact Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Target Milestone: --- Application: kontact (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.8-200.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: I was just starting up Kontact. I have four virtual desktops. I started Kontact while in one, then remembered it was not the one I wished it to be in so I switched to another for it to start there. I received the crash notification. I switched back to the first one to start another app then, while writing this report noticed that in fact Kontact was indeed open. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd5b44e1940 (LWP 20576))] Thread 26 (Thread 0x7fd58e7fc700 (LWP 26629)): #0 0x7fd5c34e4809 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd5c6ba0002 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7fd5c6b76a99 in base::PosixDynamicThreadPool::WaitForTask() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7fd5c6b76f85 in base::(anonymous namespace)::WorkerThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7fd5c6b6f9e2 in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7fd5c34de73a in start_thread () from /lib64/libpthread.so.0 #6 0x7fd5cccf6e0f in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7fd58effd700 (LWP 26622)): #0 0x7fd5bea88894 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7fd5bea42bc1 in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7fd5bea43104 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7fd5bea4327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7fd5cdaf16eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fd5cdaa268a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fd5cd8ff5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7fd5cd9039ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7fd5c34de73a in start_thread () from /lib64/libpthread.so.0 #9 0x7fd5cccf6e0f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7fd4b0a9e700 (LWP 20642)): #0 0x7fd5c34e4460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd5c6b71e79 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7fd5c6b725d7 in base::SequencedWorkerPool::Worker::Run() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7fd5c6b733d0 in base::SimpleThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7fd5c6b6f9e2 in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7fd5c34de73a in start_thread () from /lib64/libpthread.so.0 #6 0x7fd5cccf6e0f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7fd4b8db9700 (LWP 20610)): #0 0x7fd5bea4292c in g_main_context_query () from /lib64/libglib-2.0.so.0 #1 0x7fd5bea430d8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fd5bea4327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fd5cdaf16eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fd5cdaa268a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fd5cd8ff5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fd5cd9039ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fd5c34de73a in start_thread () from /lib64/libpthread.so.0 #8 0x7fd5cccf6e0f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7fd4b9dbb700 (LWP 20608)): #0 0x7fd5ccceaecd in poll () from /lib64/libc.so.6 #1 0x7fd5bea43166 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fd5bea4327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fd5cdaf16eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fd5cdaa268a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fd5cd8ff5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fd5cd9039ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fd5c34de73a in start_thread () from
[kontact] [Bug 382560] New: Kontact crashed during first time start up
https://bugs.kde.org/show_bug.cgi?id=382560 Bug ID: 382560 Summary: Kontact crashed during first time start up Product: kontact Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Target Milestone: --- Application: kontact (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.10-200.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Starting Kontact in the morning. The machine is on all the time, but I close down most apps overnight (since many KDE apps seems to experience memory bloat when left on for long periods). This morning I opened Kontact and it crashed before creating a (visible) window. Whilst it was opening I tried to show the autohiding menu bar. This lead to unusual behaviour. - Unusual behavior I noticed: After selecting Kontact to open I moved the mouse pointer down to the bottom of the screen to show the autohide menubar. It didn't fully show, only the top line of it being drawn before Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f848b8c8940 (LWP 17292))] Thread 31 (Thread 0x7f8382ed0700 (LWP 1673)): #0 0x7f849a8c4809 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f849df7f002 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f849df55a99 in base::PosixDynamicThreadPool::WaitForTask() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f849df55f85 in base::(anonymous namespace)::WorkerThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f849df4e9e2 in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f849a8be73a in start_thread () from /lib64/libpthread.so.0 #6 0x7f84a40d5e0f in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f8392675700 (LWP 1660)): #0 0x7f84a40c9ecd in poll () from /lib64/libc.so.6 #1 0x7f8495e23166 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f8495e2327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f84a4ed06eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f84a4e8168a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f84a4cde5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f84a4ce29ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f849a8be73a in start_thread () from /lib64/libpthread.so.0 #8 0x7f84a40d5e0f in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f832a177700 (LWP 23827)): #0 0x7ffc74ad5b12 in clock_gettime () #1 0x7f84a40e45a6 in clock_gettime () from /lib64/libc.so.6 #2 0x7f84a4d79b31 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7f84a4eced99 in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7f84a4ecf195 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7f84a4ed038c in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQt5Core.so.5 #6 0x7f84a4ed0455 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #7 0x7f8495e2269d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #8 0x7f8495e2308b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #9 0x7f8495e2327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #10 0x7f84a4ed06eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7f84a4e8168a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #12 0x7f84a4cde5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #13 0x7f84a4ce29ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #14 0x7f849a8be73a in start_thread () from /lib64/libpthread.so.0 #15 0x7f84a40d5e0f in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f832a978700 (LWP 23819)): #0 0x7ffc74ad5b12 in clock_gettime () #1 0x7f84a40e45a6 in clock_gettime () from /lib64/libc.so.6 #2 0x7f84a4d79b31 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7f84a4eced99 in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7f84a4ecf195 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7f84a4ed038c in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQt5Core.so.5 #6 0x7f84a4ed0455 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #7 0x7f8495e2269d in
[Akonadi] [Bug 309474] akonadictl fsck : item has no RID
https://bugs.kde.org/show_bug.cgi?id=309474 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #2 from Mark Fraser <mfraz74+...@gmail.com> --- Still happening in 2017. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 --- Comment #15 from Mark Fraser <mfraz74+...@gmail.com> --- I'm running Akregator 16.12.3 and this is still happening. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381194] KMail not detecting HTML mails
https://bugs.kde.org/show_bug.cgi?id=381194 --- Comment #2 from Mark Fraser <mfraz74+...@gmail.com> --- Even if I set the "message default format" to prefer HTML or set it in security settings, it will go back to displaying text or not displaying images when I go back to that folder later. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait" when loading a message with an attached .ics file
https://bugs.kde.org/show_bug.cgi?id=297930 --- Comment #35 from Mark Fraser <mfraz74+...@gmail.com> --- After upgrading from Kubuntu 16.10 to 17.04 I have experienced this constantly. I've even tried redoing local-mail. Seems to mainly happen when there are duplicates in that folder. Sometimes I can fix it by restarting the local mailbox. Using KMail 5.4.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait" when loading a message with an attached .ics file
https://bugs.kde.org/show_bug.cgi?id=297930 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381194] KMail not detecting HTML mails
https://bugs.kde.org/show_bug.cgi?id=381194 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #1 from Mark Fraser <mfraz74+...@gmail.com> --- Even though I have "Prefer HTML over raw text" selected, it still displays raw text the first time an email is displayed. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 381221] New: Akgregator crashes on launch
https://bugs.kde.org/show_bug.cgi?id=381221 Bug ID: 381221 Summary: Akgregator crashes on launch Product: akregator Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: magpie...@gmx.com Target Milestone: --- Application: akregator (5.5.2) (Compiled from sources) Qt Version: 5.9.0 Frameworks Version: 5.34.0 Operating System: Linux 4.9.26 x86_64 Distribution: "Linux From Scratch" -- Information about the crash: - What I was doing when the application crashed: Launching from command prompt. Same result each attempt. Kmail starts but won't connect to akonadi. 16.12.3 was stable. Exactly the same build method was used for 17.04.2. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #6 0x0110 in () #7 0x7fc4862d88f9 in QMetaObject::cast(QObject const*) const () at /opt/qt5/lib/libQt5Core.so.5 #8 0x7fc48b26cd4e in Akregator::FrameManager::saveProperties(KConfigGroup&) () at /opt/kf5/lib/libakregatorprivate.so.5 #9 0x7fc455fe8c8f in Akregator::MainWidget::saveProperties(KConfigGroup&) () at /opt/kf5/lib/plugins/akregatorpart.so #10 0x7fc455fe4ee0 in () at /opt/kf5/lib/plugins/akregatorpart.so #11 0x7fc455ffebbd in () at /opt/kf5/lib/plugins/akregatorpart.so #12 0x7fc4862fb5c1 in QObject::event(QEvent*) () at /opt/qt5/lib/libQt5Core.so.5 #13 0x7fc48701eaec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /opt/qt5/lib/libQt5Widgets.so.5 #14 0x7fc487025df1 in QApplication::notify(QObject*, QEvent*) () at /opt/qt5/lib/libQt5Widgets.so.5 #15 0x7fc4862cf758 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /opt/qt5/lib/libQt5Core.so.5 #16 0x7fc4862d20dd in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /opt/qt5/lib/libQt5Core.so.5 #17 0x7fc486321dc3 in () at /opt/qt5/lib/libQt5Core.so.5 #18 0x7fc47298afb7 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #19 0x7fc47298b1e8 in () at /usr/lib/libglib-2.0.so.0 #20 0x7fc47298b28c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #21 0x7fc4863221cf in QEventDispatcherGlib::processEvents(QFlags) () at /opt/qt5/lib/libQt5Core.so.5 #22 0x7fc4862cdefa in QEventLoop::exec(QFlags) () at /opt/qt5/lib/libQt5Core.so.5 #23 0x7fc4862d63c4 in QCoreApplication::exec() () at /opt/qt5/lib/libQt5Core.so.5 #24 0x00408c11 in () #25 0x7fc485443291 in __libc_start_main () at /lib/libc.so.6 #26 0x00408dca in _start () Possible duplicates by query: bug 381137. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379509] New: Message not found
https://bugs.kde.org/show_bug.cgi?id=379509 Bug ID: 379509 Summary: Message not found Product: kmail2 Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Target Milestone: --- I (very) frequently get "Message not found" responses. KMail fails to find a message, spends a couple of minutes trying and then gives a message in the bottom bar of the type "Failed to retrieve message from backend". I think I have an idea of the cause. Since I'm using KMail as the main message agent, I have many filters. Since I also have some messages with a completely empty body in the mailbox from which they're collected which then also appear in the folder a filter redirects them to, I suspect that both these faults are because the filtering process picks up the message before it has been completely received. No, no evidence. What would constitute useful evidence here? This error occurs several times a week for me so if there's information that would help just let me know. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 377871] New: "Filed to write data to stream"
https://bugs.kde.org/show_bug.cgi?id=377871 Bug ID: 377871 Summary: "Filed to write data to stream" Product: Akonadi Version: 5.4.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Target Milestone: --- Application: akonadiserver (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.32.0 Operating System: Linux 4.9.14-200.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Trying to access emails. Emails are arriving and showing up as duplicates, and messages are not being displayed (persistent "retrieving folder contents" messages that never resolve). I was trying to find one that would display. Although there are messages that will sometimes display properly, at times (like this) none will. - Custom settings of the application: This setup is a clean install using data that I have attempted to import from a previous F25 (produced by upgrading from F24, and earlier versions) installation. Whilst I have attempted to import mail, contact, and organizer data, none of it has appeared. I have just run fsck and vaccum with akonadictl, but these have made no difference to this situation. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1dfb7698c0 (LWP 13166))] Thread 51 (Thread 0x7f1d97fef700 (LWP 23044)): #0 0x7f1df9f5a01d in poll () from /lib64/libc.so.6 #1 0x7f1df4e63166 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f1df4e6327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1dfad606eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f1dfad1168a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x56022e6dd9d0 in Akonadi::Server::ItemRetriever::exec() () #6 0x56022e6a44a1 in Akonadi::Server::FetchHelper::fetchItems() () #7 0x56022e6a175b in Akonadi::Server::Fetch::parseStream() () #8 0x56022e590784 in Akonadi::Server::Connection::slotNewData() () #9 0x7f1dfad39a56 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f1dfad39721 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #11 0x7f1dfb8a91a5 in QAbstractSocketPrivate::emitReadyRead() () from /lib64/libQt5Network.so.5 #12 0x7f1dfb8a925c in QAbstractSocketPrivate::canReadNotification() () from /lib64/libQt5Network.so.5 #13 0x7f1dfb8b4091 in QReadNotifier::event(QEvent*) () from /lib64/libQt5Network.so.5 #14 0x7f1dfad125ea in doNotify(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f1dfad126fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f1dfad60fff in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #17 0x7f1df4e62e52 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f1df4e631d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #19 0x7f1df4e6327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f1dfad606cf in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7f1dfad1168a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7f1dfab6e5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #23 0x7f1dfab729ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #24 0x7f1df87986ca in start_thread () from /lib64/libpthread.so.0 #25 0x7f1df9f65f7f in clone () from /lib64/libc.so.6 Thread 50 (Thread 0x7f1d9effd700 (LWP 23043)): #0 0x7f1df4e62bd6 in g_main_context_check () from /lib64/libglib-2.0.so.0 #1 0x7f1df4e63104 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f1df4e6327c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f1dfad606eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f1dfad1168a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f1dfab6e5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f1dfab729ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f1df87986ca in start_thread () from /lib64/libpthread.so.0 #8 0x7f1df9f65f7f in clone () from /lib64/libc.so.6 Thread 49 (Thread 0x7f1d95feb700 (LWP 16898)): #0 0x7f1df4ea8894 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f1df4e6311a in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f1df4e6327c in
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #12 from Mark Fraser <mfraz74+...@gmail.com> --- Yes, I am still seeing this bug with Kontact 5.2.3 in Kubuntu 16.04. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 Mark <mw471...@gmail.com> changed: What|Removed |Added CC||mw471...@gmail.com --- Comment #5 from Mark <mw471...@gmail.com> --- I too would like to see this addressed. I appreciate all the hard work that has gone into KMail over the years, but it seems in this respect it's been superannuated somewhat by trends in desktop themes. Running a dark theme makes ~80% of the HTML emails I receive unreadable in KMail, which is a shame as I otherwise love it and Kontact alike. In it's simplest form, it could be a checkbox called "Force white background and black text for HTML email." -- You are receiving this mail because: You are the assignee for the bug.
[kholidays] [Bug 365241] The information on Japanese holidays is outdated
https://bugs.kde.org/show_bug.cgi?id=365241 Mark Fairbairn <farcu...@gmail.com> changed: What|Removed |Added CC||farcu...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367874] kMail crashes upon Thunderbird-generated invitation confirmations
https://bugs.kde.org/show_bug.cgi?id=367874 --- Comment #5 from Mark Petersen <petersen...@gmail.com> --- Created attachment 101085 --> https://bugs.kde.org/attachment.cgi?id=101085=edit email with outlook invitation -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367874] kMail crashes upon Thunderbird-generated invitation confirmations
https://bugs.kde.org/show_bug.cgi?id=367874 Mark Petersen <petersen...@gmail.com> changed: What|Removed |Added CC||petersen...@gmail.com --- Comment #4 from Mark Petersen <petersen...@gmail.com> --- Outlook invitations crash kmail/kontact as soon as the offending email is clicked on. openSuse Tumbleweed kmail5 16.08.0-1.2 I've added a sanitized email that triggers the crash. Mark -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368371] kontact crashes reliably upon browsing through unread emails
https://bugs.kde.org/show_bug.cgi?id=368371 Mark Draheim <rickscafe.casabla...@gmx.net> changed: What|Removed |Added CC||rickscafe.casabla...@gmx.ne ||t --- Comment #3 from Mark Draheim <rickscafe.casabla...@gmx.net> --- https://bugreports.qt.io/browse/QTBUG-41242 https://bugs.freedesktop.org/show_bug.cgi?id=91632 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368515] Kmail crashing some time after start
https://bugs.kde.org/show_bug.cgi?id=368515 Mark Draheim <rickscafe.casabla...@gmx.net> changed: What|Removed |Added CC||rickscafe.casabla...@gmx.ne ||t --- Comment #1 from Mark Draheim <rickscafe.casabla...@gmx.net> --- probably dup of #368371 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363400] New: Akonadi elements stop working with only slightly low memory
https://bugs.kde.org/show_bug.cgi?id=363400 Bug ID: 363400 Summary: Akonadi elements stop working with only slightly low memory Product: kmail2 Version: 4.14.10 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Message and folder operations gradually stop working. Message filtering stops with "only" 2.1Gb of memory (according to KDE System Monitor) available (out of a total of 5.8Gb). There is over 5Gb of swap available, but this seems to have no effect. With approx 1Gb of RAM available, messages no longer register as "read" when they have been read. At about the same level, sent messages are no longer put in the folders selected for them but only show in the outbox. While I appreciate low memory may cause lost of functionality, I struggle to think of these levels of available RAM as "small". Reproducible: Always Steps to Reproduce: 1. Use up lots of memory. NetBeans and Chrome loaded seems to do it. 2. Simply watch filtering stop working. 3. Actual Results: Messages remain in the mailboxes they arrive in. Using the "Apply all filters on folder" item from the Folders menu makes no difference. Expected Results: Messages should be transferred to the folders selected for them in the filters created. They should work as they do with lower levels of memory in use. -- 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 363396] New: KOrganizer (via KDEPIM) crashes on close after pasting events
https://bugs.kde.org/show_bug.cgi?id=363396 Bug ID: 363396 Summary: KOrganizer (via KDEPIM) crashes on close after pasting events Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Application: kontact (4.14.10) KDE Platform Version: 4.14.17 Qt Version: 4.8.7 Operating System: Linux 4.4.9-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: Having an oddly recurring event I decided to copy the original and paste subsequent instances of it. Firstly, on pasting the subsequent event does not show up on the date pasted to. Having tried this before and found that the subsequent event has been created but simply hasn't been shown, I decided to close and reopen KDEPIM. With either a single or multiple pastes, KDEPIM crashes on close. I have done this two or three times with a crash every time. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fdf7a7e6900 (LWP 1091))] Thread 3 (Thread 0x7fdf2f6b8700 (LWP 1092)): #0 0x003e70a0c540 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x003b7858af61 in JSC::BlockAllocator::blockFreeingThreadMain() () at /lib64/libQtWebKit.so.4 #2 0x003b788896d6 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQtWebKit.so.4 #3 0x003e70a07555 in start_thread (arg=0x7fdf2f6b8700) at pthread_create.c:333 #4 0x003e6ff02ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fdf25a2a700 (LWP 1096)): #0 0x7ffe25be6c8f in clock_gettime () #1 0x003e6ff10fcd in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fdf25a29a90) at ../sysdeps/unix/clock_gettime.c:115 #2 0x00316e2e6c35 in qt_gettime() (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127 #3 0x00316e2e6c35 in qt_gettime() () at tools/qelapsedtimer_unix.cpp:144 #4 0x00316e3cc939 in QTimerInfoList::updateCurrentTime() (this=this@entry=0x7fdf200030e0) at kernel/qeventdispatcher_unix.cpp:354 #5 0x00316e3cb766 in timerSourceCheckHelper(GTimerSource*) (src=0x7fdf20003080) at kernel/qeventdispatcher_glib.cpp:157 #6 0x003e71649801 in g_main_context_check () at /lib64/libglib-2.0.so.0 #7 0x003e71649d60 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #8 0x003e71649ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x00316e3cbe7e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fdf28e0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #10 0x00316e39a131 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7fdf25a29cd0, flags=...) at kernel/qeventloop.cpp:149 #11 0x00316e39a4a5 in QEventLoop::exec(QFlags) (this=this@entry=0x7fdf25a29cd0, flags=...) at kernel/qeventloop.cpp:204 #12 0x00316e289a99 in QThread::exec() (this=) at thread/qthread.cpp:538 #13 0x00316e28c38c in QThreadPrivate::start(void*) (arg=0x15e3da0) at thread/qthread_unix.cpp:352 #14 0x003e70a07555 in start_thread (arg=0x7fdf25a2a700) at pthread_create.c:333 #15 0x003e6ff02ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fdf7a7e6900 (LWP 1091)): [KCrash Handler] #6 0x0030e4ddbb00 in QAbstractSlider::maximum() const (this=0x0) at widgets/qabstractslider.cpp:366 #7 0x003448023764 in KViewStateSaver::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (this=0x1729690) at ../../kdeui/itemviews/kviewstatesaver.cpp:67 #8 0x003448023764 in KViewStateSaver::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _id=, _a=, _c=) at ./kviewstatesaver.moc:52 #9 0x00316e3b57f1 in QObject::event(QEvent*) (this=0xb006380, e=) at kernel/qobject.cpp:1222 #10 0x0030e4a0293c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x1032c00, receiver=receiver@entry=0xb006380, e=e@entry=0x1b787e0) at kernel/qapplication.cpp:4565 #11 0x0030e4a09796 in QApplication::notify(QObject*, QEvent*) (this=this@entry=0x7ffe25bbef80, receiver=receiver@entry=0xb006380, e=e@entry=0x1b787e0) at kernel/qapplication.cpp:4351 #12 0x00344805559a in KApplication::notify(QObject*, QEvent*) (this=0x7ffe25bbef80, receiver=0xb006380, event=0x1b787e0) at ../../kdeui/kernel/kapplication.cpp:311 #13 0x00316e39b8bd in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffe25bbef80, receiver=receiver@entry=0xb006380, event=event@entry=0x1b787e0) at kernel/qcoreapplication.cpp:955 #14
[kmail2] [Bug 361639] New: Kmail Crashes when double clicking on message in the message list
https://bugs.kde.org/show_bug.cgi?id=361639 Bug ID: 361639 Summary: Kmail Crashes when double clicking on message in the message list Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@truenorth.nu Application: kmail (5.1.90 rc) (Compiled from sources) Qt Version: 5.5.1 Frameworks Version: 5.21.0 Operating System: Linux 4.3.3-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: Open kmail. Double click on a message in the message list to open it as its own window. Kmail crashes and this dialog appears The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f34ea0bb7c0 (LWP 6894))] Thread 21 (Thread 0x7f34cc406700 (LWP 6895)): #0 0x7f34e78ecc8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f34dbc77b12 in poll (__timeout=-1, __nfds=1, __fds=0x7f34cc405d00) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0xf1aea0, cond=cond@entry=0xf1aee0, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x7f34dbc798f7 in xcb_wait_for_event (c=0xf1aea0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693 #4 0x7f34ce76dce9 in QXcbEventReader::run (this=0xf25850) at qxcbconnection.cpp:1229 #5 0x7f34e81eb632 in QThreadPrivate::start (arg=0xf25850) at thread/qthread_unix.cpp:331 #6 0x7f34de6475c6 in start_thread (arg=0x7f34cc406700) at pthread_create.c:334 #7 0x7f34e78f60cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 20 (Thread 0x7f34ca30d700 (LWP 6896)): #0 0x7f34e78ecc8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f34dcaedf1c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f34bc003070, timeout=, context=0x7f34bc000990) at /var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f34bc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3835 #3 0x7f34dcaee04c in g_main_context_iteration (context=0x7f34bc000990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3901 #4 0x7f34e83e226b in QEventDispatcherGlib::processEvents (this=0x7f34bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f34e8392e0a in QEventLoop::exec (this=this@entry=0x7f34ca30ce00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f34e81e6e96 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f34e81eb632 in QThreadPrivate::start (arg=0xff8b30) at thread/qthread_unix.cpp:331 #8 0x7f34de6475c6 in start_thread (arg=0x7f34ca30d700) at pthread_create.c:334 #9 0x7f34e78f60cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7f34c9b0c700 (LWP 6897)): #0 0x7f34e78ecc8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f34dcaedf1c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f34c0002e20, timeout=, context=0x7f34c990) at /var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f34c990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3835 #3 0x7f34dcaee04c in g_main_context_iteration (context=0x7f34c990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:3901 #4 0x7f34e83e226b in QEventDispatcherGlib::processEvents (this=0x7f34c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f34e8392e0a in QEventLoop::exec (this=this@entry=0x7f34c9b0be00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f34e81e6e96 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f34e81eb632 in QThreadPrivate::start (arg=0x106d390) at thread/qthread_unix.cpp:331 #8 0x7f34de6475c6 in start_thread (arg=0x7f34c9b0c700) at pthread_create.c:334 #9 0x7f34e78f60cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f34c930b700 (LWP 6898)): #0 g_source_iter_next (iter=iter@entry=0x7f34c930ac30, source=source@entry=0x7f34c930ac28) at /var/tmp/portage/dev-libs/glib-2.48.0/work/glib-2.48.0/glib/gmain.c:933 #1 0x7f34dcaed42b in g_main_context_prepare (context=context@entry=0x7f34b4000990,
[Akonadi] [Bug 353414] crash of imap component
https://bugs.kde.org/show_bug.cgi?id=353414 --- Comment #1 from Mark Stanton <m...@vowleyfarm.co.uk> --- Created attachment 96993 --> https://bugs.kde.org/attachment.cgi?id=96993=edit New crash information added by DrKonqi akonadi_imap_resource (4.14) on KDE Platform 4.14.14 using Qt 4.8.6 - What I was doing when the application crashed: Nothing. The GMail IMap thing just crashes in the background, quite frequently. More frequently, it seems to me, than it's synchronising frequency -- Backtrace (Reduced): #6 0x003378a5406d in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () at /lib64/libkimap.so.4 #7 0x003378a4327e in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () at /lib64/libkimap.so.4 #8 0x0037015a3e61 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4 #9 0x003b1a9c43ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #10 0x003b1a9cb206 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 353414] crash of imap component
https://bugs.kde.org/show_bug.cgi?id=353414 Mark Stanton <m...@vowleyfarm.co.uk> changed: What|Removed |Added CC||m...@vowleyfarm.co.uk -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 356903] New: akonadi notes agent use 800Mb of RAM all the time
https://bugs.kde.org/show_bug.cgi?id=356903 Bug ID: 356903 Summary: akonadi notes agent use 800Mb of RAM all the time Product: Akonadi Version: 4.13 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk I use Kontact (4.14.10 under Plasma5, Fedora22), and the akonadi_notes_agent always occupies around about this much memory. I have very few notes, but it seems ALL my email is also listed in a notebook. I don't want this, I'm not aware of having set it up like this, I don't seem to be able to stop it. If I select "Notes" in Kontact then its RAM usage goes up around 1.25Gb and 50% cpu usage. I haven't been able to find a solution either from the help or the IRC channel(s). Reproducible: Always Steps to Reproduce: 1. Turn on computer 2. 3. -- 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 356508] New: Kontact crashes when requesting close
https://bugs.kde.org/show_bug.cgi?id=356508 Bug ID: 356508 Summary: Kontact crashes when requesting close Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Application: kontact (4.14.10) KDE Platform Version: 4.14.14 Qt Version: 4.8.6 Operating System: Linux 4.2.6-201.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: - What I was doing when the application crashed: Closing Kontact (using close icon at top right of window) because it seemed to have gone out of control. It was using around 50% cpu most of the time without any visible cause. - Unusual behavior I noticed: A very (very) large number of emails appear as "popup notes" in the "overview" section of Kontact, although they don't appear in the popup notes section. I was looking for a way to remove them, until Kontact seemed to go wild. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8ffd78e900 (LWP 3127))] Thread 3 (Thread 0x7f8fb2be9700 (LWP 3148)): #0 0x003aad60c540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x003b7858af61 in JSC::BlockAllocator::blockFreeingThreadMain() () at /lib64/libQtWebKit.so.4 #2 0x003b788896d6 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQtWebKit.so.4 #3 0x003aad607555 in start_thread () at /lib64/libpthread.so.0 #4 0x003aacb02b9d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f8fa826b700 (LWP 3259)): #0 0x003aacaf72fd in poll () at /lib64/libc.so.6 #1 0x003aae249dbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x003aae249ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x003ab77ba4ee in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #4 0x003ab7788791 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #5 0x003ab7788b05 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #6 0x003ab7678289 in QThread::exec() () at /lib64/libQtCore.so.4 #7 0x003ab767aaac in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #8 0x003aad607555 in start_thread () at /lib64/libpthread.so.0 #9 0x003aacb02b9d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f8ffd78e900 (LWP 3127)): [KCrash Handler] #6 0x0032bdd9b0d0 in QAbstractSlider::maximum() const () at /lib64/libQtGui.so.4 #7 0x003970e23714 in KViewStateSaver::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.25] () at /lib64/libkdeui.so.5 #8 0x003ab77a3e61 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4 #9 0x0032bd9c43ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #10 0x0032bd9cb206 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #11 0x003970e5554a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #12 0x003ab7789f1d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #13 0x003ab778d536 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQtCore.so.4 #14 0x003ab77ba35e in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtCore.so.4 #15 0x003aae249a8a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #16 0x003aae249e20 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #17 0x003aae249ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #18 0x003ab77ba4ce in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #19 0x0032bda6a626 in QGuiEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtGui.so.4 #20 0x003ab7788791 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #21 0x003ab7788b05 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #22 0x003ab778e6a9 in QCoreApplication::exec() () at /lib64/libQtCore.so.4 #23 0x00403787 in main () Possible duplicates by query: bug 355848, bug 353380. Reported using DrKonqi -- 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 308968] certificate is not remembered
https://bugs.kde.org/show_bug.cgi?id=308968 --- Comment #10 from Mark Stanton <m...@vowleyfarm.co.uk> --- I should add that this happens every time KMail checks mail, not just once a session. -- 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 308968] certificate is not remembered
https://bugs.kde.org/show_bug.cgi?id=308968 Mark Stanton <m...@vowleyfarm.co.uk> changed: What|Removed |Added CC||m...@vowleyfarm.co.uk --- Comment #9 from Mark Stanton <m...@vowleyfarm.co.uk> --- This is the case here under Arch Linux with certificates that do not match the domain but I have certified as acceptable. This is with version 5.0.3. My KMail version 4. 4.14.10 does not show this when connecting to the same services -- 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 352036] Regression: kMail 5.0.0 cannot open links contained in mails
https://bugs.kde.org/show_bug.cgi?id=352036 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #13 from Mark Fraser <mfraz74+...@gmail.com> --- It isn't just restricted to KMail here. If I try to open a URL in Konsole, KRun(0x2923390) ERROR (stat): 111 "The file or folder http://dl.google.com/ does not exist." -- 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 353824] New: Kontact window continues grey after closing modal dialogue
https://bugs.kde.org/show_bug.cgi?id=353824 Bug ID: 353824 Summary: Kontact window continues grey after closing modal dialogue Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@vowleyfarm.co.uk Version 4.14.9 On opening the "configure Kontact" dialogue the rest of the app is greyed out behind it, which is fine, it's a modal dialogue. However, on closing the dialogue the app is *still* greyed out. It functions as usual but all grey. Opening another dialogue, like a bug reporting tool, clears the problem. Reproducible: Always Steps to Reproduce: 1. I opened the "configure KMail" window (to set up accounts). 2. Created a new account, but cancelled rather than saving 3. Close configure dialogue Actual Results: The app window remains very grey. It functions correctly. Switching between various "sub-apps" (contact, mail, calendar) doesn't clear the problem. Expected Results: The main window should be restored to normal contrast. -- 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 340046] after long inactivity (sleep) mailfilter agent remains at 0% indefinitely (and kmail at "Retrieving folder contents")
https://bugs.kde.org/show_bug.cgi?id=340046 Mark Fraser <mfraz74+...@gmail.com> changed: What|Removed |Added CC||mfraz74+...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 344372] moving/ copying messages from viewer
https://bugs.kde.org/show_bug.cgi?id=344372 --- Comment #9 from mark nuras...@gmail.com --- Yes, I understand that. I was suggesting to change it. What ideally would be useful is to have a workflow with similar to the behaviour in the message list. As: 1. Open a message 2. Press the shortcut for moving (m) or copying (c) message 3. A folder list open (which is searchable) ; same as in message list behaviour (perhaps reusable as code) 4. Press return at the selected target folder 5. Message is moved there The current behaviour is too complex for a often used task, IMHO. -- 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 344372] moving/ copying messages from viewer
https://bugs.kde.org/show_bug.cgi?id=344372 --- Comment #5 from mark nuras...@gmail.com --- (In reply to Laurent Montel from comment #3) Assign a shortcut is not possible because it's a menu = you can't assign a shortcut to top level ok menu :) Move I will look at how to put it. mm, it is possible to use r/f for reply/forward for example. Perhaps, with the above restriction, a sub-menu ..to folder would be a solution (similar to the location of the reply/ forward commands in their respective top level menus). Then, this would be similar to invoking copy/move from the message list. Not sure how much of a change that would be but it certainly would go some way to usability; for keyboard-centric users, opening a message and then decide where they like to move/ copy it to quickly. -- 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 344372] moving/ copying messages from viewer
https://bugs.kde.org/show_bug.cgi?id=344372 --- Comment #7 from mark nuras...@gmail.com --- (In reply to Laurent Montel from comment #6) forward/reply is an uniq action not a menu. list of folder is dynamic = create a shortcut against it it's not easy. I am confused. The reply/ forward is in the same action menu (right-click with mouse inside the message) as is the copy item to... What I imagine if I press the bespoke shortcut for moving/ copying message to folder.., is to get the same (search-able) folder list I would get if I press it on a message in the message list. -- 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 344372] moving/ copying messages from viewer
https://bugs.kde.org/show_bug.cgi?id=344372 --- Comment #14 from mark nuras...@gmail.com --- I still feel we are not on the same page. But perhaps, I do it wrong trying to understand your way. Please watch attached video from the action when done from the message list. Similar, I imagine, from the message viewer. No mouse clicks involved. With the method, you suggested, I need to navigate through the menus after activating window action menu (also video attached). -- 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 344372] moving/ copying messages from viewer
https://bugs.kde.org/show_bug.cgi?id=344372 --- Comment #2 from mark nuras...@gmail.com --- (In reply to Laurent Montel from comment #1) We are a copy item to... (ok I need to fix name) it allows to copy message Ahh, I just found it in the context menu. The addition of move.. would be nice, more useful to me, and a possibility to assign a shortcut to either. -- 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 344372] New: moving/ copying messages from viewer
https://bugs.kde.org/show_bug.cgi?id=344372 Bug ID: 344372 Summary: moving/ copying messages from viewer Product: kmail2 Version: 4.14.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: nuras...@gmail.com If a mail is viewed, it should be possible to move or copy this message to a folder the same way as it is possible from the message list. Reason being, that if a mail is searched via krunner, it will display in the viewer but one has no indication where this message was found and one might want to move it to a certain mail folder. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323455] Filter account is missing after KMail startup
https://bugs.kde.org/show_bug.cgi?id=323455 Mark Fraser mfraz74+...@gmail.com changed: What|Removed |Added CC||mfraz74+...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 323455] Filter account is missing after KMail startup
https://bugs.kde.org/show_bug.cgi?id=323455 --- Comment #12 from Mark Fraser mfraz74+...@gmail.com --- Running Kubuntu 14.10 and I'm still seeing this bug on both dual core and quad core computers. Didn't realise until this morning that when you dismiss the dialogue box that appears - and has no options other than ok and cancel - that filter is deleted. -- 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
[akregator] [Bug 338309] Akregator 4.14 RC crashes when closing
https://bugs.kde.org/show_bug.cgi?id=338309 Mark Christie baskitca...@gmail.com changed: What|Removed |Added CC||baskitca...@gmail.com --- Comment #1 from Mark Christie baskitca...@gmail.com --- Comment on attachment 88270 -- https://bugs.kde.org/attachment.cgi?id=88270 akregatorkcrash I get the same on Opensuse 13.1 however if I disable the systray icon everything is ok and the program shuts down gracefully. Can anyone else confirm please? Backtrace: Application: akregator (4.14) KDE Platform Version: 4.14.0 Qt Version: 4.8.5 Operating System: Linux 3.11.10-21-desktop x86_64 Distribution: openSUSE 13.1 (Bottle) (x86_64) -- Information about the crash: - What I was doing when the application crashed: Akregator segfaults ever time it is closed while it is showing the notification icon in the systray The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f44bacef880 (LWP 4233))] Thread 2 (Thread 0x7f4497b23700 (LWP 4235)): #0 0x7f44b7848b3d in poll () from /lib64/libc.so.6 #1 0x7f44b1c1b604 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f44b1c1b70c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f44b9125d76 in QEventDispatcherGlib::processEvents (this=0x7f4498c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x7f44b90f7d0f in QEventLoop::processEvents (this=this@entry=0x7f4497b22d20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f44b90f8005 in QEventLoop::exec (this=this@entry=0x7f4497b22d20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f44b8ff6fef in QThread::exec (this=this@entry=0x1781740) at thread/qthread.cpp:536 #7 0x7f44b90d9513 in QInotifyFileSystemWatcherEngine::run (this=0x1781740) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x7f44b8ff968f in QThreadPrivate::start (arg=0x1781740) at thread/qthread_unix.cpp:338 #9 0x7f44b2a2d0db in start_thread () from /lib64/libpthread.so.0 #10 0x7f44b785190d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f44bacef880 (LWP 4233)): [KCrash Handler] #5 deref (this=0x720077003a003a) at ../../src/corelib/arch/qatomic_x86_64.h:133 #6 QString::operator= (this=this@entry=0x16cd860, other=...) at tools/qstring.cpp:1411 #7 0x7f44ba1d286b in Akregator::Frame::slotSetStatusText (this=0x16cd820, s=...) at /usr/src/debug/kdepim-4.14.0/akregator/src/frame.cpp:65 #8 0x7f44a148a105 in Akregator::MainWidget::slotFetchingStopped (this=0x16ec7a0) at /usr/src/debug/kdepim-4.14.0/akregator/src/mainwidget.cpp:810 #9 0x7f44b910cd68 in QMetaObject::activate (sender=sender@entry=0x16a1140, m=m@entry=0x7f44ba3f47c0 Akregator::FetchQueue::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3556 #10 0x7f44ba1db783 in Akregator::FetchQueue::signalStopped (this=this@entry=0x16a1140) at /usr/src/debug/kdepim-4.14.0/build/akregator/src/moc_fetchqueue.cpp:126 #11 0x7f44ba1d2459 in Akregator::FetchQueue::slotAbort (this=this@entry=0x16a1140) at /usr/src/debug/kdepim-4.14.0/akregator/src/fetchqueue.cpp:68 #12 0x7f44ba1d24ca in Akregator::FetchQueue::~FetchQueue (this=0x16a1140, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.14.0/akregator/src/fetchqueue.cpp:50 #13 0x7f44ba1d2539 in Akregator::FetchQueue::~FetchQueue (this=0x16a1140, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.14.0/akregator/src/fetchqueue.cpp:53 #14 0x7f44ba1d1519 in Akregator::Kernel::~Kernel (this=0x7f44ba3f5c58 Akregator::Kernel::self()::self, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.14.0/akregator/src/kernel.cpp:66 #15 0x7f44b77a23d9 in __run_exit_handlers () from /lib64/libc.so.6 #16 0x7f44b77a2425 in exit () from /lib64/libc.so.6 #17 0x7f44b778bbec in __libc_start_main () from /lib64/libc.so.6 #18 0x0040872d in _start () at ../sysdeps/x86_64/start.S:122 -- 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
[knotes] [Bug 333640] Knotes version 4.13 don't inherit previous notes
https://bugs.kde.org/show_bug.cgi?id=333640 --- Comment #19 from Mark Fraser mfraz74+...@gmail.com --- In Preferences KNotes, you have to make sure that Notes is ticked under Collections. -- 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
[knotes] [Bug 333640] Knotes version 4.13 don't inherit previous notes
https://bugs.kde.org/show_bug.cgi?id=333640 Mark Fraser mfraz74+...@gmail.com changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #18 from Mark Fraser mfraz74+...@gmail.com --- Mine wouldn't migrate property either and every time Korganiser was launched, the KNotes migration window appeared. Think I solved it by changing the sources in KNotes, but will have to check when I get home. -- 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 331867] mysql: column 'name' can not be null when migrating PartTable
https://bugs.kde.org/show_bug.cgi?id=331867 Mark Anderson ourm...@gmail.com changed: What|Removed |Added CC||ourm...@gmail.com --- Comment #20 from Mark Anderson ourm...@gmail.com --- Ivan @ Comment 16 Thanks again for the walk-through. This one was a real pain for me. Mark -- 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 333534] New: Creating aknotes plasmoid crashes kontact
https://bugs.kde.org/show_bug.cgi?id=333534 Bug ID: 333534 Summary: Creating aknotes plasmoid crashes kontact Classification: Unclassified Product: kontact Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mark...@gmail.com Application: kontact (4.13) KDE Platform Version: 4.13.0 Qt Version: 4.8.5 Operating System: Linux 3.14.1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I've tried to reproduce this with others, but i seemingly am the only one who can make it crash. What i did is this: - Create two aknotes plasmoids - fill in one, leave the other as is. Don't change anything The notes work just fine, but when i start Kontact i get the crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /usr/lib/libthread_db.so.1. To enable execution of this file add add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.19-gdb.py line to your configuration file /home/mark/.gdbinit. To completely disable this security protection add set auto-load safe-path / line to your configuration file /home/mark/.gdbinit. For more information about this security protection see the Auto-loading safe path section in the GDB manual. E.g., run from the shell: info (gdb)Auto-loading safe path [Current thread is 1 (Thread 0x7fea121d3800 (LWP 2431))] Thread 4 (Thread 0x7fe9f2e4d700 (LWP 2432)): #0 0x7fea097b804f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fea0cf9094d in ?? () from /usr/lib/libQtWebKit.so.4 #2 0x7fea0cf90989 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0x7fea097b40a2 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fea0f76bd1d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe9f264c700 (LWP 2433)): #0 0x7fea097b804f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fea0ccd244d in ?? () from /usr/lib/libQtWebKit.so.4 #2 0x7fea0cfc00e6 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0x7fea097b40a2 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fea0f76bd1d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe99ed04700 (LWP 2439)): #0 0x7fea097b7500 in __pthread_mutex_unlock_usercnt () from /usr/lib/libpthread.so.0 #1 0x7fea0922d751 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #2 0x7fea091eb498 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #3 0x7fea091ebc83 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fea091ebe6c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fea0fed96a6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #6 0x7fea0feab6cf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #7 0x7fea0feab9c5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #8 0x7fea0fdaa4df in QThread::exec() () from /usr/lib/libQtCore.so.4 #9 0x7fea0fdacb7f in ?? () from /usr/lib/libQtCore.so.4 #10 0x7fea097b40a2 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fea0f76bd1d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fea121d3800 (LWP 2431)): [KCrash Handler] #5 0x7fe9ab152d03 in KNotesSummaryWidget::createNote (this=this@entry=0x1507b50, item=..., counter=3) at /home/mark/kdepim/src/kdepim-4.13.0/kontact/plugins/knotes/summarywidget.cpp:183 #6 0x7fe9ab153729 in KNotesSummaryWidget::displayNotes (this=this@entry=0x1507b50, parent=..., counter=@0x7fff5b5a9adc: 3) at /home/mark/kdepim/src/kdepim-4.13.0/kontact/plugins/knotes/summarywidget.cpp:147 #7 0x7fe9ab15373d in KNotesSummaryWidget::displayNotes (this=this@entry=0x1507b50, parent=..., counter=@0x7fff5b5a9adc: 3) at /home/mark/kdepim/src/kdepim-4.13.0/kontact/plugins/knotes/summarywidget.cpp:150 #8 0x7fe9ab153a9b in KNotesSummaryWidget::updateFolderList (this=0x1507b50) at /home/mark/kdepim/src/kdepim-4.13.0/kontact/plugins/knotes/summarywidget.cpp:121 #9 0x7fea0fec06ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #10 0x7fea0ff0a474 in QAbstractItemModel::rowsInserted(QModelIndex const, int, int) () from /usr/lib/libQtCore.so.4 #11 0x7fea0fea511e in QAbstractItemModel::endInsertRows() () from /usr/lib/libQtCore.so.4 #12 0x7fea0e726335 in ?? () from /usr/lib/libakonadi-kde.so.4 #13 0x7fea0e72687a in ?? () from /usr/lib/libakonadi-kde.so.4 #14 0x7fea0fec06ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #15 0x7fea0e749a12
[kdepimlibs] [Bug 333302] Dutch holiday list outdated
https://bugs.kde.org/show_bug.cgi?id=02 Mark mark...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||mark...@gmail.com Assignee|jl...@kde.org |mark...@gmail.com Ever confirmed|0 |1 --- Comment #2 from Mark mark...@gmail.com --- I'm taking this one since i live in the netherlands. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 332673] New: Notes don't appear in summary view unless I go into Pop-up notes
https://bugs.kde.org/show_bug.cgi?id=332673 Bug ID: 332673 Summary: Notes don't appear in summary view unless I go into Pop-up notes Classification: Unclassified Product: kontact Version: 4.13 pre Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary Assignee: kdepim-bugs@kde.org Reporter: mfraz74+...@gmail.com If I start Kontact in summary view, there are no notes showing. If I go into the pop-up notes plug-in and then go back to the summary view, the notes are now visible. Reproducible: Always Steps to Reproduce: 1. Open Kontact in summary view 2. See that no notes are visible 3. Go into popup notes and then back to summary view 4. See that the notes are now there -- 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 330420] kontact, 2 events but 0 event displayed in the list
https://bugs.kde.org/show_bug.cgi?id=330420 Mark Shelby mshel...@gmail.com changed: What|Removed |Added CC||mshel...@gmail.com --- Comment #3 from Mark Shelby mshel...@gmail.com --- Same problem here. Chakra-Linux system. Latest kde upgrades 4.12.2-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
[Akonadi] [Bug 326480] Akonadi fails to start with nvidia binary drivers installed
https://bugs.kde.org/show_bug.cgi?id=326480 Mark Fraser mfraz74+...@gmail.com changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #77 from Mark Fraser mfraz74+...@gmail.com --- Kubuntu 13.10 with KDE 4.12, just added the xorg-edgers PPA and updated to 331.38 and Akonadi is still not starting. -- 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 326480] Akonadi fails to start with nvidia binary drivers installed
https://bugs.kde.org/show_bug.cgi?id=326480 --- Comment #79 from Mark Fraser mfraz74+...@gmail.com --- Kubuntu 13.10 with KDE 4.12, just added the xorg-edgers PPA and updated to 331.38 and Akonadi is still not starting. -- 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 124216] Kmail runs out of memory when importing large Outlook Express mailboxes
https://bugs.kde.org/show_bug.cgi?id=124216 --- Comment #13 from Mark Wagner carni...@gmail.com --- Appears to be fixed. I just successfully imported a large (22,000 message) mailbox with no appreciable change in memory usage by either Kmail or KmailCVT. -- 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 329289] New: Adding Google Contacts crashes
https://bugs.kde.org/show_bug.cgi?id=329289 Bug ID: 329289 Summary: Adding Google Contacts crashes Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Google Resource Assignee: dvra...@redhat.com Reporter: mhow...@gmail.com CC: kdepim-bugs@kde.org Application: akonadi_googlecontacts_resource (4.11) KDE Platform Version: 4.11.3 Qt Version: 4.8.4 Operating System: Linux 3.11.0-14-generic x86_64 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: I was adding Google contacts, and Google attemped to access wallet, then crashed. The crash can be reproduced every time. -- Backtrace: Application: Google Contacts (not configured) of type Google Contacts (akonadi_googlecontacts_resource), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f84c82217c0 (LWP 14963))] Thread 6 (Thread 0x7f84af0ce700 (LWP 14964)): #0 0x7f84c4f6b6bd in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f84b8985e41 in ?? () from /usr/lib/nvidia-319/tls/libnvidia-tls.so.319.32 #2 0x7f84c344e670 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f84c340f1cc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f84c340f63b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f84c340fb0a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f84b2f53b66 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x7f84c34340f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f84c3aecf6e in start_thread (arg=0x7f84af0ce700) at pthread_create.c:311 #9 0x7f84c4f799cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 5 (Thread 0x7f84ae8cd700 (LWP 14965)): #0 0x7f84c4f6cf7d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f84c340f6a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f84c340f7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f84c340f7f9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f84c34340f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f84c3aecf6e in start_thread (arg=0x7f84ae8cd700) at pthread_create.c:311 #6 0x7f84c4f799cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f849b394700 (LWP 14970)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f84c12041cd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f84c1204209 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f84c3aecf6e in start_thread (arg=0x7f849b394700) at pthread_create.c:311 #4 0x7f84c4f799cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f8452e5a700 (LWP 14971)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f84c0f44bbd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f84c1233a76 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f84c3aecf6e in start_thread (arg=0x7f8452e5a700) at pthread_create.c:311 #4 0x7f84c4f799cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f8451937700 (LWP 14972)): #0 0x7f84c3aef0aa in __GI___pthread_mutex_lock (mutex=0x7f8444000a60) at pthread_mutex_lock.c:116 #1 0x7f84c344f3a1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f84c340f798 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f84c7612a76 in QEventDispatcherGlib::processEvents (this=0x7f84440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f84c75e45ef in QEventLoop::processEvents (this=this@entry=0x7f8451936db0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f84c75e48e5 in QEventLoop::exec (this=this@entry=0x7f8451936db0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f84c74e388f in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7f84c74e5f2f in QThreadPrivate::start (arg=0x28b8130) at thread/qthread_unix.cpp:338 #8 0x7f84c3aecf6e in start_thread (arg=0x7f8451937700) at pthread_create.c:311 #9 0x7f84c4f799cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f84c82217c0 (LWP 14963)): [KCrash Handler] #5 0x in ?? () #6 0x7f84c6b005a7 in KGAPI2::AuthWidget::Private::emitError (this=this@entry=0x28b5ca0, errCode=KGAPI2::Unauthorized, msg=...) at /build/buildd/libkgapi-2.0.1/common/authwidget_p.inc.cpp:66 #7
[kontact] [Bug 325666] New: Kontact crash upon launch with no apparent reason
https://bugs.kde.org/show_bug.cgi?id=325666 Bug ID: 325666 Summary: Kontact crash upon launch with no apparent reason Classification: Unclassified Product: kontact Version: 4.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@szentes.org Application: kontact (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.4 Operating System: Linux 3.8.0-30-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: Kontact crash upon launch with no apparent reason - What I was doing when the application crashed: start Kontact, - Unusual behavior I noticed: heavy diskcpu load by other program -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f6e3d5427c0 (LWP 3301))] Thread 5 (Thread 0x7f6e1ebcc700 (LWP 3302)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6e39cc7585 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f6e39cc75d9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f6e3471cf8e in start_thread (arg=0x7f6e1ebcc700) at pthread_create.c:311 #4 0x7f6e3aabfe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f6dde2c9700 (LWP 3303)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6e39a0da09 in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f6e39cf5cee in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f6e3471cf8e in start_thread (arg=0x7f6dde2c9700) at pthread_create.c:311 #4 0x7f6e3aabfe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f6dcbfff700 (LWP 3328)): #0 0x7f6e3aab33cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f6e3405a1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6e3405a304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6e3bee5036 in QEventDispatcherGlib::processEvents (this=0x7f6dc40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f6e3beb538f in QEventLoop::processEvents (this=this@entry=0x7f6dcbffed90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6e3beb5618 in QEventLoop::exec (this=this@entry=0x7f6dcbffed90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6e3bdb7410 in QThread::exec (this=this@entry=0x1dbfb40) at thread/qthread.cpp:542 #7 0x7f6e3be96edf in QInotifyFileSystemWatcherEngine::run (this=0x1dbfb40) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x7f6e3bdb9bec in QThreadPrivate::start (arg=0x1dbfb40) at thread/qthread_unix.cpp:338 #9 0x7f6e3471cf8e in start_thread (arg=0x7f6dcbfff700) at pthread_create.c:311 #10 0x7f6e3aabfe1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f6dcaf6f700 (LWP 3336)): [KCrash Handler] #6 0x7f6e3a9fd037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7f6e3aa00698 in __GI_abort () at abort.c:90 #8 0x7f6e3aa3a5ab in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f6e3ab4d860 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 #9 0x7f6e3aa46a46 in malloc_printerr (ptr=0x17a3f40, str=0x7f6e3ab49852 invalid fastbin entry (free), action=3) at malloc.c:4902 #10 _int_free (av=optimized out, p=0x17a3f30, have_lock=0) at malloc.c:3758 #11 0x7f6e3be03488 in QString::free (d=0x17a3f40) at tools/qstring.cpp:1235 #12 0x7f6e37432c89 in ~QString (this=0x2309910, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qstring.h:880 #13 QDBusMessagePrivate::~QDBusMessagePrivate (this=0x23098f0, __in_chrg=optimized out) at qdbusmessage.cpp:72 #14 0x7f6e37432d9f in QDBusMessage::~QDBusMessage (this=0xce5, __in_chrg=optimized out) at qdbusmessage.cpp:537 #15 0x7f6e3742e8ad in ~QDBusCallDeliveryEvent (this=0x25ea1d0, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #16 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x25ea1d0, __in_chrg=optimized out) at qdbusintegrator_p.h:93 #17 0x7f6e3beba17a in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x17c71b0) at kernel/qcoreapplication.cpp:1586 #18 0x7f6e3beba4a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463 #19 0x7f6e3bee4e83 in
[kmail2] [Bug 312025] unnecessary HTML code is added to e-mail
https://bugs.kde.org/show_bug.cgi?id=312025 --- Comment #17 from Mark mrkf...@yahoo.co.nz --- it's been a while. Any movement on this bug? -- 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 265653] Error after filter moves message to different folder
https://bugs.kde.org/show_bug.cgi?id=265653 --- Comment #5 from Mark Fraser mfraz74+...@gmail.com --- Still seeing this with KDE 4.10.5. When I start KMail, I'm getting 10 or so errors saying Can't move message -- 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 124216] Kmail runs out of memory when importing large Outlook Express mailboxes
https://bugs.kde.org/show_bug.cgi?id=124216 --- Comment #12 from Mark Wagner carni...@gmail.com --- Retesting will need to wait for Bug 322303 to be resolved. -- 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 308122] After some weeks downtime, google calendar fetch fails. The requested minimum modification time lies too far in the past
https://bugs.kde.org/show_bug.cgi?id=308122 --- Comment #9 from Mark Fraser mfraz74+...@gmail.com --- Just tried it and resetting the InstanceCounter doesn't work, it still increments to the next value. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 308122] After some weeks downtime, google calendar fetch fails. The requested minimum modification time lies too far in the past
https://bugs.kde.org/show_bug.cgi?id=308122 --- Comment #8 from Mark Fraser mfraz74+...@gmail.com --- Yes, that is the one I was on about. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 308122] After some weeks downtime, google calendar fetch fails. The requested minimum modification time lies too far in the past
https://bugs.kde.org/show_bug.cgi?id=308122 --- Comment #6 from Mark Fraser mfraz74+...@gmail.com --- Is there any way of resetting the resource number back to zero? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #35 from Mark Fraser mfraz74+...@gmail.com --- Just had a slightly different version of this bug. Folder list was showing 1 unread message for a certain folder which I couldn't read and a few moments later some new messages were added to that folder which I could read, but I still can't see that 1 unread message from before. -- 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 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #27 from Mark Fraser mfraz74+...@gmail.com --- The result of this bug is that I can no longer keep KMail loaded all the time and have to keep closing it in order that I will be able to actually see any new emails that arrive. -- 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
[libkgapi] [Bug 317974] Can't fetch from Google Calendar: Invalid request, service is not registered
https://bugs.kde.org/show_bug.cgi?id=317974 --- Comment #10 from Mark Fraser mfraz74+...@gmail.com --- akonadi_googlecalendar_resource_5(3698)/kdepimlibs (kcalcore): parse error ; string is empty? true akonadi_googlecalendar_resource_5(3698)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 109572 Storage collection id 594 parentCollectionId = -246 akonadi_googlecalendar_resource_5(3698)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: akonadi_googlecalendar_resource_5(3698)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: RFC822 akonadi_googlecalendar_resource_5(3698)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: akonadi_googlecontacts_resource_2(3699)/libakonadi Akonadi::ResourceBase::itemRetrieved: Item does not provide part RFC822 kontact(3066)/akonadiserializer (addressee) Akonadi::SerializerPluginAddressee::deserialize: Empty addressee object! -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[libkgapi] [Bug 317974] Can't fetch from Google Calendar: Invalid request, service is not registered
https://bugs.kde.org/show_bug.cgi?id=317974 --- Comment #11 from Mark Fraser mfraz74+...@gmail.com --- Created attachment 79494 -- https://bugs.kde.org/attachment.cgi?id=79494action=edit akonadi_googlecalendar xsesson_error output from when akonadi_googlecalendar_resource fails. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[libkgapi] [Bug 317974] Can't fetch from Google Calendar: Invalid request, service is not registered
https://bugs.kde.org/show_bug.cgi?id=317974 --- Comment #2 from Mark Fraser mfraz74+...@gmail.com --- Sorry for not replying earlier, but KMail decided to filter the reply to my search box! libkgapi0:amd64 0.4.4-0ubuntu1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 308122] After some weeks downtime, google calendar fetch fails. The requested minimum modification time lies too far in the past
https://bugs.kde.org/show_bug.cgi?id=308122 Mark Fraser mfraz74+...@gmail.com changed: What|Removed |Added CC||mfraz74+...@gmail.com -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 317974] New: Can't fetch from Google Calendar: Invalid request, service is not registered
https://bugs.kde.org/show_bug.cgi?id=317974 Bug ID: 317974 Summary: Can't fetch from Google Calendar: Invalid request, service is not registered Classification: Unclassified Product: Akonadi Version: 4.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: Google Resource Assignee: dvra...@redhat.com Reporter: mfraz74+...@gmail.com CC: kdepim-bugs@kde.org A few weeks after setting up a Google calendar resource, I will start to get errors stating that akonadi_googlecalendar_resource_x: Invalid request, service is not registered. This will keep happening until I delete the resource and install it again and it isn't restricted to just one computer - all devices linked to that account get the same error. Reproducible: Always Steps to Reproduce: 1.Set up a Google calendar resource 2.Wait a few weeks 3.See that the error box starts to appear Actual Results: Error box appears for each calendar in my account -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Mark Constable ma...@renta.net changed: What|Removed |Added CC||ma...@renta.net --- Comment #28 from Mark Constable ma...@renta.net --- Also confirming this bug for 4.10.1 on Archlinux with a dovecot IMAP server. -- 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 311561] Can't save email attachments by drag-and-drop
https://bugs.kde.org/show_bug.cgi?id=311561 --- Comment #10 from Mark Fraser mfraz74+...@gmail.com --- I find an email that has an attachment, and I click and drag from the attachment to Konqueror, the pointer changes from an arrow to a finger and nothing happens. -- 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 311561] Can't save email attachments by drag-and-drop
https://bugs.kde.org/show_bug.cgi?id=311561 --- Comment #8 from Mark Fraser mfraz74+...@gmail.com --- As an update to this bug, I installed Kubuntu 13.04 onto a new laptop and I still can't use drag and drop to save an attachment. -- 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
