[kdepim] [Bug 317177] HTML emails CSS should not be applied to the header in th UI
https://bugs.kde.org/show_bug.cgi?id=317177 Laurent Montel changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In|4.10.2 |5.12.2 Resolution|--- |FIXED Latest Commit|http://commits.kde.org/kdep |https://commits.kde.org/kde |im/7776b35a0dd52450dfe21de4 |pim-addons/7fc59ab359d08c82 |3b962cad4d1841ff|8e1e067c7abfae1af1409db2 --- Comment #14 from Laurent Montel --- Git commit 7fc59ab359d08c828e1e067c7abfae1af1409db2 by Laurent Montel. Committed on 30/09/2019 at 19:02. Pushed by mlaurent into branch 'Applications/19.08'. Fix Bug 317177 - HTML emails CSS should not be applied to the header in th UI FIXED-IN: 5.12.2 M +1-0 plugins/messageviewerheaderplugins/fancyheaderstyleplugin/fancyheaderstyleplugin.cpp https://commits.kde.org/kdepim-addons/7fc59ab359d08c828e1e067c7abfae1af1409db2 -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 317177] HTML emails CSS should not be applied to the header in th UI
https://bugs.kde.org/show_bug.cgi?id=317177 --- Comment #13 from Jonathan Marten --- No, just the standard "Classic" theme -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 317177] HTML emails CSS should not be applied to the header in th UI
https://bugs.kde.org/show_bug.cgi?id=317177 --- Comment #12 from Laurent Montel --- fancy theme ? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412474] KMail should set first account 'inbox' to open by default
https://bugs.kde.org/show_bug.cgi?id=412474 --- Comment #4 from James Th --- Hi, That makes perfect sense to me! :) Thanks for your help! James On Mon, Sep 30, 2019 at 6:00 PM +0100, "Jonathan Marten" wrote: https://bugs.kde.org/show_bug.cgi?id=412474 Jonathan Marten changed: What|Removed |Added Summary|kmail should by default |KMail should set first |open 'inbox', rather than |account 'inbox' to open by |mailbox |default Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WORKSFORME |--- --- Comment #3 from Jonathan Marten --- It should be. The default setting for the check box is on, but for the folder is -1 which means none assigned. Since a folder cannot be assigned until an account has been created, maybe this should be done after a new account creation: if no default folder has yet been assigned, set it to the inbox of the newly created account. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412465] KMail crashes when Network connection is spotty
https://bugs.kde.org/show_bug.cgi?id=412465 Jonathan Marten changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Jonathan Marten --- Please test with a recent KMail version. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412474] KMail should set first account 'inbox' to open by default
https://bugs.kde.org/show_bug.cgi?id=412474 Jonathan Marten changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412474] KMail should set first account 'inbox' to open by default
https://bugs.kde.org/show_bug.cgi?id=412474 Jonathan Marten changed: What|Removed |Added Summary|kmail should by default |KMail should set first |open 'inbox', rather than |account 'inbox' to open by |mailbox |default Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WORKSFORME |--- --- Comment #3 from Jonathan Marten --- It should be. The default setting for the check box is on, but for the folder is -1 which means none assigned. Since a folder cannot be assigned until an account has been created, maybe this should be done after a new account creation: if no default folder has yet been assigned, set it to the inbox of the newly created account. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 317177] HTML emails CSS should not be applied to the header in th UI
https://bugs.kde.org/show_bug.cgi?id=317177 --- Comment #11 from Jonathan Marten --- Created attachment 122955 --> https://bugs.kde.org/attachment.cgi?id=122955=edit Screen shot of previous attachment in HMTL view -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 317177] HTML emails CSS should not be applied to the header in th UI
https://bugs.kde.org/show_bug.cgi?id=317177
Jonathan Marten changed:
What|Removed |Added
CC||j...@keelhaul.me.uk
--- Comment #10 from Jonathan Marten ---
Created attachment 122954
--> https://bugs.kde.org/attachment.cgi?id=122954=edit
Email with CSS affecting header
Sanitised, with no personal information and safe to open. The CSS that causes
the problem is the "table { table-layout: fixed; }".
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 412485] New: "Akonadi server not operational" and KMail crashes
https://bugs.kde.org/show_bug.cgi?id=412485 Bug ID: 412485 Summary: "Akonadi server not operational" and KMail crashes Product: kontact Version: 5.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m.orl...@gmail.com Target Milestone: --- Application: kontact (5.12.1) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - Unusual behavior I noticed: Suddenly Akonadi stopped working: when I open KMail it says that "Akonadi server not operational"; if I change section in Kontact (for example from Mail to Calendar) the app crashes, and I assume that the two facts are linked somehow, 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 0x7f005423fbc0 (LWP 11702))] Thread 31 (Thread 0x7efee7fff700 (LWP 14020)): #0 0x7f0050b5f0b4 in __GI___libc_read (fd=103, buf=0x7efee7ffe7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f004a5e02d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f004a59b0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f004a59b570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f004a59b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f00516bedcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f005166003a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f00514874ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0051488c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f004c4686db in start_thread (arg=0x7efee7fff700) at pthread_create.c:463 #10 0x7f0050b7088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7efeef2fe700 (LWP 13602)): #0 0x7f0050b63bf9 in __GI___poll (fds=0x5582d371a3e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f004a59b5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f004a59b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f00516bedcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f005166003a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f00514874ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0051488c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f004c4686db in start_thread (arg=0x7efeef2fe700) at pthread_create.c:463 #8 0x7f0050b7088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7eff0d6b0700 (LWP 13587)): #0 0x7f004c46eed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7eff0d6af710, expected=0, futex_word=0x7eff0d6af8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f004c46eed9 in __pthread_cond_wait_common (abstime=0x7eff0d6af7b0, mutex=0x7eff0d6af8a8, cond=0x7eff0d6af8d0) at pthread_cond_wait.c:533 #2 0x7f004c46eed9 in __pthread_cond_timedwait (cond=0x7eff0d6af8d0, mutex=0x7eff0d6af8a8, abstime=0x7eff0d6af7b0) at pthread_cond_wait.c:667 #3 0x7f0041c57b17 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0041c5846a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0041c58552 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0041c18fb1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0041c1b4c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0041c1bab4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0041c5a561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f004c4686db in start_thread (arg=0x7eff0d6b0700) at pthread_create.c:463 #11 0x7f0050b7088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7eff0fba2700 (LWP 13574)): #0 0x7f0050b5f0b4 in __GI___libc_read (fd=81, buf=0x7eff0fba17d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f004a5e02d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f004a59b0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f004a59b570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f004a59b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f00516bedcb in
[kmail2] [Bug 412122] Crash when closing the composer
https://bugs.kde.org/show_bug.cgi?id=412122 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||5.12.2 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kma ||il/6198b6426615a58f8a667010 ||baf5de43669a1fda --- Comment #1 from Laurent Montel --- Git commit 6198b6426615a58f8a667010baf5de43669a1fda by Laurent Montel. Committed on 30/09/2019 at 11:27. Pushed by mlaurent into branch 'Applications/19.08'. Fix Bug 412122 - Crash when closing the composer I can't reproduce it, but I disconnect signal when we detroy composer. I hope that it will fix this crash FIXED-IN: 5.12.2 M +2-1src/editor/kmcomposerwin.cpp M +1-0src/editor/kmcomposerwin.h https://commits.kde.org/kmail/6198b6426615a58f8a667010baf5de43669a1fda -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412474] kmail should by default open 'inbox', rather than mailbox
https://bugs.kde.org/show_bug.cgi?id=412474 --- Comment #2 from James Th --- Many thanks for this information! Would it be better do you think, if this was actually the default behaviour? James On 30/09/2019, 11:18, "Jonathan Marten" wrote: https://bugs.kde.org/show_bug.cgi?id=412474 Jonathan Marten changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO CC||j...@keelhaul.me.uk --- Comment #1 from Jonathan Marten --- The folder to select when starting KMail should be configurable: Settings - Configure KMail - Misc - Folders Turn on "Open this folder at startup" and select the required folder. Please report if this option is not present or does not appear to work. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412474] kmail should by default open 'inbox', rather than mailbox
https://bugs.kde.org/show_bug.cgi?id=412474 Jonathan Marten changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO CC||j...@keelhaul.me.uk --- Comment #1 from Jonathan Marten --- The folder to select when starting KMail should be configurable: Settings - Configure KMail - Misc - Folders Turn on "Open this folder at startup" and select the required folder. Please report if this option is not present or does not appear to work. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412474] New: kmail should by default open 'inbox', rather than mailbox
https://bugs.kde.org/show_bug.cgi?id=412474 Bug ID: 412474 Summary: kmail should by default open 'inbox', rather than mailbox Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY Currently if I open kmail, it will open and hi-light the mailbox icon and therefore it doesn't show any emails. I think that it should open the inbox folder, so that my emails are shown. I know that this is a small thing, in the grand scheme of things, but I think it would be beneficial. STEPS TO REPRODUCE 1. close Kmail if already open. 2. open kmail, and you'll notice that the default behaviour is to start with the mailbox name. OBSERVED RESULT by default kmail opens with the mailbox hi-lighted. EXPECTED RESULT by default kmail should open with the Inbox folder hi-lighted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse TW 20190925 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412465] KMail crashes when Network connection is spotty
https://bugs.kde.org/show_bug.cgi?id=412465 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #1 from Jonathan Marten --- Backtrace looks suspicously like bug #387177. Fixed in KMail 5.8, please upgrade if possible. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 412465] New: KMail crashes when Network connection is spotty
https://bugs.kde.org/show_bug.cgi?id=412465 Bug ID: 412465 Summary: KMail crashes when Network connection is spotty Product: kmail2 Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jens.pruess...@uni-konstanz.de Target Milestone: --- Application: kmail (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-64-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - I am running Kubuntu 18.04 with Plasma 5.12.9 and the latest version of KMail. Whenever my network connection is coming back online after an interruption, KMail crashes. The crash can be reproduced every time. -- Backtrace: 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 0x7fc575b44b80 (LWP 15100))] Thread 31 (Thread 0x7fc3ddbdf700 (LWP 28491)): #0 0x7fc568515ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc3ddbde7e0, expected=0, futex_word=0x7fc4fc0047d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fc568515ed9 in __pthread_cond_wait_common (abstime=0x7fc3ddbde880, mutex=0x7fc4fc004780, cond=0x7fc4fc0047a8) at pthread_cond_wait.c:533 #2 0x7fc568515ed9 in __pthread_cond_timedwait (cond=0x7fc4fc0047a8, mutex=0x7fc4fc004780, abstime=0x7fc3ddbde880) at pthread_cond_wait.c:667 #3 0x7fc55d3e4652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc55d3ba799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc55d3bacfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc55d3b35eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc56850f6db in start_thread (arg=0x7fc3ddbdf700) at pthread_create.c:463 #8 0x7fc572c1f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fc3eed4a700 (LWP 28288)): #0 0x7fc568515ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc3eed497e0, expected=0, futex_word=0x7fc4fc0047d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fc568515ed9 in __pthread_cond_wait_common (abstime=0x7fc3eed49880, mutex=0x7fc4fc004780, cond=0x7fc4fc0047a8) at pthread_cond_wait.c:533 #2 0x7fc568515ed9 in __pthread_cond_timedwait (cond=0x7fc4fc0047a8, mutex=0x7fc4fc004780, abstime=0x7fc3eed49880) at pthread_cond_wait.c:667 #3 0x7fc55d3e4652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc55d3ba799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc55d3bacfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc55d3b35eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc56850f6db in start_thread (arg=0x7fc3eed4a700) at pthread_create.c:463 #8 0x7fc572c1f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fc411301700 (LWP 15461)): #0 0x7fc5685159f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5640878feb8c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc5685159f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5640878feb38, cond=0x5640878feb60) at pthread_cond_wait.c:502 #2 0x7fc5685159f3 in __pthread_cond_wait (cond=0x5640878feb60, mutex=0x5640878feb38) at pthread_cond_wait.c:655 #3 0x7fc55d3b5c95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc55d3b6177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc55d3b6f11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc55d3b35eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc56850f6db in start_thread (arg=0x7fc411301700) at pthread_create.c:463 #8 0x7fc572c1f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fc41250f700 (LWP 15235)): #0 0x7fc572c0e0b4 in __GI___libc_read (fd=89, buf=0x7fc41250e810, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc5668fe2d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc5668b90b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc5668b9570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc5668b96dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc57355b99b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc5735009fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc57331f23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc57332417d in () at
[kdeplasma-addons] [Bug 412433] "Note Desktop Sticky Notes" is not movable after Desktop Widget Locked
https://bugs.kde.org/show_bug.cgi?id=412433 Wolfgang Bauer changed: What|Removed |Added Product|knotes |kdeplasma-addons Assignee|kdepim-bugs@kde.org |plasma-b...@kde.org Component|general |notes CC||wba...@tmo.at --- Comment #3 from Wolfgang Bauer --- That has nothing to do with knotes though. You are obviously talking about Plasma's notes widget that's part of kdeplasma-addons. knotes' notes are actual windows, and it should be possible to move them like any other window, regardless whether desktop widgets are locked or not. -- You are receiving this mail because: You are the assignee for the bug.
