[kmail2] [Bug 322958] KMail: duplicate special folder causes endless loop Emitting defaultFoldersChanged
https://bugs.kde.org/show_bug.cgi?id=322958 Arthur Țițeică arthur.tite...@gmail.com changed: What|Removed |Added CC||arthur.tite...@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 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 Arthur Țițeică arthur.tite...@gmail.com changed: What|Removed |Added CC||arthur.tite...@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
[kmail] [Bug 205105] page margins are not used by printer
https://bugs.kde.org/show_bug.cgi?id=205105 staka...@freenet.de changed: What|Removed |Added CC||staka...@freenet.de --- Comment #5 from staka...@freenet.de --- I have the same problem here restricted to Kmail. This is KDE 4.14.2 with Kmail2 4.14.2 from the repos Opensuse KDE stable current vor opensuse 13.1 The printer is a Lexmark, color laser printer C543dn. The printerdriver is openprinting printerdriver (which is to be taken at the site of Lexmark because not included in the packages of opensuse. The problem is somehow different for KDE general printing setting and for Kmail. The kmail printing is crippled, it is not possible to set reasonable printing margins and the text is printed rasor blade close to the edge of the paper (which looks odd). The upper title of the email is cut o a half, because of the margins that are set too straigt to respect printing limits. When set by hand they are not memorized even if asked for, the next print is wrong again (may be a second bug). In the KDE pinting settings when having adjusted all according to the paper and printer, choosing poscript as language (pdf setting screw it all up) then the printing of the testpage from the KDE pinter setting page is correct in front By using double sided printing on the long edge it is cut to the left page margin (the frame is cut because too close to the margin. So: even this setting is somehow broken. Printing to PDF works, printing from Ocular works very well, printing from Libreoffice works after explicitly setting the page margins and using postcript as languae, and libreoffice (contrary to kmail) does remember the settings. Printing mail is common. I see this as a major bug toghether with the fact that one cannot print decripted messages at all (empty page) (see bug Bug 337668 - kmail fails to print encrypted messages 4.13.3 which is a regression of a bug from KDE 4.7 - 286615 (Encrypted email not decrypted in-time for printing ) marked wrongly as closed an affectig also mime encrypted pages. So in short: kmail printing is broken be it encrypted or unencrypted. -- 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 340015] Filter rules no longer matching after upgrade
https://bugs.kde.org/show_bug.cgi?id=340015 --- Comment #11 from Jean-Baptiste Mardelle j...@kdenlive.org --- This issue should be fixed by my git commit (24th of october): http://commits.kde.org/kdepim/01764b0eb3c7b7407f3119ef711d5b07d7b9a313 -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #25 from Volker Kuhlmann list0...@paradise.net.nz --- Created attachment 89408 -- https://bugs.kde.org/attachment.cgi?id=89408action=edit Kmail pop-up migrating passwords. I have two SMTP servers now whos pw kmail won't read from the wallet. I think it still reads some from the wallet though. It's affecting GMX and Posteo - both might have turned off sslv3 recently and I think I edited the transport settings accordingly. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #26 from Laurent Montel mon...@kde.org --- Thanks for infos. I found code. I will able to investigate it. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 Laurent Montel mon...@kde.org changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- 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 339172] regression: settings for folders in search messages are completely ignored
https://bugs.kde.org/show_bug.cgi?id=339172 piedro piedro.kul...@googlemail.com changed: What|Removed |Added CC||piedro.kul...@googlemail.co ||m --- Comment #2 from piedro piedro.kul...@googlemail.com --- At the moment the search functionality doesn't include the mails from local folders though explicitely selected... -- 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
[akregator] [Bug 340586] New: Akregator crashes when closing
https://bugs.kde.org/show_bug.cgi?id=340586 Bug ID: 340586 Summary: Akregator crashes when closing Product: akregator Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: spiro...@hotmail.com Application: akregator (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.6-2-desktop x86_64 Distribution: openSUSE 20141029 (Harlequin) (x86_64) -- Information about the crash: - What I was doing when the application crashed: When I pick-up quit in Akregator right click menu in system tray, Akregator crashes -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [KCrash Handler] #5 0x7f04497ef7fe in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (this=optimized out) at ../../src/corelib/tools/qvector.h:259 #6 0x7f04497ef7fe in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0x701e20, m=optimized out, local_signal_index=optimized out, argv=0x7fff4b2fd380) at kernel/qobject.cpp:3509 #7 0x7f044a8d1af7 in Akregator::Frame::signalStatusText(Akregator::Frame*, QString const) () at /usr/lib64/libakregatorprivate.so.4 #8 0x7f044a8c87eb in Akregator::Frame::slotSetStatusText(QString const) () at /usr/lib64/libakregatorprivate.so.4 #9 0x7f0431a76e85 in Akregator::MainWidget::slotFetchingStopped() () at /usr/lib64/kde4/akregatorpart.so #10 0x7f04497ef978 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0xcc9e90, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3576 #11 0x7f044a8c8349 in Akregator::FetchQueue::slotAbort() () at /usr/lib64/libakregatorprivate.so.4 #12 0x7f044a8c83ba in Akregator::FetchQueue::~FetchQueue() () at /usr/lib64/libakregatorprivate.so.4 #13 0x7f044a8c8429 in Akregator::FetchQueue::~FetchQueue() () at /usr/lib64/libakregatorprivate.so.4 #14 0x7f044a8c73ef in Akregator::Kernel::~Kernel() () at /usr/lib64/libakregatorprivate.so.4 #15 0x7f0447e87949 in __run_exit_handlers () at /lib64/libc.so.6 #16 0x7f0447e87995 in () at /lib64/libc.so.6 #17 0x7f0447e71b4c in __libc_start_main () at /lib64/libc.so.6 #18 0x0040872b in _start () Reported using DrKonqi -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #27 from Laurent Montel mon...@kde.org --- I investigated this morning, fixed another bug (save password at the first time in mailtransportrc) but I can't reproduce migrate bug. It migrated correctly here. I don't see in source code a bug about it. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559
--- Comment #28 from Laurent Montel mon...@kde.org ---
We use it to store password in wallet:
void Transport::usrWriteConfig()
{
if ( requiresAuthentication() storePassword() d-passwordDirty ) {
const QString storePassword = d-password;
Wallet *wallet = TransportManager::self()-wallet();
if ( !wallet || wallet-writePassword( QString::number( id() ), d-password
) != 0 ) {
= the problem can be that we can't write in kwallet or kwallet is never open
by mailtransport.
To know if password is stored in kwallet open:
~/.kde/share/config/mailtransports
= search group where there is your password
go to kwalletmanager search:
(in mailtransport file we have config group as [Transport 1816781056])
= search 1816781056 (your real number not mine :) )
and you will show if it's stored in kwallet.
--
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
