[kontact] [Bug 403604] New: kmail does not update main message body area when showing empty email (keeps previous email body)
https://bugs.kde.org/show_bug.cgi?id=403604 Bug ID: 403604 Summary: kmail does not update main message body area when showing empty email (keeps previous email body) Product: kontact Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY kmail does not display mail (at all) when it has no content, even if attachments exist. STEPS TO REPRODUCE 1. create empty plain text mail with attachment (7z file in my case) from MS Outlook 2016 (in my case, I don't know if this matters) 2. send this to kmail account 3. view with kmail OBSERVED RESULT kmail does not display, but also does not empty, the message body area. It just keeps displaying the previously displayed message EXPECTED RESULT kmail should show an empty message body and the attachment area (or an icon for the attachment(s)). SOFTWARE/OS VERSIONS Windows: - MacOS: - Linux/KDE Plasma: KDE Neon 18.04 with all updates applied, KMail 5.10.1 (available in About System) ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 398516] UI - Akregator comments section font seems to be hard coded. Font is tiny on a 4k monitor
https://bugs.kde.org/show_bug.cgi?id=398516 --- Comment #4 from walter --- I attatched a screenshot of Kontact with Akregator open, and the font selection setup. Note the comments under "Read more of this story" font is perhaps half the size of my font selection, and I can't change it. On Fri, Jan 18, 2019 at 8:33 PM Bug Janitor Service < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=398516 > > --- Comment #3 from Bug Janitor Service --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402813] Akonadi 5.10.0 throws a Qt error
https://bugs.kde.org/show_bug.cgi?id=402813 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 401692 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 401692] Akonadi components crash on logout
https://bugs.kde.org/show_bug.cgi?id=401692 Christoph Feck changed: What|Removed |Added CC||pe...@prh.myzen.co.uk --- Comment #16 from Christoph Feck --- *** Bug 402813 has been marked as a duplicate of this bug. *** -- 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 #51 from Sudhir Khanger --- Created attachment 117651 --> https://bugs.kde.org/attachment.cgi?id=117651=edit 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 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 403317] KMAIL2; "Share Text" plugin segfaults
https://bugs.kde.org/show_bug.cgi?id=403317 Wolfgang Bauer changed: What|Removed |Added CC||boscono...@gmail.com --- Comment #3 from Wolfgang Bauer --- *** Bug 403581 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 403581] kmail crashes when creating a new email
https://bugs.kde.org/show_bug.cgi?id=403581 Wolfgang Bauer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Wolfgang Bauer --- *** This bug has been marked as a duplicate of bug 403317 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 403581] kmail crashes when creating a new email
https://bugs.kde.org/show_bug.cgi?id=403581 --- Comment #2 from Francescodario Cuzzocrea --- Yes. I resetted akonadi and kmail, didn't enabled that plugin and now it works !! In data venerdì 25 gennaio 2019 10:41:56 CET, hai scritto: > https://bugs.kde.org/show_bug.cgi?id=403581 > > Wolfgang Bauer changed: > >What|Removed |Added > > CC||wba...@tmo.at > > --- Comment #1 from Wolfgang Bauer --- > Looks similar to bug#403566 and bug#403317. > > Does it help to disable the "Share Text" plugin? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 403581] kmail crashes when creating a new email
https://bugs.kde.org/show_bug.cgi?id=403581 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #1 from Wolfgang Bauer --- Looks similar to bug#403566 and bug#403317. Does it help to disable the "Share Text" plugin? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 403581] New: kmail crashes when creating a new email
https://bugs.kde.org/show_bug.cgi?id=403581 Bug ID: 403581 Summary: kmail crashes when creating a new email Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: boscono...@gmail.com Target Milestone: --- Application: kmail (5.10.1) Qt Version: 5.9.4 Frameworks Version: 5.54.0 Operating System: Linux 4.12.14-lp150.12.45-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: I clicked on file -> new email, the program crashes - Unusual behavior I noticed: The fact that kmail crash - Custom settings of the application: I have 3 identities configured, each one with it's own outgoing smtp account I'm using KDE Plasma 5.12.7, KDE Frameworks 5.54, Qt 5.9.4 and KDE Applications 18.12 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f03798e6980 (LWP 4188))] Thread 6 (Thread 0x7f032700 (LWP 4193)): #0 0x7f037699f07b in poll () from /lib64/libc.so.6 #1 0x7f036a47b1c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f036a47b2dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f03772cec0b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f037727709a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f03770a64da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f03770ab0ce in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f036c348559 in start_thread () from /lib64/libpthread.so.0 #8 0x7f03769a981f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f033cbda700 (LWP 4192)): #0 0x7f036a4c0dc9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f036a47a070 in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #2 0x7f036a47b085 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f036a47b2dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f03772cec0b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f037727709a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f03770a64da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f03770ab0ce in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f036c348559 in start_thread () from /lib64/libpthread.so.0 #9 0x7f03769a981f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f033da77700 (LWP 4191)): #0 0x7f036a4c0dc9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f036a47b0d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f036a47b2dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f03772cec0b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f037727709a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f03770a64da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f03770ab0ce in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f036c348559 in start_thread () from /lib64/libpthread.so.0 #8 0x7f03769a981f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f033ecac700 (LWP 4190)): #0 0x7f036a4c0dc0 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f036a47a733 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f036a47b0fb in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f036a47b2dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f03772cec0b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f037727709a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f03770a64da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f03756b1985 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7f03770ab0ce in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f036c348559 in start_thread () from /lib64/libpthread.so.0 #10 0x7f03769a981f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f03482de700 (LWP 4189)): #0 0x7f037699f07b in poll () from /lib64/libc.so.6 #1 0x7f036989e387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f036989ffba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f034a5f4029 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f03770ab0ce in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f036c348559 in start_thread () from /lib64/libpthread.so.0 #6 0x7f03769a981f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f03798e6980 (LWP 4188)): [KCrash Handler] #6
