[korganizer] [Bug 341545] Timezone offset from current timezone seems to be applied twice
https://bugs.kde.org/show_bug.cgi?id=341545 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 400043] New: Korganizer categories are broken; never stay selected, and duplicate themselves
https://bugs.kde.org/show_bug.cgi?id=400043 Bug ID: 400043 Summary: Korganizer categories are broken; never stay selected, and duplicate themselves Product: korganizer Version: 5.9.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: alexandre.bonn...@linuxfr.eu Target Milestone: --- To sum up, I have an old 2012 ics calendar created by Korganizer between 2005 up until the end of 2012, then all hell broke loose and Korganizer categories got broken. I was since then unable to use korganizer as before (ie. with correctly working categories and categories' colors), but I now need to be able to use Korganizer again. The categories problem still exists 6 years after ; basically you cannot create and use a category; it unselect itself when editing the event/task again, and the category keeps duplicating itself when opening the category list. STEPS TO REPRODUCE I tested 3 things; - with my old calendar and current settings, - with my old calendar and a brand new user, - with a new calendar and a new user. In each case, the bug was there. > With my old calendar and current settings Note: my old calendar has 233087 lines and is 6.9MB big. `grep VEVENT calendar.ics|wc -l` lists 11470 events. `grep VTODO calendar.ics|wc -l` lists 17668 tasks. 1. Open Korganizer 2. Double-click an existing event with a 'Work' category to edit it (You know this is a work event since it's color is correctly shown, and the tooltip does show the correct Work category) 3. Select the 'click to add tags' button to open the categories window 4. See that the 'Work' category (or any other categories) are _unselected_ 5. Additionally see that the 'Work' category is currently duplicated 5 times 6. Cry > with my old calendar and a brand new user 1. Create a new user 2. Login with that new user 3. Open the brand new Korganizer 4. Create a new agenda and point it to the existing 6.9MB ics calendar file 5. Wait 1 hour and 45 minutes for akonadi/korganizer to finish 'importing' it (Akonadi/Korganizer can only import 4.63 events/tasks per seconds, on my 12 core cpus, with 32GB of ram, really?! :/) 6. Go into the settings; there are NO categories shown in the color settings (it looks like those are not imported during the...import) 6. Double-click an existing event you KNOW has the 'Work' category to edit it 7. Select the 'click to add tags' button to open the categories window 8. See that the 'Work' category just appeared in that list, but still is _unselected_ 9. Check the categories on another event (ie. 'Fun'), and see that the categories list is now showing two unselected 'Work' and 'Fun' categories. 10. If you edit any Work event and check the categories list, then you can see that the 'Work' category is duplicated 5+ times, but still all are unselected 10. Cry again > with a new calendar and a new user 1. Create a new user 2. Login with that new user 3. Open the brand new Korganizer 4. Create a few new categories : 'Work', 'Fun', 'Soirée', 'Administrative work' 5. Create an event without categories 6. Create an event with the 'Work' category selected 7. Go into the settings to add a specific color to the 'Work' category (ie. blue) 8. Check that in the agenda view, the 2nd event is correctly colored in blue 9. Double-click on that event (with the 'Work' category) to edit it 10. Click the button next to the falsely advertised placeholder 'click to add tags' field, to open the categories window 11. See that the 'Work' category (or any other categories) are _unselected_ 12. See that the 'Work' category is currently duplicated 2 times 13. Close those windows and re-edit the event then show the tag window; the 'Work' category has been duplicated again 14. Try to cry since you have no tears left OBSERVED RESULT Well, in all cases, the categories at utterly broken, even on a new Kde user with a new agenda. (Is there any QA done for Korganizer?) EXPECTED RESULT Categories should : 1. Be listed directly instead of the 'Click here to add tags' placeholder (separated by a comma), currently they are not and I imagine this is related to this bug 2. Be correctly selected in the categories list, and stay selected between edits 3. Accepts accentuated characters in their names without getting duplicated 4. Not be duplicated in the categories list SOFTWARE VERSIONS (info given by kinfocenter) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION I'm sad, does this help? Let's hope this won't take 6 years again ;P Do you need the original ics file? I tried anonymizing it using https://github.com/collective/plone.app.eventindex/blob/master/anonical.py, but that removes too much information (including the categories). Do you have a script of your own to remove
[akregator] [Bug 400028] akregator segfaults in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest, thread safety issue
https://bugs.kde.org/show_bug.cgi?id=400028 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #2 from Martin Steigerwald --- Christophe, are you sure this is a duplicate of #371511? This bug is upstream report from Debian bug report of mine: libqt5webengine5: Akregator crashes very often, WebEngine related https://bugs.debian.org/910852 What I see here is that Akregator runs stable with external browser. It just crashes when using Qt Webengine as internal browser. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Martin Steigerwald changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #9 from Martin Steigerwald --- Reopening, as crash still happens with Qt 5.11.2. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 --- Comment #8 from Dmitry Shachnev --- It still happens with Qt 5.11.2. There are some fresh stack traces in https://bugs.debian.org/910852. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 --- Comment #7 from Jonathan Marten --- (In reply to Christophe Giboudeaux from comment #6) > (In reply to Jonathan Marten from comment #4) > > Did you create a phabricator task for your patch ? No, because I assumed (from the Qt bugreports) that it had been fixed in 5.9 or certainly in 5.10. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 --- Comment #6 from Christophe Giboudeaux --- (In reply to Jonathan Marten from comment #4) Did you create a phabricator task for your patch ? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Christophe Giboudeaux changed: What|Removed |Added CC||mity...@gmail.com --- Comment #5 from Christophe Giboudeaux --- *** Bug 400028 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 400028] akregator segfaults in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest, thread safety issue
https://bugs.kde.org/show_bug.cgi?id=400028 Christophe Giboudeaux changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christophe Giboudeaux --- *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are the assignee for the bug.
[kcontacts] [Bug 400033] New: Sync of google contacts overwrites local settings
https://bugs.kde.org/show_bug.cgi?id=400033 Bug ID: 400033 Summary: Sync of google contacts overwrites local settings Product: kcontacts Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: axel.br...@gmx.de Target Milestone: --- Make a change to a contact from the google addressbook in Kontact, hit sync - the change is gone (overwritten by google settings) SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 400028] New: akregator segfaults in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest, thread safety issue
https://bugs.kde.org/show_bug.cgi?id=400028 Bug ID: 400028 Summary: akregator segfaults in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest , thread safety issue Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: mity...@gmail.com Target Milestone: --- Forwarded from https://bugs.debian.org/910852. Akregator 18.08.1 with Qt 5.11.2 crashes randomly on various feeds. Qt upstream in https://bugreports.qt.io/browse/QTBUG-71284 says: > It looks like a thread safety issue in kdepim's WebEngineViewer. > QtWebEngine executes interceptors[1] on the IO thread, but > WebEngineViewer's interceptor[2] does not take this into account. > > Since this is a common issue, QtWebEngine 5.13 will have new API[3] > to allow intercepting requests on the main UI thread, but until > then WebEngineViewer's interceptor needs to synchronize with the > UI thread to prevent memory corruption. > > [1] > https://doc.qt.io/qt-5/qwebengineurlrequestinterceptor.html#interceptRequest > [2] > https://lxr.kde.org/source/kde/pim/messagelib/webengineviewer/src/urlinterceptor/networkurlinterceptor.cpp > [3] https://codereview.qt-project.org/235118 Stacktrace: #0 0x7fffed21086c in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #1 0x7fffeeca82a6 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::RepeatingCallback const&, GURL*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7fffeedf86eb in net::URLRequest::Start() [clone .part.109] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7fffedb13bce in content::ResourceLoader::StartRequestInternal() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fffedb148ad in content::ResourceLoader::Resume(bool) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fffedb14a9a in content::ResourceLoader::StartRequest() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fffedb0e1de in content::ResourceDispatcherHostImpl::BeginRequestInternal(std::unique_ptr >, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fffedb0faff in content::ResourceDispatcherHostImpl::BeginNavigationRequest(content::ResourceContext*, net::URLRequestContext*, storage::FileSystemContext*, content::NavigationRequestInfo const&, std::unique_ptr >, content::NavigationURLLoaderImplCore*, mojo::InterfacePtr, mojo::InterfaceRequest, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, unsigned int, content::GlobalRequestID*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fffedafd855 in content::NavigationURLLoaderImplCore::Start(content::ResourceContext*, net::URLRequestContextGetter*, storage::FileSystemContext*, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, std::unique_ptr >, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fffedafd160 in base::internal::Invoker >, std::unique_ptr >), scoped_refptr, content::ResourceContext*, base::internal::UnretainedWrapper, base::internal::UnretainedWrapper, content::ServiceWorkerNavigationHandleCore*, content::AppCacheNavigationHandleCore*, base::internal::PassedWrapper > >, base::internal::PassedWrapper > > >, void ()>::RunOnce(base::internal::BindStateBase*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fffee7a47e8 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fffee7c4eea in base::MessageLoop::RunTask(base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7fffee7c598f in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7fffee7c5b28 in base::MessageLoop::DoWork() [clone .part.202] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7fffee7c8542 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7fffee7e77cb in base::RunLoop::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #16 0x7fffed8fd3fa in content::BrowserThreadImpl::IOThreadRun(base::RunLoop*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #17 0x7fffed8fd8a7 in content::BrowserThreadImpl::Run(base::RunLoop*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #18 0x7fffee808bf8 in base::Thread::ThreadMain() () from
[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 Martin Steigerwald changed: What|Removed |Added Keywords||usability -- 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 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=381850 --- Comment #7 from gr...@kde.org --- Left akonadi and kmail running overnight, and now bumped into a case of "world is going to end" again. Stopped akonadi, quit kmail, bumped sysctl and the messages I previously couldn't read, now were ok again. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400024] function "show source" don't show the source
https://bugs.kde.org/show_bug.cgi?id=400024 jiri.reisc...@ecn.cz changed: What|Removed |Added CC||jiri.reisc...@ecn.cz -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400024] function "show source" don't show the source
https://bugs.kde.org/show_bug.cgi?id=400024 --- Comment #1 from jiri.reisc...@ecn.cz --- Created attachment 115748 --> https://bugs.kde.org/attachment.cgi?id=115748=edit source from the IMAP server diff mailman-got.msq mailman-send.msq 16d15 < 26c25 < =2D V=FDsledky: --- > - V=FDsledky: 30c29,30 <=20 --- > = > 62c62,63 < zas=EDlejte na tzv. request adresu, kter=E1 m=E1 tvar=20 --- > zas=EDlejte na tzv. request adresu, kter=E1 m=E1 tvar = > 79c80,81 <=20 --- > = > 146c148,149 < unsubscribe [address=3Dadresa]=20 --- > unsubscribe [address=3Dadresa] = > 153c156,157 < volbu za heslo, tentokr=E1t bez address=3D.=20 --- > volbu za heslo, tentokr=E1t bez address=3D. = > 233d236 < -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400024] New: function "show source" don't show the source
https://bugs.kde.org/show_bug.cgi?id=400024 Bug ID: 400024 Summary: function "show source" don't show the source Product: kmail2 Version: 5.8.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: jiri.reisc...@ecn.cz Target Milestone: --- Created attachment 115747 --> https://bugs.kde.org/attachment.cgi?id=115747=edit source by Kmail SUMMARY Function "show source" don't show the source exactly. There is different source between kmail source and source in IMAP message file. STEPS TO REPRODUCE 1. select the message and press "V" -function show source" 2. open the message file directly on IMAP server 3. make diff OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- 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 vp11 changed: What|Removed |Added CC||virtualproces...@yahoo.co.j ||p --- Comment #19 from vp11 --- I just wanted to report that this is still a problem. I'm using KDE with Breeze Dark and KMail comes close to unusable for reading and writing e-mails with the default black background. There has to be an easy solution that lets users choose a different "theme" that should work only in KMail. -- You are receiving this mail because: You are the assignee for the bug.