[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD

2018-10-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381850

--- Comment #7 from gr...@kde.org ---
Left akonadi and kmail running overnight, and now bumped into a case of "world
is going to end" again. Stopped akonadi, quit kmail, bumped sysctl and the
messages I previously couldn't read, now were ok again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD

2018-10-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381850

--- Comment #6 from gr...@kde.org ---
I just built 11-STABLE (r 339415) and rebooted, after commenting-out the
changes in the sysctls. KMail still seems to work, but the thing was that you
wouldn't *necessarily* have KMail fall over on you immediately. So let's call
it "probably fixed, sysctls no longer needed" -- but it needs some longer
period of trying it out.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD

2018-10-17 Thread Edward Tomasz Napierala
https://bugs.kde.org/show_bug.cgi?id=381850

--- Comment #5 from Edward Tomasz Napierala  ---
FWIW, I'm wondering if it could have been fixed in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181741.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD

2018-10-17 Thread Alexandre Martins
https://bugs.kde.org/show_bug.cgi?id=381850

--- Comment #4 from Alexandre Martins  ---
(In reply to Edward Tomasz Napierala from comment #3)
> Just wondering...  is the workaround still neccessary with 12.0-ALPHA or
> recent 11-STABLE?  Thanks!

I'm working with the last FreeBSD 11.2, and I still need the workaround.

I don't know for the latest versions, sorry.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD

2018-10-17 Thread Edward Tomasz Napierala
https://bugs.kde.org/show_bug.cgi?id=381850

Edward Tomasz Napierala  changed:

   What|Removed |Added

 CC||tr...@freebsd.org

--- Comment #3 from Edward Tomasz Napierala  ---
Just wondering...  is the workaround still neccessary with 12.0-ALPHA or recent
11-STABLE?  Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD

2018-04-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381850

gr...@kde.org changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||gr...@kde.org

--- Comment #2 from gr...@kde.org ---
On my 11.1-amd64 box, it's the two stream settings,
net.local.stream.recvspace=65536 and net.local.stream.sendspace=65536 seem to
have done the trick. I'll use KMail some more today and see what happens.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD

2018-04-12 Thread Alexandre Martins
https://bugs.kde.org/show_bug.cgi?id=381850

Alexandre Martins  changed:

   What|Removed |Added

 CC||deadma...@gmail.com

--- Comment #1 from Alexandre Martins  ---
I found the problem on my FreeBSD 11.1 !

It's due to the size of the UNIX socket. On FreeBSD, it's defaulted to 8Kb, but
on Linux it is much more large !

On my PC, it just increase the size to 64k and it's working. For that, put the
followinf lines into /etc/sysctl.conf file:

net.local.stream.recvspace=65536
net.local.stream.sendspace=65536
net.local.dgram.recvspace=65536
net.local.dgram.maxdgram=65536
net.local.seqpacket.recvspace=65536
net.local.seqpacket.maxseqpacket=65536

I don't known which one make the job ...

-- 
You are receiving this mail because:
You are the assignee for the bug.