[Reminder Daemon] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 --- Comment #10 from Till Schäfer --- Wow, cool! THX! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458202] Search for messages in kmail does not work anymore... no results at all
https://bugs.kde.org/show_bug.cgi?id=458202 --- Comment #5 from Till Schäfer --- I can confirm the patch is fixing the problem. Thx for the fast help. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 --- Comment #11 from Till Schäfer --- I can confirm the patch is fixing the problem. Thx for the fast help. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 436815] address autocompletion, only addresses from "recent" are showed, not those from the address book
https://bugs.kde.org/show_bug.cgi?id=436815 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de Version|unspecified |5.21.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 Till Schäfer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458202 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458202] Search for messages in kmail does not work anymore... no results at all
https://bugs.kde.org/show_bug.cgi?id=458202 Till Schäfer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458245 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 436815] address autocompletion, only addresses from "recent" are showed, not those from the address book
https://bugs.kde.org/show_bug.cgi?id=436815 Till Schäfer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458245 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 Till Schäfer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=436815 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 --- Comment #9 from Till Schäfer --- Another regression in 20.08.0, that does relate to listing or finding e-mail adresses -> Bug 436815 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458202] Search for messages in kmail does not work anymore... no results at all
https://bugs.kde.org/show_bug.cgi?id=458202 --- Comment #2 from Till Schäfer --- To clarify things, the quick filter on top of the message list (Alt+Q) works, but the search dialog (Tools -> Find Messages...) does not. Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.59-gentoo (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z97X-UD5H -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 --- Comment #8 from Till Schäfer --- Also the regular e-mail search is broken since 5.21.0. Maybe this is related to each other. See Bug 458202 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458202] Search for messages in kmail does not work anymore... no results at all
https://bugs.kde.org/show_bug.cgi?id=458202 Till Schäfer changed: What|Removed |Added Ever confirmed|0 |1 Version|unspecified |5.21.0 CC||till2.schaefer@uni-dortmund ||.de Status|REPORTED|CONFIRMED --- Comment #1 from Till Schäfer --- I can confirm the issue here. This is a recent regression. It worked in 5.20.3/20.04.3. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 --- Comment #7 from Till Schäfer --- Created attachment 151727 --> https://bugs.kde.org/attachment.cgi?id=151727=edit display_message.log I have attached a log of akonadiconsole that was recorded while switching to a new message. The akonadi search returned zero results for the e-mail search for rssfeed@null.invalid (which is part of the contact with the html preference). Thus, this might actually be a bug of akonadi and not kmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 --- Comment #6 from Till Schäfer --- Since it was referenced in the duplicate bug and it looked related to the issue, I have tried to revert https://invent.kde.org/pim/kmail/commit/f894cffa2b7ea91b86bc7754e6dd51495de312d3 of Bug 395711. However, it does not fix the issue. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 Till Schäfer changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 --- Comment #2 from Till Schäfer --- Created attachment 151548 --> https://bugs.kde.org/attachment.cgi?id=151548=edit example html message of contact -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 --- Comment #1 from Till Schäfer --- Created attachment 151547 --> https://bugs.kde.org/attachment.cgi?id=151547=edit contact settings -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458245] New: Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 Bug ID: 458245 Summary: Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings Product: kmail2 Version: 5.21.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- After upgrading to kmail 5.21, the per contact settings for html/plain preference and remote content retrieval are no longer applied (see attached screenshot for an example). This is a regression in the current version, since it worked flawlessly in version 5.20.3. I have already tried to modify the contact and save it again but had no luck. Per folder setting for html preference is still applied correctly. Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.59-gentoo (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z97X-UD5H -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455472] Reminders crashes on login
https://bugs.kde.org/show_bug.cgi?id=455472 Till Schäfer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=457090 --- Comment #5 from Till Schäfer --- this not fixed completely -> see Bug 457090 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455472] Reminders crashes on login
https://bugs.kde.org/show_bug.cgi?id=455472 Till Schäfer changed: What|Removed |Added Component|general |general Version|unspecified |5.20.2 Product|kalendar|Reminder Daemon Assignee|claudio.cam...@gmail.com|kdepim-bugs@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 --- Comment #22 from Till Schäfer --- (In reply to Bernhard E. Reiter from comment #21) > One more usability degradation: > > ### confusing "decline" button > > The reminding dialog per appointment remnder offer me a "decline" option > (in German "Ablehnen"). I am unsure what is does. Usually "decline" (and > more so "Ablehnen") for an appointment would mean that I want to refuse to > make the appointment, especially when this is a meeting in the Kalender this > would potentially mean that I inform the others that I will not participate > in the meeting. I guess that this is not what the button does, it probably > just declines being remined of this meeting. However that is not clear from > the presentation of the dialog. With no localization (i.e., English language) this is called "dismiss". IMO, a fitting German translation would be "Verwerfen". -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 --- Comment #18 from Till Schäfer --- (In reply to Volker Krause from comment #16) Thank you for the explanation. That clears things up (also about the motivation to replace korgac). Here are some of my use cases (1) Some event your need to participate. I would like to differentiate here a bit more. (1a) As you described. A meeting, where you need some short lived prepare time in advance. For example: online meetings, a meeting at work in the room next door. Here a default delay of 5 minutes might be a good compromise. you can configure a second reminder as a workaroud to not forget the event during preparation, e.g., 2 minutes before the event. (1b) A meeting where you need longer time to prepare. E.g. make some presentation. I used to configure a very early reminder and a late reminder in that case. I think this actually mixes up (1a) and (2). (1c) A real meeting with someone where you need longer time to get there. For example: going with the kids to the doctor, doing some sport in a remote location, etc. As for (1a) you may need some prepare time, which you may want to delay. However there are some other use cases for delayed reminders. For example, if you do not know the exact time of someone who will pick you up to arrive you may enter en early reminder and delay it according to more recent information. The same is true for public transport, where you may just take a second option because the first one is missed, canceled or delayed. Sometimes this use case is not perfectly separable from (1a). For example, if you have a real life meeting at work and you do not know if you are at already at work before that event starts or you actually need to get there (e.g., because you are working form home at that day). At the time the event is put into the calendar, you may not be able to know which case is true. (1d) Some event that is not exactly timed. E.g. Meet with some friend in the "afternoon". In this case i often just create an event for the full afternoon, such that this time is somehow blocked and I do not accidentally add another event there. The reminder is set at the earliest possible time of that event, such that i am actually remembered and may delay it according to recent information or my personal preference (e.g. I want to finish some other stuff and just shift it an our, because that would still be early enough to not upset the other person.) So this is also an example for shifting the reminder past the start of an event. (2) Task management. (2a) Prepare for an event with larger task. Eg. make presentation. Some limited delay possible (2b) Some TODO. For example: call someone, do the kitchen job at work. In general there are some workaround for delaying reminders: (a) Setting up real TODOs instead of calendar events. IMO this is only well suited for one time events, e.g., a one time call and you may still want to delay a TODOs reminder. But at least it will stay there with a high priority in the list of TODOs. However, TODOs face other limitations as given below: -> Recurring Events. TODOs cannot be repeated every xth week or so. E.g., do the kitchen job every forth week at work. In that kitchen job example, I used to set up a reminder at the start of the work day. Then I delay it to a suitable time depending on other work that needs to be done and the situation in the kitchen (e.g. dishwasher is not full jet, lets look at it in another 2 hour. This delay is unpredictable). Usually the other blocking events are not known at the time of creation of the kitchen job event. So configuring a suitable reminder time is not an option. Especially, I do not want to reconfigure that event for every recurrence. -> An calendar event depended TODO. This is basically the prepare for something situation with and extensive amount of preparation time. When creating a second TODO for preparation in addition to that calendar event, the TODO is decoupled from the event. If the event is than moved to another day or deleted you need to modify that decoupled TODO as well, which is very error prone and cumbersome. Thus, I do not use TODOs in that case. (b) Using multiple reminders from the start. As stated previously, not every event is fully understood at the time of creation. The situation might change dynamically and thereby an a-priori creation of suitable reminders is not possible. Outlook / Proposal: I think, the above use cases are very hard to archive with some well chosen default delay options. Thus, I suggest to provide a default delay as is (i.e., the 5 minutes) and add another button "custom delay" that opens another dialog with an option to specify a delay time. Some other calendars such as business calendar 2 (android) take a similar approach to have a custom dialog for more advanced reminder handling. Other things like the direct editing of an event might not be so important to presen
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 --- Comment #14 from Till Schäfer --- Created attachment 148553 --> https://bugs.kde.org/attachment.cgi?id=148553=edit screenshot of hamburger menu in notifications (In reply to Volker Krause from comment #13) > We cannot have the same level of detail for the suspend time UI as the old > dialog had, system notifications are much more restricted in that regard. > However, there is certainly room to improve the current system. > > The 5 minute interval makes sense for events at a fixed time in say the next > hour or so (eg. meetings or calls) I think. For events in the more distant > future, all day events, todos (or events used to represent tasks) we can > probably find better defaults. Something proportional to the distance to the > event would seem like it would address at least some of the problems? That does not really fit my use cases (see also Bug 453298). For example, the duration of a phone call or meeting does not depend on distance of the event. What would make more sense to me is a constant distance before the event. But also in this case a single duration would most probably be not enough to be useful in the majority of use cases. Some Ideas here (I am not very familiar with the implementation specific limitations, so please say if they are not worthwhile to consider). A) Is it possible to have a drop down button that let you select a list of default snooze times? Having just multiple intervals with good (maybe configurable defaults) would make more sense to me, if a custom input is not possible. For example: 5 Minutes, 30 Minutes, 1 Hour, 2 Hours, 5 Hours, 1 Day, 1 Hour before the even, 30 minutes before the event start, 5 minuted before the event, when the event starts. B) When copying a file, there is a hamburger menu in the notification area, where i get full access to file operations about the copied file (see screenshot). If a direct drop down button is not possible for the snooze button (see A), it maybe possible to give advanced options in such an hamburger menu. I think such a drop down menu would also make sense for things like a direct editing of events (see Bug ). C) maybe it is possible to open another message box that asks about a custom delay if such an option is available (e.g., through A or B) D) Is it possible to display more complex widgets than a simple line based menu for the hamburger? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453299] kalendarac: Notifications miss option to edit event directly
https://bugs.kde.org/show_bug.cgi?id=453299 --- Comment #2 from Till Schäfer --- Created attachment 148530 --> https://bugs.kde.org/attachment.cgi?id=148530=edit highlighted event in Korganzer I still think that an edit button would make things easier. First, simply having an edit button is a one click solution, while the current solution would be to click the notification, and editing the event in a second step. Second, there are some issues, that are more Korganizer related, which make the "Edit the highlighted event in Korganizer" step cumbersome: * The highlighted event is barely visible to me. Can you see the highlighted event in the attached screenshot? For me that is only visible if multiple entries from the same calendar are next to each other. In this case I can see a slight color difference in direct comparison. * The details view (left part of the screenshot), which shows event details does not have an edit functionality as well. To conclude: I now have to search the event (e.g. in the agenda view) which matches the details view. This requires a significant amount of cognitive overhead in order to edit it. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453299] kalendarac: Notifications miss option to edit event directly
https://bugs.kde.org/show_bug.cgi?id=453299 Till Schäfer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 Till Schäfer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 Till Schäfer changed: What|Removed |Added Keywords||regression --- Comment #10 from Till Schäfer --- Bug 453299: kalendarac: Notifications miss option to edit event directly -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453300] New: kalendarac: Notifications click removes the event form notification history
https://bugs.kde.org/show_bug.cgi?id=453300 Bug ID: 453300 Summary: kalendarac: Notifications click removes the event form notification history Product: Akonadi Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- When clicking a reminder event of kalendarac, the event is highlighted in Korganizer for me. By doing so the notification popup as well as the notification history entry is removed. While the former is expected, the latter makes not sense to me. The notification history should make it possible to re-access the event after the popup disappeared. Removing it from history effectively disables the history feature. On use case of the history would be for example, that someone gets distracted by something else after clicking, but not handling the event. Then it would be useful to just have a look into the history to bring up the event again. Thus, I propose to keep the history entry when clicking an event (i.e., handled such as timeouts). Instead, the history entry should be only removed, when the close button (x) is pressed as for other notification entries. Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-gentoo-r1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453299] New: kalendarac: Notifications miss option to edit event directly
https://bugs.kde.org/show_bug.cgi?id=453299 Bug ID: 453299 Summary: kalendarac: Notifications miss option to edit event directly Product: Akonadi Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- The replacement of korgac does no longer support the direct editing of an event from the reminder popup. I propose to re-implement this previous feature. Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-gentoo-r1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 --- Comment #9 from Till Schäfer --- (In reply to Till Schäfer from comment #8) > I would like to add that the new notification also misses the remind later > function for other durations than 5 minutes. > > I used this a lot. For example when I was in a phone call and a reminder > popped up, i said remind me in a hour or so. Now, I am either bothered every > 5 minutes or I have to re-configure the event in Korganizer, which is quite > cumbersome. Bug 453298: kalendarac: Notifications miss option to remind later with other time duration than 5 minutes -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453298] New: kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 Bug ID: 453298 Summary: kalendarac: Notifications miss option to remind later with other time duration than 5 minutes Product: Akonadi Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- With the removal of korgac, the calendar notifications now miss an option to remind later other than 5 minutes. I had several use cases for this remind later functionality. Here are some examples: 1. I often trigger a reminder well ahead of an event, because I need some time to prepare myself for that event (e.g. read some protocol of a previous meeting). When I am currently doing something else I often delayed the reminder to remind me again when my current doing is no longer interrupted or the other event becomes time critical. With the 5 minutes delay it is impossible to work without disturbance if my current doing is taking another hour or so. 2. Sometimes events span several days (e.g. at some week I am responsible to clean the coffee machine at work). So i configure one reminder each day. However, when I am currently not close to the kitchen, I let me remind later, when I know I am back in office. Of course it is also possible to re-configure an event. However, this i A. very cumbersome B. not very good for periodic events (e.g. the the periodic coffee machine job of example 2) Thus, I propose the re-implement this regressed feature. Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-gentoo-r1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 340204] Korganizers reminder is up to one minute late
https://bugs.kde.org/show_bug.cgi?id=340204 Till Schäfer changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Till Schäfer --- 22.04 removed korgac and the current implementation does not have the issue anymore -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #8 from Till Schäfer --- I would like to add that the new notification also misses the remind later function for other durations than 5 minutes. I used this a lot. For example when I was in a phone call and a reminder popped up, i said remind me in a hour or so. Now, I am either bothered every 5 minutes or I have to re-configure the event in Korganizer, which is quite cumbersome. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 452285] New: Cannot disable or enable plugin conponents, such as KJots or Zanshin, anymore
https://bugs.kde.org/show_bug.cgi?id=452285 Bug ID: 452285 Summary: Cannot disable or enable plugin conponents, such as KJots or Zanshin, anymore Product: kontact Version: 5.19.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- In previous versions of Kontact, I was able to disable and enable components (e.g., KJots, Calendar, Zanshin) by enableing or disabling a checkbox in front of the component in the settings window. Now I cannot find any such option anymore, which is a problem in two ways: 1. I cannot re-enable previously disabled views 2. The components sidebar is cluttered with irrelevant components and this sidebar is different on different computers regarding the components installed there. For example, if Zanshin is not installed the component is not show. This also changes short cut assignments, since Ctrl+Number is associated with the ordered view in that sidebar. This in turn makes them hard to use when working in different environments. Current workaround is to enable/disable plugins manually via kontactrc (see my example below). Thus, I would like to see an option again to enable / disable components. [Plugins] kontact_akregatorpluginEnabled=false kontact_journalpluginEnabled=false kontact_kaddressbookpluginEnabled=true kontact_kjotspluginEnabled=false kontact_kmailpluginEnabled=true kontact_knodepluginEnabled=false kontact_knotespluginEnabled=false kontact_korganizerpluginEnabled=true kontact_ktimetrackerpluginEnabled=true kontact_plannerpluginEnabled=true kontact_specialdatespluginEnabled=true kontact_summarypluginEnabled=false kontact_todopluginEnabled=true kontact_zanshinpluginEnabled=false Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.26-gentoo (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 340204] Korganizers reminder is up to one minute late
https://bugs.kde.org/show_bug.cgi?id=340204 Till Schäfer changed: What|Removed |Added Version|5.15.3 |5.18.2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Till Schäfer changed: What|Removed |Added Version|unspecified |5.15.3 --- Comment #49 from Till Schäfer --- same here with recent package versions (Akonadi 5.15.3 / 20.08.3). Should be a assigned to frameworks/kdav now, or am I wrong? Operating System: Gentoo Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.11-gentoo OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.9 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397703] Kmail2 5.9.0: Message list shows read mails as unread
https://bugs.kde.org/show_bug.cgi?id=397703 Till Schäfer changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #8 from Till Schäfer --- does not occur to me in 5.15.3 anymore -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 369247] Kontact: settings between Kontact and components (e.g. KMail) are not synchronized
https://bugs.kde.org/show_bug.cgi?id=369247 Till Schäfer changed: What|Removed |Added Summary|Kontact 5.9.0: settings |Kontact: settings between |between Kontact and |Kontact and components |components (e.g. KMail) are |(e.g. KMail) are not |not synchronized|synchronized -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 369247] Kontact 5.9.0: settings between Kontact and components (e.g. KMail) are not synchronized
https://bugs.kde.org/show_bug.cgi?id=369247 Till Schäfer changed: What|Removed |Added Version|5.9.0 |5.15.3 --- Comment #5 from Till Schäfer --- still valid for 5.15.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 329964] Kmail does not show the encryption symbol in message list for inline pgp mails
https://bugs.kde.org/show_bug.cgi?id=329964 Till Schäfer changed: What|Removed |Added Version|5.9.0 |5.15.3 Summary|Kmail2 5.9.0 does not show |Kmail does not show the |the encryption symbol in|encryption symbol in |message list for inline pgp |message list for inline pgp |mails |mails --- Comment #5 from Till Schäfer --- still valid for 5.13.3 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 340204] Korganizers reminder is up to one minute late
https://bugs.kde.org/show_bug.cgi?id=340204 Till Schäfer changed: What|Removed |Added Version|5.9.0 |5.15.3 Summary|Korganizers 5.9.0 reminder |Korganizers reminder is up |is up to one minute late|to one minute late --- Comment #3 from Till Schäfer --- still valid for 5.15.3 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 373617] Korganizer 5.9.0 / DAV Resource: "Update Calendar Folder" is not working
https://bugs.kde.org/show_bug.cgi?id=373617 Till Schäfer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Till Schäfer --- "Update Calendar" is now greyed out on calendar folders -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 426094] New: Kontact crash after restart
https://bugs.kde.org/show_bug.cgi?id=426094 Bug ID: 426094 Summary: Kontact crash after restart Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Application: kontact (5.15.0 (20.08.0)) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.7.19-gentoo x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: I have restartet the kontakt application, since some calendar items where not displayed at all. During restart, tha pplication crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 QSortFilterProxyModelPrivate::updateChildrenMapping(QModelIndex const&, QSortFilterProxyModelPrivate::Mapping*, Qt::Orientation, int, int, int, bool) (this=0x56425a364430, source_parent=..., parent_mapping=0x56425a4779a0, orient=Qt::Vertical, start=0, end=0, delta_item_count=1, remove=false) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/tools/qhash.h:414 #7 0x7fb62c72624b in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int, int, Qt::Orientation) (this=0x56425a364430, source_parent=..., start=, end=0, orient=Qt::Vertical) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qsortfilterproxymodel.cpp:972 #8 0x7fb62c7295c6 in QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) (this=0x56425a364430, source_parent=..., start=0, end=0) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qsortfilterproxymodel.cpp:1661 #9 0x7fb62c72a27e in QSortFilterProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qsortfilterproxymodel.h:199 #10 0x7fb62c77fcdc in doActivate(QObject*, int, void**) (sender=0x56425a349060, signal_index=13, argv=0x7ffc49383dd0) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #11 0x7fb62c779b5f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x56425a349060, m=m@entry=0x7fb62ca22060 , local_signal_index=local_signal_index@entry=10, argv=argv@entry=0x7ffc49383dd0) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/kernel/qobject.cpp:3946 #12 0x7fb62c6fab5e in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=this@entry=0x56425a349060, _t1=..., _t2=, _t3=, _t4=...) at .moc/moc_qabstractitemmodel.cpp:592 #13 0x7fb62c70309f in QAbstractItemModel::endInsertRows() (this=0x56425a349060) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qabstractitemmodel.cpp:2777 #14 0x7fb62c75 in QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&, QVector const&, QModelIndex const&, Qt::Orientation, bool) (this=0x56425a356d70, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=Qt::Vertical, emit_signal=true) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qsortfilterproxymodel.cpp:922 #15 0x7fb62c7264cb in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int, int, Qt::Orientation) (this=, source_parent=..., start=, end=, orient=Qt::Vertical) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qsortfilterproxymodel.cpp:1033 #16 0x7fb62c7295c6 in QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) (this=0x56425a356d70, source_parent=..., start=0, end=0) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qsortfilterproxymodel.cpp:1661 #17 0x7fb62c72a27e in QSortFilterProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/itemmodels/qsortfilterproxymodel.h:199 #18 0x7fb62c77fcdc in doActivate(QObject*, int, void**) (sender=0x7fb5f404c090, signal_index=13, argv=0x7ffc49384160) at /var/tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #19 0x7fb62c779b5f in
[kmail2] [Bug 363027] Per folder HTML settings are not working
https://bugs.kde.org/show_bug.cgi?id=363027 Till Schäfer changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #12 from Till Schäfer --- oh, I mixed that up. sry for the noise. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363027] Per folder HTML settings are not working
https://bugs.kde.org/show_bug.cgi?id=363027 Till Schäfer changed: What|Removed |Added Version|5.9.0 |5.13.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363027] Per folder HTML settings are not working
https://bugs.kde.org/show_bug.cgi?id=363027 Till Schäfer changed: What|Removed |Added Ever confirmed|1 |0 Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #10 from Till Schäfer --- I do not see the direct relation to Bug 375314 despite Comment 8 mentioning it. So lets keep the two separate until we can directly link them to the same error source. I have "HTML email disabled by default". Thus, my setting does not apply to the other bug in this asppect. And yes, I can still reproduce the issue with - KDEPIM 5.13.3 (19.12.3) - Frameworks 5.69.0 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 412751] Invalid RRULE in Timezone Component with libical 3.0.6
https://bugs.kde.org/show_bug.cgi?id=412751 --- Comment #13 from Till Schäfer --- just a guess: VTIMEZONE is related to daylight saving time. Thus, you may need to select a time zone (maybe also system time zone?) that has a daylight saving time. I have my system configured to the german time zone for example. see also https://stackoverflow.com/a/42941087 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 385364] Timezone RRULE entry has bot UNTIL and COUNT property
https://bugs.kde.org/show_bug.cgi?id=385364 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #13 from Till Schäfer --- Version 3.0.6 of libical now produces completely invalid RRULE entries: "RRULE:ERROR: No Value" (Bug 412751) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 412751] Invalid RRULE in Timezone Component with libical 3.0.6
https://bugs.kde.org/show_bug.cgi?id=412751 Till Schäfer changed: What|Removed |Added Summary|Invalid RRULE in Timezone |Invalid RRULE in Timezone |Component |Component with libical ||3.0.6 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 412751] Invalid RRULE in Timezone Component
https://bugs.kde.org/show_bug.cgi?id=412751 --- Comment #11 from Till Schäfer --- I can confirm, that a downgrade to libical 3.0.5 is a working workaround ;-) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 412751] Invalid RRULE in Timezone Component
https://bugs.kde.org/show_bug.cgi?id=412751 Till Schäfer changed: What|Removed |Added Version|5.12.1 |5.12.2 CC||till2.schaefer@uni-dortmund ||.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Till Schäfer --- I can confirm this error on Gentoo. Synchronization of tasks with DavX/Task on my phone now fail if I specify a due date in my todos. KDE Apps: 19.08.2 KDE Frameworks: 5.63.0 libical: 3.0.6 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 392092] akonadi_control crash on first start
https://bugs.kde.org/show_bug.cgi?id=392092 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #23 from Till Schäfer --- I can confirm the crash on every start with akonadi_control 5.11.2: Cannot remove old log file '%s': %s") at global/qlogging.cpp:887 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 Till Schäfer changed: What|Removed |Added Version|5.4.0 |5.9.2 --- Comment #39 from Till Schäfer --- still valid on 5.9.2 with frameworks 5.51.0 and qt 5.11.2 in the meanwhile for everybody frustrated to type killall kontact every few hours: here is a script to detect and kill hanging kmail instances. I have just added it to my kontact.desktop file, such that kontact just starts and does not wait for the hanging instance. #!/bin/bash pid=$(pidof kontact) if [[ $pid != "" ]]; then echo "Running KMail instance found: $pid" windowsofpid=$(xdotool search --pid $pid) if [[ $windowsofpid == "" ]]; then echo "Hanging KMail instance found. Killing..." kdialog --passivepopup "Hanging KMail instance found: $pid. Killing ..." 5 --title "Kill Hanging Kontact Script" kill $pid fi fi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397703] Kmail2 5.9.0: Message list shows read mails as unread
https://bugs.kde.org/show_bug.cgi?id=397703 --- Comment #6 from Till Schäfer --- does not seem to be a duplicate then -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397703] Kmail2 5.9.0: Message list shows read mails as unread
https://bugs.kde.org/show_bug.cgi?id=397703 --- Comment #3 from Till Schäfer --- (In reply to sourcemaker from comment #2) > Can you also confirm Bug 397677? does the error persist after an application restart? In my case read mails never change the status to unread. Its only the other way round, i.e., that unread mails sometimes do not change correctly to the status read. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363027] Per folder HTML settings are not working
https://bugs.kde.org/show_bug.cgi?id=363027 Till Schäfer changed: What|Removed |Added Version|5.3.1 |5.9.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 346212] Kontact/KMail-5.9.0 ignores per contact settings about html and external resources synced over dav resource
https://bugs.kde.org/show_bug.cgi?id=346212 Till Schäfer changed: What|Removed |Added Component|general |contacts -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 346212] Kontact/KMail-5.9.0 ignores per contact settings about html and external resources synced over dav resource
https://bugs.kde.org/show_bug.cgi?id=346212 Till Schäfer changed: What|Removed |Added Version|5.3.1 |5.9.0 Summary|Kontact/KMail-5.3.1 ignores |Kontact/KMail-5.9.0 ignores |per contact settings about |per contact settings about |html and external resources |html and external resources |synced over dav resource|synced over dav resource --- Comment #3 from Till Schäfer --- still valid in 5.9.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 369247] Kontact 5.9.0: settings between Kontact and components (e.g. KMail) are not synchronized
https://bugs.kde.org/show_bug.cgi?id=369247 Till Schäfer changed: What|Removed |Added Summary|Kontact 5.4.0: settings |Kontact 5.9.0: settings |between Kontact and |between Kontact and |components (e.g. KMail) are |components (e.g. KMail) are |not synchronized|not synchronized Version|5.4.0 |5.9.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 329964] Kmail2 5.9.0 does not show the encryption symbol in message list for inline pgp mails
https://bugs.kde.org/show_bug.cgi?id=329964 Till Schäfer changed: What|Removed |Added Summary|Kmail2 5.7.3 does not show |Kmail2 5.9.0 does not show |the encryption symbol in|the encryption symbol in |message list for inline pgp |message list for inline pgp |mails |mails Version|5.7.2 |5.9.0 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 340204] Korganizers 5.9.0 reminder is up to one minute late
https://bugs.kde.org/show_bug.cgi?id=340204 Till Schäfer changed: What|Removed |Added Version|5.7.2 |5.9.0 Summary|Korganizers 5.7.3 reminder |Korganizers 5.9.0 reminder |is up to one minute late|is up to one minute late -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 373617] Korganizer 5.9.0 / DAV Resource: "Update Calendar Folder" is not working
https://bugs.kde.org/show_bug.cgi?id=373617 Till Schäfer changed: What|Removed |Added Summary|Korganizer 5.7.3 / DAV |Korganizer 5.9.0 / DAV |Resource: "Update Calendar |Resource: "Update Calendar |Folder" is not working |Folder" is not working Version|5.7.2 |5.9.0 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 391769] KOrganizer 5.9.0: Incident times of tasks are not updated when edited by keyboard only
https://bugs.kde.org/show_bug.cgi?id=391769 Till Schäfer changed: What|Removed |Added Summary|KOrganizer 5.7.3: Incident |KOrganizer 5.9.0: Incident |times of tasks are not |times of tasks are not |updated when edited by |updated when edited by |keyboard only |keyboard only -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 391769] KOrganizer 5.7.3: Incident times of tasks are not updated when edited by keyboard only
https://bugs.kde.org/show_bug.cgi?id=391769 Till Schäfer changed: What|Removed |Added Version|5.7.2 |5.9.0 --- Comment #1 from Till Schäfer --- still valid for 5.9.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397703] Kmail2 5.9.0: Message list shows read mails as unread
https://bugs.kde.org/show_bug.cgi?id=397703 --- Comment #1 from Till Schäfer --- This seems to happen more often, when I go through the mails in a faster rate, i.e., press the right/left arrow 3 time a second or so. This often happens when I skip some rss news with dull content. Smells like some race condition.. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397703] New: Kmail2 5.9.0: Message list shows read mails as unread
https://bugs.kde.org/show_bug.cgi?id=397703 Bug ID: 397703 Summary: Kmail2 5.9.0: Message list shows read mails as unread Product: kmail2 Version: 5.9.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Created attachment 114529 --> https://bugs.kde.org/attachment.cgi?id=114529=edit screenshot of the bug (2 mails marked blue in the folder golem with unread count 0) When I go through my mails in the message list, some mails are still marked unread after if have read them. However, the counter in the folder view is decreasing correctly (see screenshot: two mails are painted blue in the folder golem, but the folder count is 0). Changing the folder does not fix the problem. Only a restart of KMail fixes the wrong representation. I allway navigate with the keyboard to switch through the mails (arrow keys), but after the bug occurred, clicking the schroedinger state mail does not fix the wrong representation. This is a regression after upgrading to KMail 5.9.0 from 5.8.3 and happens quiet frequently. complete software stack: - kde apps 18.08.0 - kde frameworks: 5.49 - plasma 5.13.4 - qt 5.11.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388440] scrolling in KMail: "page down" only works once
https://bugs.kde.org/show_bug.cgi?id=388440 --- Comment #11 from Till Schäfer --- This is fixed for me after upgrading to KMail 5.8.3 and frameworks 5.48 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388440] scrolling in KMail: "page down" only works once
https://bugs.kde.org/show_bug.cgi?id=388440 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #10 from Till Schäfer --- I can reproduce this issue with - KMail 5.8.2 - qt 5.11.1 - frameworks 5.47 on gentoo. Page up does always jump to the top and does not scroll one page up. Page down does always jump to the second page (even if i already scrolled further). The previous mentioned workaround (unmap (set to none) shortcut "Scroll Message Down/Up (more)") works for me. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 379842] DAV resource: calendar vanishes and looses settings after akonadi restart
https://bugs.kde.org/show_bug.cgi?id=379842 Till Schäfer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Till Schäfer --- I have not recognized the bug anymore in recent versions -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395616] New: "Open folder where attachment was saved" does not respect the file manager preference
https://bugs.kde.org/show_bug.cgi?id=395616 Bug ID: 395616 Summary: "Open folder where attachment was saved" does not respect the file manager preference Product: kmail2 Version: 5.8.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- If a mail attachment is saved, a message pops up, that contains the button "Open folder where attachment was saved". The action of this button always triggers dolphin, even if another file manager (here: krusader) is selected in the system settings as the default file manager. Thus, kmail should respect the choice of the default file manager configured in the system settings. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the show message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 --- Comment #15 from Till Schäfer <till2.schae...@uni-dortmund.de> --- I have observed, that there is an "expert plugin" for KMail 5.8.0. This plugin re-enables the desired menu option to show the message list structure. I think this is a reasonable solution and for my use case the issue is fixed. There is one smaller aspect I would like to discuss before closing this bug: When the plugin is disabled, it still keeps the shortcut and menu option for "show message structure" accessible. Thus, it still violates the expectation "toolbar" \subseteq "menu". I propose to remove at least the toolbar entry as well, when the expert plugin is disabled. Any objections? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #10 from Till Schäfer <till2.schae...@uni-dortmund.de> --- I am reopening this bug for the following reasons: 1. Your answer is a clear validation of KDEs Community Code of Conduct [1]: - The answer is not respectful. Quote: "stop to cry" is a clear assault on somebody else who is committed to the project. The code of conduct sais: "We do not tolerate personal attacks"! - Your answer is not considerate. It is no problem to disagree and I would accept a decision you make as a package maintainer. However, having multiple voices, from major open source contributors, that have politely pointed out issues with your position should not be put down without at least a few word acknowledging the others issues and explaining why you still think you position is right. - I also think, even as a maintainer one should not act as a dictator. The code of conduct says: "We value tangible results over having the last word in a discussion." 2. This bug was not fixed. If you do not want to fix the issue, this would go in the category WONTFIX and should be marked as such. [1] https://www.kde.org/code-of-conduct/ -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 391769] New: KOrganizer 5.7.3: Incident times of tasks are not updated when edited by keyboard only
https://bugs.kde.org/show_bug.cgi?id=391769 Bug ID: 391769 Summary: KOrganizer 5.7.3: Incident times of tasks are not updated when edited by keyboard only Product: korganizer Version: 5.7.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: incidence editors Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- When editing the start/due time of an existing task with the keyboard only and clicking ok afterwards, the new values are not saved. This only happens to tasks, but not to calendar entries. On the other hand, when selecting the new time by clicking a preset time (i.e., using the drop down list) with the mouse cursor, it works without problems. Even, when some time from the drop down list is selected with the mouse and edited afterwards with the keyboard, the keyboard editing is saved correctly. Thus, I assume that somehow, the keyboard-only edits are not recognized as task modifications. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 340204] Korganizers 5.7.3 reminder is up to one minute late
https://bugs.kde.org/show_bug.cgi?id=340204 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Version|GIT (master)|5.7.2 Summary|Korganizers 5.3.1 reminder |Korganizers 5.7.3 reminder |is up to one minute late|is up to one minute late --- Comment #2 from Till Schäfer <till2.schae...@uni-dortmund.de> --- still valid for 5.7.3 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 373617] Korganizer 5.7.3 / DAV Resource: "Update Calendar Folder" is not working
https://bugs.kde.org/show_bug.cgi?id=373617 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Summary|Korganizer 5.7.2 / DAV |Korganizer 5.7.3 / DAV |Resource: "Update Calendar |Resource: "Update Calendar |Folder" is not working |Folder" is not working -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 373617] Korganizer 5.7.2 / DAV Resource: "Update Calendar Folder" is not working
https://bugs.kde.org/show_bug.cgi?id=373617 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Summary|Korganizer 5.3.3 / DAV |Korganizer 5.7.2 / DAV |Resource: "Update Calendar |Resource: "Update Calendar |Folder" is not working |Folder" is not working Version|5.3.2 |5.7.2 --- Comment #1 from Till Schäfer <till2.schae...@uni-dortmund.de> --- still valid for 5.7.3 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387393] akonadiserver 17.08.03 crashed during idle
https://bugs.kde.org/show_bug.cgi?id=387393 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Summary|akonadiserver 17.08.03 |akonadiserver 17.08.03 |during idle |crashed during idle Version|unspecified |5.6.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 329964] Kmail2 5.7.3 does not show the encryption symbol in message list for inline pgp mails
https://bugs.kde.org/show_bug.cgi?id=329964 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Summary|Kmail2 5.3.1 does not show |Kmail2 5.7.3 does not show |the encryption symbol in|the encryption symbol in |message list for inline pgp |message list for inline pgp |mails |mails -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 329964] Kmail2 5.3.1 does not show the encryption symbol in message list for inline pgp mails
https://bugs.kde.org/show_bug.cgi?id=329964 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Version|5.3.1 |5.7.2 --- Comment #4 from Till Schäfer <till2.schae...@uni-dortmund.de> --- still valid for 5.7.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 390560] KMail 5.7.2 does not save the "view -> disable emoticon" setting
https://bugs.kde.org/show_bug.cgi?id=390560 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #3 from Till Schäfer <till2.schae...@uni-dortmund.de> --- found the other bug, which was already closed *** This bug has been marked as a duplicate of bug 389592 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389592] KMail2 View "disable Emoticons" option is not permanent
https://bugs.kde.org/show_bug.cgi?id=389592 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #3 from Till Schäfer <till2.schae...@uni-dortmund.de> --- *** Bug 390560 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 390560] KMail 5.7.2 does not save the "view -> disable emoticon" setting
https://bugs.kde.org/show_bug.cgi?id=390560 --- Comment #2 from Till Schäfer <till2.schae...@uni-dortmund.de> --- Can you please point to the specific bug? Searching for "kmail emoticon" does not give any matching result. If we have the reference, we should also mark this bug as a duplicate with a reference. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 390560] New: KMail 5.7.2 does not save the "view -> disable emoticon" setting
https://bugs.kde.org/show_bug.cgi?id=390560 Bug ID: 390560 Summary: KMail 5.7.2 does not save the "view -> disable emoticon" setting Product: kmail2 Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- KMail displays emoticons for some text sequences, when viewing incoming mails. This can be disabled by "view -> disable emoticon". However, this setting is cleared after a KMail restart and there is no option in the config dialog to disable emoticons completely. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387393] akonadiserver 17.08.03 during idle
https://bugs.kde.org/show_bug.cgi?id=387393 --- Comment #2 from Till Schäfer <till2.schae...@uni-dortmund.de> --- This is not reproducible... I have only seen it once. Should we close the bug then? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 --- Comment #5 from Till Schäfer <till2.schae...@uni-dortmund.de> --- I use it as an end user, e.g. to verify that a newsletter format of my wordpress instance is correct. I also think, that "toolbar" \subseteq "menu" is a typical pattern and therefore is the expectation of users. Thus, having items randomly appearing only for the on or the other place will only create more confusion. I also do not think that this menu item is very confusing for other users. Alternatively it may be possible to hide advanced features and only show them if you choose the advanced mode? I.e. similar to the vlc approach. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Version|unspecified |5.7.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Summary|KMail 5.7.0 is missing the |KMail 5.7.0 is missing the |Message Structure Option|message structure option -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387931] New: KMail 5.7.0 is missing the Message Structure Option
https://bugs.kde.org/show_bug.cgi?id=387931 Bug ID: 387931 Summary: KMail 5.7.0 is missing the Message Structure Option Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- In Kmail 5.6.3 it was possible to show the message strecture pane by "view -> show message structure". This option is no longer available in 5.7.0. However, it is still needed in some cases, e.g., of malformed/complex mails, to select the right container and it also helps to see/verify the actual mail structure and content (e.g. to see if there is a plain text version). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 337551] Quick Search filters "Subject", "From", "Message Text" and "BCC" search complete header
https://bugs.kde.org/show_bug.cgi?id=337551 --- Comment #5 from Till Schäfer <till2.schae...@uni-dortmund.de> --- almost fixed in 5.7.0. Only "body" does not find anything. other fields work as expected. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 363024] New contact editor misses options to display messages in HTML
https://bugs.kde.org/show_bug.cgi?id=363024 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Till Schäfer <till2.schae...@uni-dortmund.de> --- In the meanwhile the options returned in the contact tab of the contact editor (I have checked here with 5.6.3 and 5.7.0) -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 387393] New: akonadiserver 17.08.03 during idle
https://bugs.kde.org/show_bug.cgi?id=387393 Bug ID: 387393 Summary: akonadiserver 17.08.03 during idle Product: Akonadi Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Application: akonadiserver (5.6.3) (Compiled from sources) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.12.12-gentoo x86_64 Distribution: "Gentoo Base System release 2.4.1" -- Information about the crash: - What I was doing when the application crashed: I let my computer run for a night (idling with akonadi running). During the night the crash popped up. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 [Current thread is 1 (Thread 0x7f4a1c9cb800 (LWP 19030))] Thread 34 (Thread 0x7f4965ffb700 (LWP 20374)): #0 0x7f4a1b40383d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4a1849467c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f4954002e70, timeout=175967, context=0x7f4954000990) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f4954000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3924 #3 0x7f4a1849478c in g_main_context_iteration (context=0x7f4954000990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #4 0x7f4a1bf753eb in QEventDispatcherGlib::processEvents (this=0x7f49540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4a1bf2430a in QEventLoop::exec (this=this@entry=0x7f4965ffadb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f4a1bd814c4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f4a1bd856e1 in QThreadPrivate::start (arg=0x216daa0) at thread/qthread_unix.cpp:368 #8 0x7f4a1a6bf637 in start_thread (arg=0x7f4965ffb700) at pthread_create.c:456 #9 0x7f4a1b40ebbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 33 (Thread 0x7f4967fff700 (LWP 19221)): #0 0x7f4a1b40383d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4a1849467c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f4960003270, timeout=175967, context=0x7f496990) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f496990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3924 #3 0x7f4a1849478c in g_main_context_iteration (context=0x7f496990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #4 0x7f4a1bf753eb in QEventDispatcherGlib::processEvents (this=0x7f4968c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4a1bf2430a in QEventLoop::exec (this=this@entry=0x7f4967ffedb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f4a1bd814c4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f4a1bd856e1 in QThreadPrivate::start (arg=0x21a2030) at thread/qthread_unix.cpp:368 #8 0x7f4a1a6bf637 in start_thread (arg=0x7f4967fff700) at pthread_create.c:456 #9 0x7f4a1b40ebbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 32 (Thread 0x7f49877fe700 (LWP 19210)): #0 g_mutex_unlock (mutex=0x7f4978000990) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gthread-posix.c:1348 #1 0x7f4a18493e49 in g_main_context_query (context=context@entry=0x7f4978000990, max_priority=2147483647, timeout=timeout@entry=0x7f49877fdc74, fds=fds@entry=0x7f4978003070, n_fds=n_fds@entry=2) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3656 #2 0x7f4a184945f7 in g_main_context_iterate (context=context@entry=0x7f4978000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3911 #3 0x7f4a1849478c in g_main_context_iteration (context=0x7f4978000990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #4 0x7f4a1bf753eb in QEventDispatcherGlib::processEvents (this=0x7f49780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4a1bf2430a in QEventLoop::exec (this=this@entry=0x7f49877fddb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f4a1bd814c4 in QThread::exec (this=) at
[kontact] [Bug 387340] New: Kontact 5.6.3 crashed on shutdown
https://bugs.kde.org/show_bug.cgi?id=387340 Bug ID: 387340 Summary: Kontact 5.6.3 crashed on shutdown Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Application: kontact (5.6.3) (Compiled from sources) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.12.12-gentoo x86_64 Distribution: "Gentoo Base System release 2.4.1" -- Information about the crash: - What I was doing when the application crashed: Kontact crashed while closing it. Previously i was in the TODO view. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d0ad6f2c0 (LWP 3776))] Thread 28 (Thread 0x7f2cf57fa700 (LWP 6639)): #0 0x7f2d28ef619d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2d23c9b700 in read (__nbytes=16, __buf=0x7f2cf57f9c50, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7f2bd4004f20) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gwakeup.c:210 #3 0x7f2d23c57102 in g_main_context_check (context=context@entry=0x7f2cd80026a0, max_priority=2147483647, fds=fds@entry=0x7f2cd8001530, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3707 #4 0x7f2d23c57620 in g_main_context_iterate (context=context@entry=0x7f2cd80026a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3926 #5 0x7f2d23c5778c in g_main_context_iteration (context=0x7f2cd80026a0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #6 0x7f2d29a6c26b in QEventDispatcherGlib::processEvents (this=0x7f2cd80024b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f2d29a1b18a in QEventLoop::exec (this=this@entry=0x7f2cf57f9e70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7f2d29878344 in QThread::exec (this=) at thread/qthread.cpp:515 #9 0x7f2d2987c561 in QThreadPrivate::start (arg=0xf0bc0f0) at thread/qthread_unix.cpp:368 #10 0x7f2d25e90637 in start_thread (arg=0x7f2cf57fa700) at pthread_create.c:456 #11 0x7f2d28f05bbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 27 (Thread 0x7f2be7bf2700 (LWP 4042)): #0 g_main_context_query (context=context@entry=0x7f2bdc000990, max_priority=2147483647, timeout=timeout@entry=0x7f2be7bf1d34, fds=fds@entry=0x7f2bdc003220, n_fds=n_fds@entry=2) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3633 #1 0x7f2d23c575f7 in g_main_context_iterate (context=context@entry=0x7f2bdc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3911 #2 0x7f2d23c5778c in g_main_context_iteration (context=0x7f2bdc000990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #3 0x7f2d29a6c26b in QEventDispatcherGlib::processEvents (this=0x7f2bdc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2d29a1b18a in QEventLoop::exec (this=this@entry=0x7f2be7bf1e70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f2d29878344 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f2d2987c561 in QThreadPrivate::start (arg=0x4d38000) at thread/qthread_unix.cpp:368 #7 0x7f2d25e90637 in start_thread (arg=0x7f2be7bf2700) at pthread_create.c:456 #8 0x7f2d28f05bbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 26 (Thread 0x7f2becdf2700 (LWP 4016)): #0 0x7f2d25e97422 in futex_wait_cancelable (private=, expected=0, futex_word=0x1d9eaac) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x1d9ea58, cond=0x1d9ea80) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x1d9ea80, mutex=0x1d9ea58) at pthread_cond_wait.c:655 #3 0x7f2d1b67d5af in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2d1b67dd47 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2d1b67eb10 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f2d1b67b17d in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f2d25e90637 in start_thread (arg=0x7f2becdf2700) at pthread_create.c:456 #8 0x7f2d28f05bbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
[kontact] [Bug 374537] fixing location of kontact window does not obey settings
https://bugs.kde.org/show_bug.cgi?id=374537 --- Comment #6 from Till Schäfer <till2.schae...@uni-dortmund.de> --- workaround: also check the option "Ignore requested geometry" ans select "force" and "yes" -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 379842] New: DAV resource: calendar vanishes and looses settings after akonadi restart
https://bugs.kde.org/show_bug.cgi?id=379842 Bug ID: 379842 Summary: DAV resource: calendar vanishes and looses settings after akonadi restart Product: Akonadi Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Sometimes one of my calendars of the DAV resource vanishes from a list of different calendars. It is my only writable calendar that does so. Restarting the calendar afterwards brings the calendar back, but not its settings. I.e. all calendar properties, such as calendar color or reminder settings are lost. THi especially happens after keeping akonadi running for a longer time (i.e. 2 or 3 days) This bug may be related to Bug 341998, but it is back since i have upgraded to 5.5.0 and is still reproducible for 5.5.1. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379662] Kontact 5.5.0 does not respect KWin window placement
https://bugs.kde.org/show_bug.cgi?id=379662 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379662] Kontact 5.5.0 does not respect KWin window placement
https://bugs.kde.org/show_bug.cgi?id=379662 Till Schäfer <till2.schae...@uni-dortmund.de> changed: What|Removed |Added Version|GIT (master)|5.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379662] New: Kontact 5.5.0 does not respect KWin window placement
https://bugs.kde.org/show_bug.cgi?id=379662 Bug ID: 379662 Summary: Kontact 5.5.0 does not respect KWin window placement Product: kontact Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Kontact seems to do some magic regarding his initial window placement. Typically KWin remembers the last size and position of a window and restores it, when it is opened a second time. This is not the case for kontact. Furthermore, windows rules that are applied initially for the size or position of Kontact do not have any effect (using rule mode force does have). Thus, I guess Kontact does some special handling about the size and position of the window and does some magic about its placement on its own (and bypass KWin rules by doing so). This is also problematic if one is working with dual monitor setup as Kontact is always started on the left screen ---regardless of the primary screen setting or the active screen---. If the left screen then has some horizontal offset, the position of Kontact may be even outside of the visible area! Example: I have to monitors and can only move Kontact to the visible area by using a shortcut. It is always started on screen HDMI1. As you can see from the screen configuration below HDMI1 has an offset of 416 pixels, which is not respected by the Kontact window placement. Screens: - HDMI1 connected 1280x1024+0+416 (normal left inverted right x axis y axis) 380mm x 300mm - DP2 connected primary 2560x1440+1280+0 (normal left inverted right x axis y axis) 600mm x 340mm Proposal: Do not set the size and position of Kontact after initialization. This breaks the placement rules of KWin. -- You are receiving this mail because: You are the assignee for the bug.
