[kontact] [Bug 398577] closing a message subwindow crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=398577 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 375060] week / day / month view not making sense
https://bugs.kde.org/show_bug.cgi?id=375060 Philipp Woelfel changed: What|Removed |Added CC||woel...@gmx.net Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Philipp Woelfel --- Same problem / workaround with KOrganizer 5.10.2 (Manjaro) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 --- Comment #15 from Stas --- It is nearly unbelivable that this issue is solved ;) Thank you very much! No I will be able to use Korganizer again. -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 --- Comment #60 from Peter Humphrey --- (In reply to Martin Steigerwald from comment #59) > KMail has clickable links also in plain text view. In HTML however > the link can go to an entirely different location than what the user gets to > see, while in plain text it cannot. Thus there is a valid security concern. Ah, well in that case, maybe you've just shown the route to a solution: make sure that both views show the same, real value of the link. I can see there may be complications in doing that (different display engines being used) but this seems to be where the insecurity comes from - not from the user, who's unlikely to understand that the black bar is trying to warn him of the distinction you've drawn: what it says is nothing like what it seems to mean. I didn't see it anyway, in spite of having been using the Internet for a bit longer than five minutes. :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 Daniel Vrátil changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.11 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||pim-runtime/2cbb8037d3d7b6c ||e2610129800499b465c892da3 --- Comment #14 from Daniel Vrátil --- Git commit 2cbb8037d3d7b6ce2610129800499b465c892da3 by Daniel Vrátil. Committed on 23/02/2019 at 10:47. Pushed by dvratil into branch 'master'. Google Calendar: fix recurrence instance handling With the fix in LibKGAPI we no longer need any additional magic to handle recurrence instances. FIXED-IN: 5.11 M +1-1CMakeLists.txt M +2-39 resources/google/calendar/calendarresource.cpp https://commits.kde.org/kdepim-runtime/2cbb8037d3d7b6ce2610129800499b465c892da3 -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 --- Comment #13 from Daniel Vrátil --- Git commit 52eb4116f96063fe9a047abdf27f5020ff698687 by Daniel Vrátil. Committed on 23/02/2019 at 10:38. Pushed by dvratil into branch 'master'. Calendar: fix recurrence handling Parse and set recurringEventId and properly distinguish between ID and iCalUID fields, which allows to identify recurrence instances M +1-1CMakeLists.txt M +115 -91 src/calendar/calendarservice.cpp M +10 -1src/calendar/calendarservice.h M +18 -0src/calendar/event.cpp M +12 -0src/calendar/event.h M +1-1src/calendar/eventcreatejob.cpp M +2-2src/calendar/eventdeletejob.cpp M +1-1src/calendar/eventmodifyjob.cpp M +2-2src/calendar/eventmovejob.cpp https://commits.kde.org/libkgapi/52eb4116f96063fe9a047abdf27f5020ff698687 -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 --- Comment #59 from Martin Steigerwald --- (In reply to Peter Humphrey from comment #58) > (In reply to Christoph Feck from comment #55) > > It is a security reason. You could receive an HTML mail that looks like a > > plain text mail, and with HTML you have the ability to embed malicious links > > everywhere. If you have no way to see that the message is actually an HTML > > message, i.e. _outside_ the message viewer, you could click those links > > without being aware that they link to sites that you don't see in the text. > This is completely spurious. If you click on a link, you know it's a link. > If it's a link it must be in HTML. You don't need an ugly great splodge to > tell you it's HTML. > > If you think there are people who can't see this, let them keep the warning. > The rest of us, who've used the Internet for more than five minutes, should > be allowed to switch the splodge off, as we always used to be. Peter, KMail has clickable links also in plain text view. In HTML however the link can go to an entirely different location than what the user gets to see, while in plain text it cannot. Thus there is a valid security concern. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 361006] Akonadi-Agent crash
https://bugs.kde.org/show_bug.cgi?id=361006 Peter Humphrey changed: What|Removed |Added CC||pe...@prh.myzen.co.uk --- Comment #4 from Peter Humphrey --- (In reply to Andrew Crouthamel from comment #1) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. I'm experiencing it today. It's repeatable. Every time I attempt to archive Local Folders, when it reaches a certain group of folders it crashes. These are four folders of mails generated locally by my LAN boxes. I've tried deleting the folders and importing from backup, with one of two effects: either no change, or when I move one of the folders into place I get an error message: Unable to retrieve item from resource: [LRCONFLICT] Resource akonadi_maildir_resource_0 tries to modify item 7406() (in collection 84) with dirty payload. aborting STORE I tried importing from an earlier backup but got the same result. This is Gentoo ~amd64 with kmail-18.12.2 (5.10.2), kde-frameworks 5.55.0. Context: a newly built ~amd64 system, built entirely from sources as Gentoo always is. I wanted ~amd64 rather than the stable versions to get the latest kmail, which has always caused me problems too numerous to mention here. My problem may be unrelated to this bug; please tell me what I can do to help more. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404704] Kmail has no option to show complete message header
https://bugs.kde.org/show_bug.cgi?id=404704 Colin J Thomson changed: What|Removed |Added CC||colin.thom...@g6avk.co.uk -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 --- Comment #58 from Peter Humphrey --- (In reply to Christoph Feck from comment #55) > It is a security reason. You could receive an HTML mail that looks like a > plain text mail, and with HTML you have the ability to embed malicious links > everywhere. If you have no way to see that the message is actually an HTML > message, i.e. _outside_ the message viewer, you could click those links > without being aware that they link to sites that you don't see in the text. This is completely spurious. If you click on a link, you know it's a link. If it's a link it must be in HTML. You don't need an ugly great splodge to tell you it's HTML. If you think there are people who can't see this, let them keep the warning. The rest of us, who've used the Internet for more than five minutes, should be allowed to switch the splodge off, as we always used to be. -- You are receiving this mail because: You are the assignee for the bug.
