[kmail2] [Bug 360012] Quote expand/collapse icons are misaligned
https://bugs.kde.org/show_bug.cgi?id=360012 --- Comment #2 from Alexander Potashev --- KDEPIM 15.12.2. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 360012] Quote expand/collapse icons are misaligned
https://bugs.kde.org/show_bug.cgi?id=360012 --- Comment #1 from Alexander Potashev --- Created attachment 97644 --> https://bugs.kde.org/attachment.cgi?id=97644&action=edit screenshot -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 360012] New: Quote expand/collapse icons are misaligned
https://bugs.kde.org/show_bug.cgi?id=360012 Bug ID: 360012 Summary: Quote expand/collapse icons are misaligned Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: aspotas...@gmail.com The quote expand/collapse icons are partly beyond the left edge of message viewer. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 360000] KMail grabs default PCM device on notification
https://bugs.kde.org/show_bug.cgi?id=36 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kdepim] [Bug 232832] Collapsing / Expanding quotes misbehaves with multiple quote marks
https://bugs.kde.org/show_bug.cgi?id=232832 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.
https://bugs.kde.org/show_bug.cgi?id=359964 --- Comment #4 from Laurent Montel --- (In reply to eemantsal from comment #2) > Yes, but where should I look at to see what has been sent? I think the logic > thing is to believe that sent mail folder contains sent mail, exactly what > Kmail sents, nothing more and nothing less. Why should a program do > something different to what its name says? > Anyway I, of course don't deny what you say, but then, how can we know what > has really been sent? We keep it in sent-mail folder as when we want to reply/reedit we need to know why identity was used for example etc. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 360000] New: KMail grabs default PCM device on notification
https://bugs.kde.org/show_bug.cgi?id=36 Bug ID: 36 Summary: KMail grabs default PCM device on notification Product: kmail2 Version: 5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: patrick.auer...@gmail.com The soundcard of my PC stopped working after a while, so I started monitoring the usage of PCM devices in my system. What I found is that KMail grabs the default PCM device of the system when a notification dialog pops up (in my case it was the sieve script upload confirmation dialog). If the device is already in use (by pulseaudio), audio keeps working as it should. It seems that some notifications bypass pulseaudio and use ALSA directly, but do not release the device afterwards. Closing the application releases the device again, but its really annoying. Reproducible: Always Steps to Reproduce: 1. Open the sieve script editor 2. Klick OK to close the editor 3. Default PCM device gets used by KMail Actual Results: No audio over default soundcard Expected Results: Sound keeps working Arch Linux package version: 15.12.2-1 Kernel: 4.4.1-2-ARCH x86_64 output of fuser -av USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: valethF...m kmail -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.
https://bugs.kde.org/show_bug.cgi?id=359964 --- Comment #3 from eemantsal --- Silly form... I can't edit my message, so I have to write this reply and spam your mailbox inncessarily >:-( Ok, 3 seconds after sending my previus message I realized that I just have to send an email to myself and look at the headers. So, then, if Kmail wouldn't send the user agent nor the Message-ID it will be as privacy friendly as the privacy friendly webmail apps. Great. But, where can be disabled or customize Message-ID? I've been looking in identities' and accounts' preferences but haven't found it. Also, don't you think that if it can be disabled or customized with a generic name like "localhost", "PC", or whatever generic name is used by the majority, it should be the default? Shouldn't privacy be preserved just out of the box, not tell users to change something that besides is not very visible? Anyway, is more tranquilizing to see that only user agent and Message-ID are sent. Thanks for indicating, if not, I'd been convinced that Kmail sends many other personal info, like I think everyone who may read my post at KDE forum must be thinking. :-/ I'll write a comment to tranquilize the readers. Thanks, and I hope it's improved as soon as possible. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.
https://bugs.kde.org/show_bug.cgi?id=359964 --- Comment #2 from eemantsal --- Yes, but where should I look at to see what has been sent? I think the logic thing is to believe that sent mail folder contains sent mail, exactly what Kmail sents, nothing more and nothing less. Why should a program do something different to what its name says? Anyway I, of course don't deny what you say, but then, how can we know what has really been sent? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 359990] New: IMAP Hostname change clears disconnected cache
https://bugs.kde.org/show_bug.cgi?id=359990 Bug ID: 359990 Summary: IMAP Hostname change clears disconnected cache Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: aheine...@intevation.de CC: kdepim-bugs@kde.org, vkra...@kde.org I'm currently having to resync several gigabytes of mail because the hostname of my imap server changed. This was surprising and had I known this I would have just changed the DNS entry for the server. Isn't there a better way to figure out this is a new server? Or can the user be asked "Should this be treated as a different account?" I'm not sure what would happen though if it's really a different account and the user says no to that question. Probably nothing good ;-) I think the trigger for this (or the place for a warning) would be in ImapResouce::onConfigurationDone but I might misreading the code. Reproducible: Always Steps to Reproduce: 1. Change hostname of server in imap account 2. Apply settings Expected Results: At the very least a warning. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 359988] New: KMail crashed after accepting certificate in dialog windows (IMAP server)
https://bugs.kde.org/show_bug.cgi?id=359988 Bug ID: 359988 Summary: KMail crashed after accepting certificate in dialog windows (IMAP server) Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: vlastimil.k...@seznam.cz CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.17 Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I select "accept certificate" in dialog window that appers while KMail trys to acces IMAP server. Then the KMail (Kontact) crash. (It was this case after wake-up from S3 sleep mode - but it crash also if not this case.) The crash can be reproduced every time. -- Backtrace: Application: FEKT of type E-mailový IMAP server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4324297c0 (LWP 31242))] Thread 2 (Thread 0x7fa41fafe700 (LWP 31244)): #0 0x7fa42dd0bbbd in poll () from /lib64/libc.so.6 #1 0x7fa42d334e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa42d334f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa431f16fde in QEventDispatcherGlib::processEvents (this=0x7fa4180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7fa431ee8d4f in QEventLoop::processEvents (this=this@entry=0x7fa41fafde20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fa431ee9045 in QEventLoop::exec (this=this@entry=0x7fa41fafde20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fa431de64df in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7fa431de8bbf in QThreadPrivate::start (arg=0x1eda600) at thread/qthread_unix.cpp:349 #8 0x7fa42da1a0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fa42dd13fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fa4324297c0 (LWP 31242)): [KCrash Handler] #6 QMetaObject::invokeMethod (obj=0x6, member=member@entry=0x7fa430c800ee "doSslErrorHandlerResponse", type=type@entry=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166 #7 0x7fa430c5df18 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=0x7fa430c800ee "doSslErrorHandlerResponse", obj=) at /usr/include/QtCore/qobjectdefs.h:434 #8 KIMAP::SessionThread::sslErrorHandlerResponse (this=, response=true) at /usr/src/debug/kdepimlibs-4.14.10/kimap/sessionthread.cpp:274 #9 0x7fa431f0249e in QObject::event (this=0x1f134a0, e=) at kernel/qobject.cpp:1231 #10 0x7fa43128479c in QApplicationPrivate::notify_helper (this=this@entry=0x1ca2df0, receiver=receiver@entry=0x1f134a0, e=e@entry=0x7fa40c00d5c0) at kernel/qapplication.cpp:4565 #11 0x7fa43128acdd in QApplication::notify (this=0x7ffc1eb4b2d0, receiver=0x1f134a0, e=0x7fa40c00d5c0) at kernel/qapplication.cpp:4351 #12 0x7fa42f165e1a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #13 0x7fa431eea18d in QCoreApplication::notifyInternal (this=0x7ffc1eb4b2d0, receiver=receiver@entry=0x1f134a0, event=event@entry=0x7fa40c00d5c0) at kernel/qcoreapplication.cpp:953 #14 0x7fa431eed45d in sendEvent (event=0x7fa40c00d5c0, receiver=0x1f134a0) at kernel/qcoreapplication.h:231 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1c711a0) at kernel/qcoreapplication.cpp:1577 #16 0x7fa431eed903 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #17 0x7fa431f177fe in sendPostedEvents () at kernel/qcoreapplication.h:236 #18 postEventSourceDispatch (s=0x1ca82f0) at kernel/qeventdispatcher_glib.cpp:300 #19 0x7fa42d334c84 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #20 0x7fa42d334ed8 in ?? () from /usr/lib64/libglib-2.0.so.0 #21 0x7fa42d334f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #22 0x7fa431f16fbe in QEventDispatcherGlib::processEvents (this=0x1c769c0, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #23 0x7fa4313216a6 in QGuiEventDispatcherGlib::processEvents (this=, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #24 0x7fa431ee8d4f in QEventLoop::processEvents (this=this@entry=0x7ffc1eb4b240, flags=...) at kernel/qeventloop.cpp:149 #25 0x7fa431ee9045 in QEventLoop::exec (this=this@entry=0x7ffc1eb4b240, flags=...) at kernel
[kontact] [Bug 353482] Akonadi will not load in PMI files.
https://bugs.kde.org/show_bug.cgi?id=353482 --- Comment #14 from saufenkau...@web.de --- Created attachment 97636 --> https://bugs.kde.org/attachment.cgi?id=97636&action=edit New crash information added by DrKonqi korganizer () using Qt 5.4.2 - What I was doing when the application crashed: Everytime I try to add a new event in kOrganizer, it crashes. The same happens, when I try to open preferences in kOrganizer, Kmail, or aKregator -- Backtrace (Reduced): #7 0xb4b6e29a in Akonadi::Tag::operator= (this=0xbfe1b294, other=...) at ../../../../akonadi/src/core/tag.cpp:80 #8 0xb4b6e3ff in Akonadi::Tag::Tag (this=0xbfe1b294, other=...) at ../../../../akonadi/src/core/tag.cpp:72 #9 0xb4c0d537 in Akonadi::TagModelPrivate::tagForIndex (this=0xa400b18, index=...) at ../../../../akonadi/src/core/models/tagmodel_p.cpp:105 #10 0xb4c0c32c in Akonadi::TagModel::data (this=0xa3fa5d0, index=..., role=262) at ../../../../akonadi/src/core/models/tagmodel.cpp:91 #11 0xb4d12a49 in Akonadi::TagWidget::updateView (this=0xa3fec08) at ../../../../akonadi/src/widgets/tagwidget.cpp:102 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
