[Bug 249992] Can't log in to IMAP server running dovecot 2.0.1
https://bugs.kde.org/show_bug.cgi?id=249992 --- Comment #11 from Bernhard Rosenkraenzer bero arklinux org 2011-11-07 23:22:24 --- Created an attachment (id=65371) -- (http://bugs.kde.org/attachment.cgi?id=65371) Another variant of the fix The patch works for me too - but I wonder if just switching the if() statements wouldn't be a better fix (patch attached). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 266453] New: Akonadi keeps asking about an SSL certificate it knows should be accepted
https://bugs.kde.org/show_bug.cgi?id=266453 Summary: Akonadi keeps asking about an SSL certificate it knows should be accepted Product: Akonadi Version: 1.5.0 Platform: Unlisted Binaries OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: b...@arklinux.org CC: vkra...@kde.org, kdepim-bugs@kde.org Version: 1.5.0 (using KDE 4.6.0) OS:Linux Not 100% sure if this is an Akonadi or a kio-ssl issue... I've configured kmail to use an SSL IMAP server with a bad certificate. Akonadi (correctly) showed a dialog saying The server failed the authenticity check (mail.X.ch). The certificate does not apply to the given host. The certificate is not signed by any trusted certificate authority. (Both are expected, the server was running an out-of-the-box dovecot installation including its sample imap.example.com certificate). I told Akonadi to accept it by clicking Continue, and in the dialog that followed (Would you like to accept this certificate forever without being prompted?), Forever. However, the The server failed the authenticity check (mail.X.ch). dialog keeps popping up occasionally (even when kmail isn't running). Reproducible: Always Steps to Reproduce: 1. Set up an IMAP server with a bad SSL certificate 2. Connect to it with kmail 3. Confirm you want to accept the invalid certificate forever 4. Wait Actual Results: Keeps prompting about the certificate several times a day Expected Results: Warnings about the certificate go away I know I should fix the certificate on the imap server instead ;) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 259517] Virtuoso-t/nepomuk consume much too much CPU time in KDE 4.6
https://bugs.kde.org/show_bug.cgi?id=259517 --- Comment #8 from Bernhard Rosenkraenzer bero arklinux org 2011-01-05 10:13:51 --- duplicate of bug 246678? Does killing the nepomukstorage process fix it for you as well? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 249992] Can't log in to IMAP server running dovecot 2.0.1
https://bugs.kde.org/show_bug.cgi?id=249992 Bernhard Rosenkraenzer b...@arklinux.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Bernhard Rosenkraenzer bero arklinux org 2010-12-17 11:00:23 --- I can't reproduce this anymore with 4.6.0-beta2, assuming it's fixed -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 244630] nepomuk_email_feeder: error dialog Nepomuk backend for strigi not available
https://bugs.kde.org/show_bug.cgi?id=244630 Bernhard Rosenkraenzer b...@arklinux.org changed: What|Removed |Added CC||b...@arklinux.org --- Comment #7 from Bernhard Rosenkraenzer bero arklinux org 2010-12-09 11:58:55 --- I'm running into this error with 4.6.0-beta2... Is this supposed to be fixed? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 249992] New: Can't log in to IMAP server running dovecot 2.0.1
https://bugs.kde.org/show_bug.cgi?id=249992 Summary: Can't log in to IMAP server running dovecot 2.0.1 Product: Akonadi Version: 1.4.0 Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: b...@arklinux.org CC: vkra...@kde.org, kdepim-bugs@kde.org Version: 1.4.0 (using KDE 4.5.0) OS:Linux When trying to set up an account on a IMAP server running dovecot 2.0.1, akonadi (run from kmail) complains The server refused the supplied username and password. Do you want to go to settings, have another attempt at logging in, or do nothing? SASL(0): successful result: The login actually succeeded (if I type the password again in the dialog, I get IMAP session in the wrong state for authentication because I'm already logged in), but kmail/akonadi thinks it didn't. The SASL version in use is cyrus-sasl 2.1.24-rc1. Reproducible: Always Steps to Reproduce: Try to configure an IMAP account on a dovecot 2.0.1 server with kmail from the 4.5 branch in SVN Actual Results: Fails with SASL(0): successful result: Expected Results: Succeeds -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 225632] New: akonadiserver fails to start with mysql 5.5.1
https://bugs.kde.org/show_bug.cgi?id=225632 Summary: akonadiserver fails to start with mysql 5.5.1 Product: Akonadi Version: 4.4 Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: vkra...@kde.org ReportedBy: b...@arklinux.org CC: kdepim-bugs@kde.org Version:(using KDE 4.4.0) Compiler: gcc 4.4.3 OS:Linux Installed from:Compiled From Sources With mysql 5.5.1-m2, akonadiserver fails to start (this is on first startup, so all configs are at the defaults). The self-test says Database driver found. MySQL server found. MySQL server is executable. MySQL server log contains errors. -- MySQL server default configuration found. MySQL server custom configuration not available. MySQL server configuration is usable. akonadictl found and usable Akonadi control process not registered at D-Bus. -- Akonadi server process not registered at D-Bus. -- Nepomuk search service not registered at D-Bus. -- Protocol version check not possible. No resource agents found. -- No current Akonadi server error log found. No previous Akonadi server error log found. No current Akonadi control error log found. No previous Akonadi control error log found. Looking at the errors in more detail: MySQL server log contains errors: It actually does -- that's why the problem may be related to using mysql 5.5.1: 100205 15:06:16 [Note] Plugin 'FEDERATED' is disabled. 100205 15:06:16 [Note] Plugin 'ndbcluster' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 100205 15:06:16 InnoDB: Retrying to lock the first data file InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files.
[Bug 225632] akonadiserver fails to start with mysql 5.5.1
https://bugs.kde.org/show_bug.cgi?id=225632 --- Comment #1 from Bernhard Rosenkraenzer bero arklinux org 2010-02-05 16:00:28 --- FWIW after this happens, mysqld is still running /usr/sbin/mysqld --defaults-file=/home/arklinux/.local/share/akonadi//mysql.conf --datadir=/home/arklinux/.local/share/akonadi/db_data/ --socket=/home/arklinux/.local/share/akonadi/db_misc/mysql.socket And I can talk to it through that socket - but akonadiserver isn't running. Without further debugging, this looks like akonadi server respawns mysqld a couple of times (causing the Unable to lock errors), but doesn't stay around long enough to see the mysql server that works. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 179765] KMail crashed when selecting an IMAP folder
http://bugs.kde.org/show_bug.cgi?id=179765 Bernhard Rosenkraenzer bero arklinux org changed: What|Removed |Added CC|b...@arklinux.org | --- Comment #29 from Bernhard Rosenkraenzer bero arklinux org 2009-01-17 19:31:39 --- Finally got around to updating -- fix confirmed, works for me now. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 171043] New: kmail loses IMAP account information on hard poweroff
http://bugs.kde.org/show_bug.cgi?id=171043 Summary: kmail loses IMAP account information on hard poweroff Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using KDE 4.1.1) Compiler: gcc 4.3.2 OS:Linux Installed from:Compiled From Sources When doing a hard poweroff (e.g. running out of battery on a notebook that lacks proper ACPI support or power outage on a desktop box) while kmail is running, kmail forgets about the configured IMAP accounts, and goes to the account setup wizard on next startup. I'm not sure if this happens all the time, but it has happened a number of times here. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 159075] New: The IMAP account config dialog is too big to show on 1280x800
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=159075 Summary: The IMAP account config dialog is too big to show on 1280x800 Product: kmail Version: 1.9.50 Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: bero arklinux org Version: 1.9.50 (using Devel) Installed from:Compiled sources Compiler: gcc 4.3.0 OS:Linux When using a resolution of 1280x800 (or lower), the bottom entries of the IMAP config dialog (e.g. identity to use) isn't visible (hidden below the plasma panel/bottom of screen). There's plenty of space horizontally, splitting it in 2 columns might be an option. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 154911] New: Messages sent with current kdepimlibs/kdepim SVN arrive as blank messages on the smtp server
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=154911
Summary: Messages sent with current kdepimlibs/kdepim SVN arrive
as blank messages on the smtp server
Product: kmail
Version: 1.9.50
Platform: Compiled Sources
OS/Version: Linux
Status: NEW
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdepim-bugs kde org
ReportedBy: bero arklinux org
Version: 1.9.50 (using KDE Devel)
Installed from:Compiled sources
Compiler: gcc 4.3-svn 131213
OS:Linux
Messages sent with current kdepimlibs and kdepim SVN are ok in the outbox and
sent-mail folders, but arrive as blank/bogus messages on the smtp server.
kdelibs rev. 754673
kdepimlibs rev. 754919
kdepim rev. 754957
I've used a recent gcc 4.3 snapshot to compile; this might be a compiler
specific issue - but given gcc 4.3 works pretty well by now (but, like any new
gcc, barfs on many things older versions accepted) this is likely to be a
hidden problem in kio_smtp.
strace-ing the kio_smtp process shows:
[...]
read(4, 220 www.arklinux.org ESMTP Postfix\r\n, 36) = 36
uname({sys=Linux, node=localhost.localdomain, ...}) = 0
gettimeofday({1199121509, 479804}, NULL) = 0
gettimeofday({1199121509, 479830}, NULL) = 0
select(5, [4], [4], NULL, {0, 0}) = 1 (out [4], left {0, 0})
write(4, EHLO localhost.localdomain\r\n, 28) = 28
gettimeofday({1199121509, 479958}, NULL) = 0
gettimeofday({1199121509, 479978}, NULL) = 0
select(5, [4], [], NULL, {600, 0}) = 1 (in [4], left {599, 683000})
ioctl(4, FIONREAD, [125]) = 0
read(4, 250-www.arklinux.org\r\n250-PIPELINING\r\n250-SIZE
2048\r\n250-VRFY\r\n250-ETRN\r\n250-ENHANCEDSTATUSCODES\r\n250-8BITMIME\r\n250
DSN\r\n, 125) = 125
gettimeofday({1199121509, 797444}, NULL) = 0
gettimeofday({1199121509, 797471}, NULL) = 0
select(5, [4], [4], NULL, {0, 0}) = 1 (out [4], left {0, 0})
write(4, MAIL FROM:bero arklinux org SIZE=402\r\nRCPT TO:bero arklinux
org\r\nDATA\r\n, 75) = 75
gettimeofday({1199121509, 797620}, NULL) = 0
gettimeofday({1199121509, 797640}, NULL) = 0
select(5, [4], [], NULL, {600, 0}) = 1 (in [4], left {599, 751000})
ioctl(4, FIONREAD, [65])= 0
read(4, 250 2.1.0 Ok\r\n250 2.1.5 Ok\r\n354 End data with
CRLF.CRLF\r\n, 65) = 65
gettimeofday({1199121510, 47422}, NULL) = 0
gettimeofday({1199121510, 47448}, NULL) = 0
select(4, [3], [3], NULL, NULL) = 1 (out [3])
write(3, 8_6c_\0\0\0\0\0\0\0\0, 18) = 18
gettimeofday({1199121510, 47737}, NULL) = 0
gettimeofday({1199121510, 47759}, NULL) = 0
select(4, [3], [3], NULL, NULL) = 1 (out [3])
write(3, 0_65_, 10) = 10
gettimeofday({1199121510, 47949}, NULL) = 0
gettimeofday({1199121510, 47969}, NULL) = 0
gettimeofday({1199121510, 47986}, NULL) = 0
select(4, [3], [], NULL, NULL) = 1 (in [3])
ioctl(3, FIONREAD, [10])= 0
read(3, 0_64_, 4106) = 10
gettimeofday({1199121510, 48100}, NULL) = 0
gettimeofday({1199121510, 48120}, NULL) = 0
select(5, [4], [4], NULL, {0, 0}) = 1 (out [4], left {0, 0})
write(4, .\r\n, 3)= 3
gettimeofday({1199121510, 48236}, NULL) = 0
gettimeofday({1199121510, 48254}, NULL) = 0
select(5, [4], [], NULL, {600, 0}) = 1 (in [4], left {599, 759000})
ioctl(4, FIONREAD, [37])= 0
read(4, 250 2.0.0 Ok: queued as 6426A7C0594\r\n, 37) = 37
gettimeofday({1199121510, 289322}, NULL) = 0
gettimeofday({1199121510, 289349}, NULL) = 0
select(4, [3], [3], NULL, NULL) = 1 (out [3])
[...]
Anything sent after DATA is bogus - the message was simply
Subject: test
test
test
test
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 154911] Messages sent with current kdepimlibs/kdepim SVN arrive as blank messages on the smtp server
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=154911 --- Additional Comments From bero arklinux org 2007-12-31 18:27 --- Created an attachment (id=22784) -- (http://bugs.kde.org/attachment.cgi?id=22784action=view) Message as it appears in the sent-mail folder ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
