[Akonadi] [Bug 484579] Cannot create EWS Account Resource
https://bugs.kde.org/show_bug.cgi?id=484579 --- Comment #2 from avlas --- This happens to me as well. Is there a way to workaround this? I cannot even get to know if EWS works or not in kmail as I cannot configure the account. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 484579] Cannot create EWS Account Resource
https://bugs.kde.org/show_bug.cgi?id=484579 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #24 from avlas --- I still can reproduce the issue -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376565] Automatic spell checking is not working
https://bugs.kde.org/show_bug.cgi?id=376565 avlas changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from avlas --- I cannot reproduce this anymore -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 313667] Kmail2 5.3.1: sent e-mail missing in 'Sent' folder after restoring unsaved composer content
https://bugs.kde.org/show_bug.cgi?id=313667 avlas changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from avlas --- I cannot reproduce this issue anymore -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 459826] New: Open feed in a background tab does not work when triggered by a midle button click
https://bugs.kde.org/show_bug.cgi?id=459826 Bug ID: 459826 Summary: Open feed in a background tab does not work when triggered by a midle button click Classification: Applications Product: akregator Version: 5.21.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- It does work when the setting is to trigger this behavior by a mouse left button click, but not when triggered by a midle button click. In this case the feed is opened in a tab and focus is moved to that tab. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 312608] kmail thread sorting , aggregation - thread leader - most recent message , is not working right
https://bugs.kde.org/show_bug.cgi?id=312608 --- Comment #7 from avlas --- It's several years since I reported this bug and perhaps we are just a few interested in this, so I wonder if the issue is that devs are busy implementing new features and fixing other more important bugs than this (my appreciation from here for your effort!), or whether the problem (of sorting, so the newest emails in a thread appear at top) is due to some technical difficulty from how threads are implemented in kmail. It would be nice to know :) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 459649] New: LanguageTool: language list error when using LanguageTool locally
https://bugs.kde.org/show_bug.cgi?id=459649
Bug ID: 459649
Summary: LanguageTool: language list error when using
LanguageTool locally
Classification: Applications
Product: kmail2
Version: 5.21.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-bugs@kde.org
Reporter: jsar...@gmail.com
Target Milestone: ---
This is not a duplicate of bug439205 but a regression of that fix when using
LanguageTool locally. I informed about this about 1 year ago
https://bugs.kde.org/show_bug.cgi?id=439205#c13 but my comment did not get
attention.
The issue is that the list of available languages are looked at:
https://api.languagetoolplus.com/v2/languages/languages, which returns the
following error:
Error: Unsupported action: 'languages/languages'. Please see
https://languagetool.org/http-api/swagger-ui/#/default
Instead, the list of available languages should be looked at:
https://api.languagetoolplus.com/v2/languages, which returns the proper list:
[{"name":"Arabic","code":"ar","longCode":"ar"},{"name":"Asturian","code":"ast","longCode":"ast-ES"},{"name":"Belarusian","code":"be","longCode":"be-BY"},{"name":"Breton","code":"br","longCode":"br-FR"},{"name":"Catalan","code":"ca","longCode":"ca-ES"},{"name":"Catalan
(Valencian)","code":"ca","longCode":"ca-ES-valencia"},{"name":"Chinese","code":"zh","longCode":"zh-CN"},{"name":"Danish","code":"da","longCode":"da-DK"},{"name":"Dutch","code":"nl","longCode":"nl"},{"name":"Dutch","code":"nl","longCode":"nl"},{"name":"Dutch
(Belgium)","code":"nl","longCode":"nl-BE"},{"name":"English","code":"en","longCode":"en"},{"name":"English","code":"en","longCode":"en"},{"name":"English
(Australian)","code":"en","longCode":"en-AU"},{"name":"English
(Australian)","code":"en","longCode":"en-AU"},{"name":"English
(Canadian)","code":"en","longCode":"en-CA"},{"name":"English
(Canadian)","code":"en","longCode":"en-CA"},{"name":"English
(GB)","code":"en","longCode":"en-GB"},{"name":"English
(GB)","code":"en","longCode":"en-GB"},{"name":"English (New
Zealand)","code":"en","longCode":"en-NZ"},{"name":"English (New
Zealand)","code":"en","longCode":"en-NZ"},{"name":"English (South
African)","code":"en","longCode":"en-ZA"},{"name":"English (South
African)","code":"en","longCode":"en-ZA"},{"name":"English
(US)","code":"en","longCode":"en-US"},{"name":"English
(US)","code":"en","longCode":"en-US"},{"name":"Esperanto","code":"eo","longCode":"eo"},{"name":"French","code":"fr","longCode":"fr"},{"name":"French","code":"fr","longCode":"fr"},{"name":"Galician","code":"gl","longCode":"gl-ES"},{"name":"German","code":"de","longCode":"de"},{"name":"German","code":"de","longCode":"de"},{"name":"German
(Austria)","code":"de","longCode":"de-AT"},{"name":"German
(Austria)","code":"de","longCode":"de-AT"},{"name":"German
(Germany)","code":"de","longCode":"de-DE"},{"name":"German
(Germany)","code":"de","longCode":"de-DE"},{"name":"German
(Swiss)","code":"de","longCode":"de-CH"},{"name":"German
(Swiss)","code":"de","longCode":"de-CH"},{"name":"Greek","code":"el","longCode":"el-GR"},{"name":"Irish","code":"ga","longCode":"ga-IE"},{"name":"Italian","code":"it","longCode":"it"},{"name":"Japanese","code":"ja","longCode":"ja-JP"},{"name":"Khmer","code":"km","longCode":"km-KH"},{"name":"Norwegian
(Bokmål)","code":"nb","longCode":"nb"},{"name":"Norwegian
(Bokmål)","code":"no","longCode":"no"},{"name":"Persian","code":"fa","longCode":"fa"},{"name":"Polish","code":"pl","longCode":"pl-PL"},{"name":"Portuguese","code":"pt","longCode":"pt"},{"name":"Portuguese
(Angola preAO)","code":"pt","longCode":"pt-AO"},{"name":"Portuguese
(Brazil)","code":"pt","longCode":"pt-BR"},{"name":"Portuguese (Moçambique
preAO)","code":"pt","longCode":"pt-MZ"},{"name":"Portuguese
(Portugal)","code":"pt","longCode":"pt-PT"},{"name":"Romanian","code":"ro","longCode":"ro-RO"},{"name":"Russian","code":"ru","longCode":"ru-RU"},{"name":"Simple
German","code":"de-DE-x-simple-language","longCode":"de-DE-x-simple-language"},{"name":"Slovak","code":"sk","longCode":"sk-SK"},{"name":"Slovenian","code":"sl","longCode":"sl-SI"},{"name":"Spanish","code":"es","longCode":"es"},{"name":"Spanish","code":"es","longCode":"es"},{"name":"Spanish
(voseo)","code":"es","longCode":"es-AR"},{"name":"Swedish","code":"sv","longCode":"sv"},{"name":"Tagalog","code":"tl","longCode":"tl-PH"},{"name":"Tamil","code":"ta","longCode":"ta-IN"},{"name":"Ukrainian","code":"uk","longCode":"uk-UA"}]
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 439205] language tool, language list error
https://bugs.kde.org/show_bug.cgi?id=439205 --- Comment #14 from avlas --- (In reply to avlas from comment #13) > I don't think the issue is totally fixed, at least when using the local > instance. The problem in this case is that languages are searched in > the /v2/languages/languages path instead of in the /v2/languages path, where > the actual language list is present (note /ĺanguages is added twice). In the > meantime I disabled the local instance to get it working, but I prefer not > sending my emails on the Internet. In fact, I wonder if my issue might be a regression of the fix -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 439205] language tool, language list error
https://bugs.kde.org/show_bug.cgi?id=439205 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #13 from avlas --- I don't think the issue is totally fixed, at least when using the local instance. The problem in this case is that languages are searched in the /v2/languages/languages path instead of in the /v2/languages path, where the actual language list is present (note /ĺanguages is added twice). In the meantime I disabled the local instance to get it working, but I prefer not sending my emails on the Internet. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #23 from avlas --- (In reply to Laurent Montel from comment #22) > I confirm it. > I will investigate it Thank you -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #21 from avlas --- (In reply to Laurent Montel from comment #20) > (In reply to avlas from comment #19) > > (In reply to Laurent Montel from comment #13) > > > Git commit 137430312149daa2a95109160d236ad7c70d14a6 by Laurent Montel. > > > Committed on 25/04/2019 at 07:11. > > > Pushed by mlaurent into branch 'master'. > > > > > > Fix Bug 406334 - Markdown addon: embedded images (attached to the email) > > > are > > > not displayed > > > FIXED-IN: 5.12.0 > > > > > > M +6-5 > > > kmail/editorconvertertextplugins/markdown/markdowninterface.cpp > > > > > > https://commits.kde.org/kdepim-addons/ > > > 137430312149daa2a95109160d236ad7c70d14a6 > > > > Not sure there has been a regression of some sort, but attached images are > > not displayed in markdown formatted html emails. > > Test case ? > For me it seems working here. Please see: https://i.imgur.com/moqaQSv.png The image is missing and if I send the email anyway, I cannot find the image in the resulting email -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #19 from avlas --- (In reply to Laurent Montel from comment #13) > Git commit 137430312149daa2a95109160d236ad7c70d14a6 by Laurent Montel. > Committed on 25/04/2019 at 07:11. > Pushed by mlaurent into branch 'master'. > > Fix Bug 406334 - Markdown addon: embedded images (attached to the email) are > not displayed > FIXED-IN: 5.12.0 > > M +6-5 > kmail/editorconvertertextplugins/markdown/markdowninterface.cpp > > https://commits.kde.org/kdepim-addons/ > 137430312149daa2a95109160d236ad7c70d14a6 Not sure there has been a regression of some sort, but attached images are not displayed in markdown formatted html emails. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375314] "Toggle HTML Display Mode" button does not work with HTML enabled by default
https://bugs.kde.org/show_bug.cgi?id=375314 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #4 from avlas --- (In reply to keitalbame from comment #3) > You are right. > When I read "directory tree is not created", remembered about the bug I > mentioned because when I first saw the issue, the folders where not being > created in the filesystem. I found out later that they where created on a > different (incorrect) path. I see. It might still be the same underlying issue, but it's not obvious. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #2 from avlas --- It doesn't seem related, as this one doesn't have anything to do with local mail, but not sure. At some point I found an alternative way to add an email account in Kmail that did work. This was some months ago, so I don't totally recall. But for the case other users suffer this, they could explore alternative ways to create the account, as it seems based on my experience that one is troublesome and the other is not. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411647] New: regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 Bug ID: 411647 Summary: regression: adding a new imap account prompts no error but no directory tree is created Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- I tried to add a new imap account. The process triggers no errors and everything seems fine. However, the directory tree (inbox, sent, etc) is not created. Tried several times with same result every time. This is an office 365 account, analogous to another I configured few months before with no issue, so I suppose this is some sort of regression. Also, adding the account to Trojita works just fine, so it doesn't seem to be something internal to the servers. Could you please try to add a new imap account to see if you can reproduce the issue in your system? Not sure if the issue in kmail is specific for office365 imap accounts or general. Any help is more than appreciated! SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-27-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411147] IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147 --- Comment #3 from avlas --- (In reply to Laurent Montel from comment #2) > see > https://www.dvratil.cz/2019/08/kontact-google-integration-issue/ Thank you Laurent. I got bitten by this issue, even though I had my account configured successfully, (I think) after I manually cancelled Kmail synchronization due to a extremely slow internet connection. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411147] IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 --- Comment #6 from avlas --- This happens to me (in KDE neon) most of the times after "Accepting a Google Calendar Invitation Request" in my gmail account. The email that is sent (not always but very frequently, I would say 80% of the times or more) gets stuck and then no more emails can be sent from any account (gmail and others). Saying because if you could reproduce this behavior, it may help to debug and fix the issue. [Note: I have the feeling that this happens more frequently if the akonadi process has been running for a while] -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 --- Comment #2 from avlas --- (In reply to Laurent Montel from comment #1) > yep pim-setting-exporter but that's only settings, right? as I understand it, there is no way one can export (import) everything to (from) a single compressed file -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #18 from avlas --- (In reply to Laurent Montel from comment #17) > now we can define the size of image (using =x) Nice! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #16 from avlas --- (In reply to Laurent Montel from comment #15) > (In reply to avlas from comment #14) > > (In reply to Laurent Montel from comment #13) > > > Git commit 137430312149daa2a95109160d236ad7c70d14a6 by Laurent Montel. > > > Committed on 25/04/2019 at 07:11. > > > Pushed by mlaurent into branch 'master'. > > > > > > Fix Bug 406334 - Markdown addon: embedded images (attached to the email) > > > are > > > not displayed > > > FIXED-IN: 5.12.0 > > > > > > M +6-5 > > > kmail/editorconvertertextplugins/markdown/markdowninterface.cpp > > > > > > https://commits.kde.org/kdepim-addons/ > > > 137430312149daa2a95109160d236ad7c70d14a6 > > > > Great, thanks! > > > > Do you think there could be a way to apply styling? I think it would be the > > last missing piece > > It's still on my todo list (+ some others fix/improvement) > > See you if I will find a fix for it too :) Very much appreciated! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #14 from avlas --- (In reply to Laurent Montel from comment #13) > Git commit 137430312149daa2a95109160d236ad7c70d14a6 by Laurent Montel. > Committed on 25/04/2019 at 07:11. > Pushed by mlaurent into branch 'master'. > > Fix Bug 406334 - Markdown addon: embedded images (attached to the email) are > not displayed > FIXED-IN: 5.12.0 > > M +6-5 > kmail/editorconvertertextplugins/markdown/markdowninterface.cpp > > https://commits.kde.org/kdepim-addons/ > 137430312149daa2a95109160d236ad7c70d14a6 Great, thanks! Do you think there could be a way to apply styling? I think it would be the last missing piece -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #16 from avlas --- (In reply to Laurent Montel from comment #15) > (In reply to avlas from comment #13) > Ok you can't use locale instance until 19.04.1 ;( > Sorry. No big deal, 19.04.1 it's behind the corner :) It's great to see all these nice addons in Kmail, very much appreciated! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #13 from avlas --- (In reply to Laurent Montel from comment #9) > [LanguageTool] > language=en > languagetoolpath=https://languagetool.org/api/v2 It seems I also need to manually add the bool for enabling the local path. Could you please let me know how to add that setting? -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #12 from avlas --- (In reply to Laurent Montel from comment #10) > > If possible, a nice way to implement this could be setting the language of > > LanguageTools in sync with composer's dictionary (this would apply to those > > languages that are available in both addons, while the rest would just use > > default, i.e. English, I guess). > > > > This way the UI would not change and the "magic" would happen under the > > hood. Not sure how hard this may be to implement though. > > The problem is that we don't have the same settings between composer > dictionary and languagetools... > I can try to create a map but not sure that it will easy. > I will investigate it +1 -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #11 from avlas --- (In reply to Laurent Montel from comment #9) > [LanguageTool] > language=en > languagetoolpath=https://languagetool.org/api/v2 Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #8 from avlas --- Excellent! Is it easy for you to show how that settings section looks like in kontactrc/kmail2rc settings? That would be a workaround until the fix is released. > > By the way, having the possibility to easily change the LanguageTools > > language setting in composer would be great as many users write emails > > > > in 2+ languages :) > > > Ok it seems a good idea. > I will look at how to implement it If possible, a nice way to implement this could be setting the language of LanguageTools in sync with composer's dictionary (this would apply to those languages that are available in both addons, while the rest would just use default, i.e. English, I guess). This way the UI would not change and the "magic" would happen under the hood. Not sure how hard this may be to implement though. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #2 from avlas --- (In reply to avlas from comment #1) > In the meantime, to work around this, how should I manually add the > LanguageTools server and language setting to kontactrc? Tried to figure it out checking kontactrc, but couldn't find the way. But I did find a typo in Markdown settings that appear in the [Mardown] section (note the missing 'k') -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #1 from avlas --- It seems LanguageTools settings are not stored in kontactrc. This is the only thing I see: [LanguageToolConfigDialog] Size=500,300 In the meantime, to work around this, how should I manually add the LanguageTools server and language setting to kontactrc? By the way, having the possibility to easily change the LanguageTools language setting in composer would be great as many users write emails in 2+ languages :) -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406680] New: LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 Bug ID: 406680 Summary: LanguageTools: kmail restart loses configuration of local server address in favor of default remote Product: kdepim Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messagecomposer Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- I've download and set up a local server for LanguageTools to test this new functionality (which is very cool, btw). This works fine, but Kmail setting about the location of the server is lost after quitting in favor of the default remote one. Also, it seems I cannot set English (US) instead of English. When I do, the change reverts itself. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #24 from avlas --- (In reply to Laurent Montel from comment #23) > > Sorry, I think I didn't explain myself well. I was not talking here now > > about the conversion from markdown to html, but about highlighting the email > > body in the composer while writing (if/when the markdown button is > > activated). In that case, it would be great to see how markdown keywords > > written in plain text get automatically highlighted. This would help writing > > markdown emails, e.g. to better structure the email or more easily visualize > > markdown typos. > > Ah ok. I don't know if it's possible but indeed I can look at it. Great, thanks -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #22 from avlas --- (In reply to Laurent Montel from comment #21) > (In reply to avlas from comment #20) > > (In reply to Laurent Montel from comment #18) > > > Created attachment 119461 [details] > > > Screenshot > > > > I had some ideas for further enhancement after seeing your screenshot (as > > well as this one http://25.io/mou/img/1...@2x.png): > > > > 1) It would be great if Kmail composer would use KSyntaxHighlighting > > technology as well to ease writing emails in markdown format, so it gets > > automatically enabled when the markdown button in the composer is activated. > > KSyntaxHighlighting highlights only text, it can create a html code but not > for converting > markdown to html. Sorry, I think I didn't explain myself well. I was not talking here now about the conversion from markdown to html, but about highlighting the email body in the composer while writing (if/when the markdown button is activated). In that case, it would be great to see how markdown keywords written in plain text get automatically highlighted. This would help writing markdown emails, e.g. to better structure the email or more easily visualize markdown typos. > > 2) It would be so great to have a live preview (as shown in the link above; > > please note that Kate has already something similar to this) instead of a > > pop-up window. > > We can't do it as composer is a "QTextEdit" and we need a html viewer/editor > for showing > mardown result. QTextEdit is too limited for html. I see. That's a pity, such a feature would probably attract users, especially KDE users using markdown-here in other email client applications or in the browser. I know there is the option but never tried using an external editor for writing emails. I assume this would not be an option for writing emails in markdown either, right? Saying because perhaps one could use Kate for this... > > 3) It would be nice if there could be an option to remember the status of > > the Markdown button in the composer. > > We can do it. I will look at it. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #20 from avlas --- (In reply to Laurent Montel from comment #18) > Created attachment 119461 [details] > Screenshot I had some ideas for further enhancement after seeing your screenshot (as well as this one http://25.io/mou/img/1...@2x.png): 1) It would be great if Kmail composer would use KSyntaxHighlighting technology as well to ease writing emails in markdown format, so it gets automatically enabled when the markdown button in the composer is activated. 2) It would be so great to have a live preview (as shown in the link above; please note that Kate has already something similar to this) instead of a pop-up window. 3) It would be nice if there could be an option to remember the status of the Markdown button in the composer. Please let me know if these ideas make sense and if you would like me to open new bug reports for them, especially points 2 and 3 above, which are not about highlighting. I can easily foresee myself in the near future writing all my emails in markdown format instead of plain text :) -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #19 from avlas --- (In reply to Laurent Montel from comment #18) > Created attachment 119461 [details] > Screenshot Neat! (thank you) -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #17 from avlas --- (In reply to Laurent Montel from comment #16) > Now we can hightlight block. > I need to fix some little bugs but it's good now :) Excellent! [ If you'd have a chance and it's not too much trouble, please attach a screenshot of an example. I'd love to see it in action :) ] -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 --- Comment #11 from avlas --- And unfortunately: "You can't sensibly pass a css file to the library, because non-inline css is handled in the document header and markdown formats the contents of the document body." and wondering... I assume that it would not be proper to use mkd2html directly, right? -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 --- Comment #10 from avlas --- (In reply to avlas from comment #9) > (In reply to avlas from comment #8) > > (In reply to Laurent Montel from comment #6) > > > Discount lib > > > > Mmm, I didn't realize you meant the lib, but makes total sense. I don't > > know, will ask Discount dev... > > May it be using the following function? > > int mkd_css(MMIOT *doc, char **out) allocates a buffer and populates it with > any style blocks found in the document. > > I asked Discount Dev to confirm... This is what I got from Discount Dev: Discount sweeps up `
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 --- Comment #9 from avlas --- (In reply to avlas from comment #8) > (In reply to Laurent Montel from comment #6) > > Discount lib > > Mmm, I didn't realize you meant the lib, but makes total sense. I don't > know, will ask Discount dev... May it be using the following function? int mkd_css(MMIOT *doc, char **out) allocates a buffer and populates it with any style blocks found in the document. I asked Discount Dev to confirm... -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 --- Comment #8 from avlas --- (In reply to Laurent Montel from comment #6) > Discount lib Mmm, I didn't realize you meant the lib, but makes total sense. I don't know, will ask Discount dev... -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #12 from avlas --- (In reply to Laurent Montel from comment #11) > Thanks I will continue to implement it today or tomorrow Thank you very much! If you implement all these enhancements, it's going to be amazing! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 --- Comment #7 from avlas --- (In reply to Laurent Montel from comment #6) > adding a css to generate file is not a problem but how told to Discount lib > that we want to generate tables with specific css ? I just explained it in another (related) issue: https://bugs.kde.org/show_bug.cgi?id=406334 Please let me know if you would encounter any problem -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #10 from avlas --- (In reply to avlas from comment #7) > (In reply to Laurent Montel from comment #5) > > (In reply to avlas from comment #1) > > > I tested this in Discount and works as expected, embedding the image > > > within > > > other markdown content. Could you please consider adding this option? > > > > How did you test it ? > > Could you give me your command line ? > > thanks > > I do: > > mkd2html -G -css github.css mainTest.md mainTest_github.html Forgot to say about the image, which I didn't attach (as it may have copyright). Please change it by one that you have to test. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #9 from avlas --- In addition to the github css style (that I attached) I have another css file from markdown-here. The one I use (and like the most) is the github one, with single exception, the background color that is used in the title row of tables, which is taken from markdown-here. It would be ideal to, for instance, use the github style by default but allow the final user to add a specific css file in settings, if desired. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #7 from avlas --- (In reply to Laurent Montel from comment #5) > (In reply to avlas from comment #1) > > I tested this in Discount and works as expected, embedding the image within > > other markdown content. Could you please consider adding this option? > > How did you test it ? > Could you give me your command line ? > thanks I do: mkd2html -G -css github.css mainTest.md mainTest_github.html -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #8 from avlas --- Created attachment 119433 --> https://bugs.kde.org/attachment.cgi?id=119433&action=edit File of github style for markdown conversion -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #6 from avlas --- Created attachment 119432 --> https://bugs.kde.org/attachment.cgi?id=119432&action=edit File to test markdown format conversion -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #3 from avlas --- (In reply to Laurent Montel from comment #2) > option for what ? > Generating a image.png ? I meant for adding images within context. Imaging you write a markdown email and you refer to one or more images in the body of the email. Discount allows to generate an html version of it that embeds the referenced image in its right place. It would be great if Kmail would benefit from this, so referenced images are embedded in the right places of the email body. For this, Kmail would need to be smart enough to know where to find the image (that needs of course to be attached to the email). I hope I was clearer this time :) -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 --- Comment #5 from avlas --- (In reply to Laurent Montel from comment #4) > v3 branch ? I meant in the v3 branch of discount: https://github.com/Orc/discount/tree/v3 By the way, discount works great with css files. I got a github style css file that makes markdown html conversion look great (tables, blockquotes, etc), IMO far better than just plain markdown. Blockquotes are particularly important for email replies. Would you consider adding the possibility of styling via a css file in Kmail's markdown addon? I think this option would be very appreciated by its users. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 --- Comment #1 from avlas --- I tested this in Discount and works as expected, embedding the image within other markdown content. Could you please consider adding this option? -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366
--- Comment #3 from avlas ---
This is set by default now in Discount v3 branch, which is great. An example of
this is the following:
### This is my list:
- [x] this is set
- [ ] this is not
- and this is a regular list item.
However, to make it work as expected (i.e. removing dots from the checkboxes
and aligning) it requires:
- either adding to the file/email:
.github_checkbox { list-style-type: none; margin-left: -1.5em; }
this option works when converting via: markdown -style < checkbox.md >
checkbox.html
- or (much better option) to create a css file with:
.github_checkbox { list-style-type: none; margin-left: -1.5em; }
this option works when converting via: mkd2html -css checkbox.css checkbox.md
Do you think it be possible to add an option to set a css for mkd2html
conversion (and perhaps add this by default), so that the final user doesn't
have to be aware, neither repeat this for every email?
The css option could also be interesting for:
- styling code highlighting?
- table/blockquote format
[I opened issues in Discount regarding the style of tables and blockquotes. I
hope this will be considered to look similar to github/markdown here. if so, I
will let you know].
--
You are receiving this mail because:
You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #12 from avlas --- (In reply to avlas from comment #11) > (In reply to avlas from comment #10) > > Laurent, Discount dev has finished implementing this and asks if you could > > please test it: > > > > "It Works For Me(tm) -- can the Kmail crew check it out for nontrivial > > external formatting (I don't do any syntax highlighting in my little test > > callback, I just wanted to make certain it works)?" > > Forgot to say that the code is the master branch: > https://github.com/Orc/discount Laurent, it was quite easy to compile discount. If there would be an easy way to check highlighting without compiling kmail (which seems scary!), I'd like to give it a try... -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #11 from avlas --- (In reply to avlas from comment #10) > Laurent, Discount dev has finished implementing this and asks if you could > please test it: > > "It Works For Me(tm) -- can the Kmail crew check it out for nontrivial > external formatting (I don't do any syntax highlighting in my little test > callback, I just wanted to make certain it works)?" Forgot to say that the code is the master branch: https://github.com/Orc/discount -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #10 from avlas --- > It's not necessary to use kpart. We have a lib for my highlighting. > For sure if we have a code block callback I will be able to highlight it. Laurent, Discount dev has finished implementing this and asks if you could please test it: "It Works For Me(tm) -- can the Kmail crew check it out for nontrivial external formatting (I don't do any syntax highlighting in my little test callback, I just wanted to make certain it works)?" -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #9 from avlas --- (In reply to Laurent Montel from comment #8) > (In reply to avlas from comment #7) > > Would "a code block callback so that an external function could apply syntax > > highlighting" be useful for applying highlighting in Kmail via Kpart? > > It's not necessary to use kpart. We have a lib for my highlighting. > For sure if we have a code block callback I will be able to highlight it. Awesome! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #7 from avlas --- Would "a code block callback so that an external function could apply syntax highlighting" be useful for applying highlighting in Kmail via Kpart? -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406332] Markdown addon option 'Enable embedded LaTeX' does not work
https://bugs.kde.org/show_bug.cgi?id=406332 --- Comment #3 from avlas --- (In reply to Laurent Montel from comment #2) > We need a component for generated latex equations. > But kmail is a mailer not an text editor where it can be useful. The readability of emails with displayed equations would be far higher than those having just raw latex. This would be very useful for scientists and engineers. But I understand. I was wondering whether it might be a way to easily render/convert latex equations into images embedded in the html (perhaps using katex or kile). -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 --- Comment #2 from avlas --- (In reply to Laurent Montel from comment #1) > Hi, > it's a configure option to discount. > But I use discount lib, I don't rebuild it. > It's not a flags in lib. > So we can't do it or I missed something Mmm, I asked about it, but I think you're right (https://github.com/Orc/discount/issues/187#issuecomment-382942705): "I can't use another MKD_ flag without breaking the published interface, because the flags are stored in a 32 bit integer and I've already got 32 of them defined. So for the short term it's gotta be configured with the --github-checkbox option to configure.sh" -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406366] New: Markdown addon: please add support for --github-checkbox
https://bugs.kde.org/show_bug.cgi?id=406366 Bug ID: 406366 Summary: Markdown addon: please add support for --github-checkbox Product: kdepim Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messagecomposer Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Right now Markdown addon in Kmail shows this issue https://github.com/Orc/discount/issues/187 This has been fixed (Discount 2.2.4 documentation): (feature) support github checkbox list items (static configuration option) --github-checkbox does the checkbox with html check entities --github-checkbox=input does them with html elements (set to disabled so that people can’t check and uncheck willy-nilly) -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #6 from avlas --- Discount dev replied this: "Discount doesn't know about the structure of codeblocks, so it can't do it natively. I could implement a code block callback so that an external function could apply syntax highlighting, though?" (https://github.com/Orc/discount/issues/203#issuecomment-481283980) Laurent, could you please give your view on this? Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #5 from avlas --- I submitted an issue to Discount to see if this could be implemented: https://github.com/Orc/discount/issues/203 -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #4 from avlas --- (In reply to Laurent Montel from comment #3) > When I started to implement this feature, I looked at first markdown-here. > But it was very hard to use js in kmail directly... I see. Thanks for the info. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406332] Markdown addon option 'Enable embedded LaTeX' does not work
https://bugs.kde.org/show_bug.cgi?id=406332 --- Comment #1 from avlas --- If I'm not wrong 'Enable embedded LaTeX' option from Discount lib (libmarkdown2) is just to avoid converting LaTeX content to html as if it was markdown content, and instead leaving it as raw text. If correct, I wonder whether there is any option to render LaTeX equations in Kmail and/or convert them to PNG (or SVG) images embedded in html. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #2 from avlas --- Thanks a lot for working on the Markdown plugin. It's very nice and useful! > Yep indeed but "Discount" lib seems that it doesn't support style :( (In reply to Laurent Montel from comment #1) I see. I wonder how difficult would be to build upon markdown-here instead. I guess very difficult... -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406334] New: Markdown addon: embedded images (attached to the email) are not displayed
https://bugs.kde.org/show_bug.cgi?id=406334 Bug ID: 406334 Summary: Markdown addon: embedded images (attached to the email) are not displayed Product: kdepim Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messagecomposer Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- The following example: Some text in markdown format  Some more text in markdown format should ideally display "image.png" embedded within the text (if attached in the email, of course). -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406333] New: Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 Bug ID: 406333 Summary: Markdown addon: support syntax highlighting Product: kdepim Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: messagecomposer Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- An example from https://markdown-here.com : ```javascript // All the code you will ever need var hw = "Hello World!" alert(hw); ``` -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 406332] New: Markdown addon option 'Enable embedded LaTeX' does not work
https://bugs.kde.org/show_bug.cgi?id=406332 Bug ID: 406332 Summary: Markdown addon option 'Enable embedded LaTeX' does not work Product: kdepim Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messagecomposer Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- LaTeX is installed and working fine in my system. Perhaps there is a (not so obvious) dependency (that I am not aware of) for getting this working in Kmail with the Markdown addon (which works fine in my system). Any help on this is more than appreciated! -- 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 #52 from avlas --- (In reply to Sudhir Khanger from comment #51) > Created attachment 117651 [details] > html white bar > > Even if you set the colors to either white or grayish you will end up with > same bad UI behavior. > > @avlas Where do I put ColorbarBackground code? Under some heading like > [Reader] or just at the bottom. > > [Reader] > CloseToQuotaColor=218,68,83 > ColorbarBackgroundHTML=255,255,255 > ColorbarBackgroundPlain=255,255,255 > ColorbarForegroundHTML=255,255,255 > ColorbarForegroundPlain=255,255,255 > LinkColor=41,128,185 > QuotedText1=32,145,80 > QuotedText2=26,116,64 > QuotedText3=19,87,48 > ScamDetectionEnabled=false > attachment-strategy=inlined > defaultColors=false > header-plugin-style-name=brief > htmlLoadExternal=true > htmlMail=true > showColorBar=false Under [Reader] -- 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 #50 from avlas --- (In reply to Sudhir Khanger from comment #49) > @avlas thanks for that info. By any chance do you have the code that is > relevant for removing this egregious UI. Sorry, perhaps I was not clear enough. These config sections are not for disabling the html status bar, but for changing its appearance. These are my settings in the Reader section of kontactrc and kmail2rc: ColorbarBackgroundHTML=250,251,252 ColorbarBackgroundPlain=250,251,252 ColorbarForegroundHTML=0,116,185 ColorbarForegroundPlain=250,251,252 I configured it so that the background of the html status bar always matches the window background color (according to the color scheme you use), and for the text color, I set it to blue when HTML is active, and virtually invisible otherwise (by matching the color of the background in plain text emails). -- 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 #48 from avlas --- (In reply to avlas from comment #47) > (In reply to Cristian Adam from comment #5) > > I have found a partial workaround – namely changing the background color of > > the HTML Status Bar. > > > > This can be done in Settings -> Configure KMail -> Appearance -> Colors. I > > have used "#fcfcfc" for all four "HTML Status Bar" entries. > > > > Not the status bar is still eating valuable screen width, but at least is > > not an eye sore anymore. > > This workaround only works for Kmail launched as a single application. It > has not effect if Kmail is embedded in Kontact. > > Not that I wanted to remove it completely but I wanted a more integrated > background in white with nice text in soft blue (breeze like). But no way to > do this :( There is actually a way to do this, but it's far from obvious, as one needs to apply this in kmail settings and then copy that section to kontact settings manually... No need to say that this should be applied directly withouth having to: 1. Open kmail as a standalone application 2. Change the settings 3. Open kmailrc and copy the relevant section 4. Edit kontactrc by pasting that settings section -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 401739] Kmail crashes while open on fresh start system, attempting to reopen it results in the completely empty application window, no mailbox or mail message available
https://bugs.kde.org/show_bug.cgi?id=401739 --- Comment #6 from avlas --- If bug 402253 is truly a duplicate of this, the affected users can benefit of the workaround I found. See https://bugs.kde.org/show_bug.cgi?id=402253#c14 and https://bugs.kde.org/show_bug.cgi?id=402253#c16 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #16 from avlas --- I figured out that the Kontact/Kmail crash happens only if I enable "Share text" in "Editor connectors" of the Kmail settings (sorry if this doesn't fully correspond to the English labels, I have my system in a different language). After disabling that connector, Kontact is again fully functional. Hope this helps affected users, as well as developers to reproduce and fix the issue. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #15 from avlas --- (In reply to avlas from comment #14) > FYI, I found a way to start kmail normally after removing the autosave > folder in ~/.local/share/kmail2 This doesn't mean kmail works normally. I cannot write/reply or forward any e-mail, without restarting the loop, i.e. kontact/kmail crashing and repeating that behavior until I remove the autosave folder (or its contents) again... so I guess the bug is triggered right before or at the compose window startup (note that I never reach to see the compose window, kontact crashes before). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #14 from avlas --- FYI, I found a way to start kmail normally after removing the autosave folder in ~/.local/share/kmail2 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #12 from avlas --- I hope the valgrind report is helpful. If there is anything that can be improved or you would like me to test other things, please don't hesitate to ask. To play a bit myself, yesterday I tried to build kmail from source in kde neon (user edition), but cmakelist complains about the version of installed dev packages. I guess the version in the official user repo are not sufficiently up-to-date. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #11 from avlas --- (In reply to avlas from comment #10) > > Please also check if moving kmail2's *.rc helps. The *.rc files are in > > ~/.local/share/kxmlgui5/ > > I don't have any kmail rc file there, I have for other applications but not > for kmail, which I guess means I just use default. Talked too early, I do have one for kontact as I never use kmail as a stand-alone application. Unfortunately moving kontact's rc file didn't fix the issue. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #10 from avlas --- (In reply to Christoph Feck from comment #8) > All duplicates originate from KMMainWidget::initializePluginActions() > calling into KXMLGUI, and causing a crash there in > KXMLGUIFactory::plugActionList(). I see > If you want to help, you could install debug symbols for libKF5XmlGui.so.5 > and try to get a valgrind log. For more information, please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind Done > Please also check if moving kmail2's *.rc helps. The *.rc files are in > ~/.local/share/kxmlgui5/ I don't have any kmail rc file there, I have for other applications but not for kmail, which I guess means I just use default. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #9 from avlas --- Created attachment 116996 --> https://bugs.kde.org/attachment.cgi?id=116996&action=edit valgrind report -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #7 from avlas --- ... that could help me to *avoid getting* stacked... -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #6 from avlas --- I recall now that it crashed when trying to reply to an email, and each time I try to start kmail/kontact it tries to open the composer and crashes again (see the kmail backtrace below, which I hope is more informative than the kontact one, I submitted before). Is there a way to avoid opening the composer at startup, like removing some cache or something? that could help me to get stacked with it for now, until a proper fix is find. Help on this is highly appreciated! Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6aa1cccbc0 (LWP 19922))] Thread 6 (Thread 0x7f6a5ca31700 (LWP 19927)): #0 0x7f6a9ed8fbf9 in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f6a9268b539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a9268b64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a9f6ca04b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a9f66e30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a9f499bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a9f4a4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a945576db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f6a9ed9c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f6a5d232700 (LWP 19926)): #0 0x7f6a9455f06a in pthread_getspecific () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f6a926b35f0 in g_thread_self () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a9268b63d in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a9f6ca04b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a9f66e30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a9f499bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a9f4a4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a945576db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f6a9ed9c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f6a5e0d1700 (LWP 19925)): #0 0x7f6a926d1064 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6a9268aa88 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a9268b46b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a9268b64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a9f6ca04b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a9f66e30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a9f499bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a9f4a4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a945576db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f6a9ed9c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f6a5f2e2700 (LWP 19924)): #0 0x7f6a926d1064 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6a9268ad39 in g_main_context_query () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a9268b4b7 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a9268b64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a9f6ca04b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a9f66e30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a9f499bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a9da7fe45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f6a9f4a4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f6a945576db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f6a9ed9c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f6a6903c700 (LWP 19923)): #0 0x7f6a9ed8fbf9 in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f6a91ab5747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f6a91ab736a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f6a6ad40ed9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f6a9f4a4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a945576db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f6a9ed9c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #5 from avlas --- (In reply to avlas from comment #4) > Excuse my ignorance but I wonder how can they be duplicates if they > originate at different source code locations? Or am I looking at it wrong? > > this bug: > > #25 0x7f761b9d2a3d in > KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () > at /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 > #26 0x55dd3b40f421 in main(int, char**) (argc=, > argv=) at ./src/main.cpp:212 > > bug 401201: > > #38 0x563afc8a133b in main (argc=, argv=) > at /usr/include/qt5/QtCore/qcoreapplication.h:116 > [Inferior 1 (process 4173) detached] > > Unfortunately other bugs do not seem as informative Oops, sorry, I meant in comparison to bug 401739 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #4 from avlas --- Excuse my ignorance but I wonder how can they be duplicates if they originate at different source code locations? Or am I looking at it wrong? this bug: #25 0x7f761b9d2a3d in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () at /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #26 0x55dd3b40f421 in main(int, char**) (argc=, argv=) at ./src/main.cpp:212 bug 401201: #38 0x563afc8a133b in main (argc=, argv=) at /usr/include/qt5/QtCore/qcoreapplication.h:116 [Inferior 1 (process 4173) detached] Unfortunately other bugs do not seem as informative -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #3 from avlas --- FYI: Internally it may be similar (or even the same) to other bugs, but the crash I talk about is not at exit (bug 402129), neither I can open kontact/kmail at all to see an empty window thereafter (bug 401739). Can you please share if someone is trying to fix this issue(-s) at the moment? Or if is there anything I can test to speed up a fix? I don't want to be pushy but I use kontact/kmail in production and not being able to even open the application makes me pretty anxious. I hope you understand. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 --- Comment #1 from avlas --- Not sure if related to any of these two thing: - I deleted two identities from the 4 I had - Kmail got updated in neon recently (25 iteration), but downgrading to 24 iteration did not fix it -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 402253] New: Kmail/Kontact crash
https://bugs.kde.org/show_bug.cgi?id=402253 Bug ID: 402253 Summary: Kmail/Kontact crash Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Application: kontact (5.10.0) Qt Version: 5.11.2 Frameworks Version: 5.53.0 Operating System: Linux 4.18.0-13-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: It happens at startup every single time The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f761c1b1b80 (LWP 29502))] Thread 29 (Thread 0x7f74c8c03700 (LWP 29558)): #0 0x7f7618b4fbf9 in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f7612594539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f761259464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f76196a204b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f761964630a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7619471bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f761947cadb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f76144606db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f7618b5c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 28 (Thread 0x7f74c9404700 (LWP 29557)): #0 0x7f7618b4fbf9 in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f7612594539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f761259464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f76196a204b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f761964630a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7619471bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f761947cadb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f76144606db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f7618b5c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 27 (Thread 0x7f74ca2a3700 (LWP 29554)): #0 0x7f7618b4fbf9 in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f7612594539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f761259464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f76196a204b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f761964630a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7619471bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f761947cadb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f76144606db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f7618b5c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 26 (Thread 0x7f74df7fe700 (LWP 29540)): #0 0x7f7618b6b6ac in () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f7618b6d474 in __fprintf_chk () at /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f760170b9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f760170bb44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f760170d46c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f7601703114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f7609ac7fc4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7609ae820b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7609b0a60f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7609b05ff1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f76144606db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f7618b5c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 25 (Thread 0x7f759a957700 (LWP 29538)): #0 0x7f76144669f3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7602b49954 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f7602b4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f76144606db in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f7618b5c88f in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 24 (Thread 0x7f7599c4c700 (LWP 29537)): #0 0x7f7618b4fbf9 in pol
[kmail2] [Bug 400964] New: Thread view improvement: plain subthread view
https://bugs.kde.org/show_bug.cgi?id=400964 Bug ID: 400964 Summary: Thread view improvement: plain subthread view Product: kmail2 Version: 5.9.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- SUMMARY Messages get rapidly hidden in long threads (thread view). This is not a rare case in collaborative projects and mailing lists. Navigation then becomes blind. STEPS TO REPRODUCE 1. Go to a thread of 10-100 emails 2. Navigate down the thread in the message list OBSERVED RESULT Emails rapidly become invisible because of the right shift from one email to another down in the thread EXPECTED RESULT All emails should be visible in the thread of message list. ADDITIONAL INFORMATION There are probably cool solutions to this like the one implemented by mailspring and other email clients, but I think a solution easy to implement given the current architecture would be to right shift only once, from the head message of the thread to the rest. This would allow differentiating between messages belonging to a thread from others, while strongly diminishing the blinding effect. One can say that it misses information about subthreads, but correct display of subthreads is tricky and I for one don't care much about them (frankly I think that not being able to see messages is more important than how subthreads are organized). Also, this (plain thread view) could be an additional option to display the message list (in addition to the current subthread structure). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389891] Pin messages so they appear on top
https://bugs.kde.org/show_bug.cgi?id=389891 --- Comment #4 from avlas --- > I thought mine would fullfill both, if not, feel free to reopen and explain > more in depth your use case and use scenario I like your proposal very much and it's not orthogonal of mine, but I was just suggesting to pin a message so it appears at top of a given folder, similarly to how this can be set in telegram, whatsapp, twitter, etc. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389891] Pin messages so they appear on top
https://bugs.kde.org/show_bug.cgi?id=389891 --- Comment #2 from avlas --- Not sure it's completely the same. We both use the word "pin", but the two bugs mean it differently, don't they? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"
https://bugs.kde.org/show_bug.cgi?id=399245 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #7 from avlas --- What about start improving the UI by fixing this https://bugs.kde.org/show_bug.cgi?id=393421#c47 In brief, the colors of the html bar have no effect in Kontact -- 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 #47 from avlas --- (In reply to Cristian Adam from comment #5) > I have found a partial workaround – namely changing the background color of > the HTML Status Bar. > > This can be done in Settings -> Configure KMail -> Appearance -> Colors. I > have used "#fcfcfc" for all four "HTML Status Bar" entries. > > Not the status bar is still eating valuable screen width, but at least is > not an eye sore anymore. This workaround only works for Kmail launched as a single application. It has not effect if Kmail is embedded in Kontact. Not that I wanted to remove it completely but I wanted a more integrated background in white with nice text in soft blue (breeze like). But no way to do this :( -- 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 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #39 from avlas --- Yes, it doesn't make any sense (this is just my opinion -- a user that agrees on 99.9% of KDE dev decisions, but not this one). This reminds me plasma cashew, btw... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388167] reply, reply to all and forward templates should be consistent with account dictionary
https://bugs.kde.org/show_bug.cgi?id=388167 --- Comment #1 from avlas --- I was about to report this (again). Fortunately I realized I did already. I am more explicit about it below. I hope it receives a bit more attention this time... SUMMARY Let's consider two email accounts that use different languages (e.g. personal -> non-English, and work -> English). Then, Kmail should use this information so when there is a reply or forward email, automatic text is written in the proper associated language. Currently the associated language with the account is not used. Instead, only the language associated with the Default email account (or Kmail language, not sure given they are the same in my system) seems to be used. STEPS TO REPRODUCE 1. Create 2 different email accounts, each using a different language 2. Reply/Forward to an email in both 3. Look at the self-formated text OBSERVED RESULT Both appear in the same language when they shouldn't EXPECTED RESULT Each self-formatted text should appear in the language specified in settings SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50 Qt Version: 5.11.1 ADDITIONAL INFORMATION This is different from Bug https://bugs.kde.org/show_bug.cgi?id=353134 (which is long fixed in my system). I mentioned this issue in that context but got no attention. I thought that this deserves to be a bug on its own. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397629] Multiple error messages (typically hundreds) after akonadi manual start: could not delete calendar event (no items found)
https://bugs.kde.org/show_bug.cgi?id=397629 --- Comment #4 from avlas --- > What's special about your configuration? Is that something I might be able > to set up locally to try to reproduce the issue? I'm not sure there is anything special. I have the following calendars: - a local/personal calendar w/ change control - dates and birthdates calendar - invitations calendar - my google calendar - a third google calendar (configured as an ics) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397629] Multiple error messages (typically hundreds) after akonadi manual start: could not delete calendar event (no items found)
https://bugs.kde.org/show_bug.cgi?id=397629 --- Comment #3 from avlas --- (In reply to Daniel Vrátil from comment #1) > Can you please provide a screenshot of the error message? I would be > surprised if the dialog came from the actual resource, so I wonder if that's > maybe KOrgac showing this. Sure, please see attached a screenshot. This time I got 28 error messages, which is not much, sometimes they are more than a hundred. Also, I sometimes get korganizer errors in addition to kontact, as indicated by the title of the pop-up error. This screenshot I took with my phone as my computer typically becomes irresponsive (kwin uses all CPU power) until I kill kontact (but then the errors disappear). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397629] Multiple error messages (typically hundreds) after akonadi manual start: could not delete calendar event (no items found)
https://bugs.kde.org/show_bug.cgi?id=397629 --- Comment #2 from avlas --- Created attachment 114601 --> https://bugs.kde.org/attachment.cgi?id=114601&action=edit Error pop-up message -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397629] New: Multiple error messages (typically hundreds) after akonadi manual start: could not delete calendar event (no items found)
https://bugs.kde.org/show_bug.cgi?id=397629 Bug ID: 397629 Summary: Multiple error messages (typically hundreds) after akonadi manual start: could not delete calendar event (no items found) Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ICal file resource Assignee: kdepim-bugs@kde.org Reporter: jsar...@gmail.com Target Milestone: --- While these hundreds of pop-ups emerge, the system is irresponsive and afterwards, they have to be closed one-by-one to continue working normally. This is quite annoying as you can imagine (fortunately I don't have to manually start akonadi many times). I guess the issue depends on my own calendars and configuration, so not much people is affected (otherwise I assume it would have been already fixed). I'm willing to report more info and help testing if properly directed. In the meantime I'll try to silence these pop-up error messages. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387618] words less than 3 letters are ignored
https://bugs.kde.org/show_bug.cgi?id=387618 --- Comment #7 from avlas --- dolphin's filter works for any number of letters, I don't see why this has to be any different in kmail either -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376565] Automatic spell checking is not working
https://bugs.kde.org/show_bug.cgi?id=376565 --- Comment #11 from avlas --- https://bugs.kde.org/show_bug.cgi?id=376565 --- Comment #10 from Bogdan Mihaila --- (In reply to Laurent Montel from comment #7) > you report as it's not a specific kmail bug > => please reassign to Qt or kf5 Hi Laurent I'm having a hard time to find any of above in the product drop down list of Bugzilla. Guess those just do not exist. I could reassign to frameworks-ktextedit but not sure if that is any better? Would not want to cause noise elsewhere if this might actually be fixed in Qt upstream. Suggestions? I think there is frameworks-kpart... -- You are receiving this mail because: You are the assignee for the bug.
