https://bugs.kde.org/show_bug.cgi?id=371766
Bug ID: 371766
Summary: Minimize to tray stopped working in 2.5.0
Product: krusader
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Se
https://bugs.kde.org/show_bug.cgi?id=350920
--- Comment #8 from Stephen Anthony ---
Along with minimize to tray, clicking the 'X' (close) button on the main window
used to do the same thing (ie, minimize to tray). Now it closes the app. Is
this a related bug, or should a new bug
https://bugs.kde.org/show_bug.cgi?id=350920
--- Comment #10 from Stephen Anthony ---
I guess it's not really needed. You're right that the description is exactly
what it does now. But it could also be considered a regression, since the 4.x
version worked with the close button too.
https://bugs.kde.org/show_bug.cgi?id=388068
Stephen Anthony changed:
What|Removed |Added
CC||stephena@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=388079
Stephen Anthony changed:
What|Removed |Added
CC||stephena@users.sourceforge
https://bugs.kde.org/show_bug.cgi?id=388068
--- Comment #5 from Stephen Anthony ---
Switching to TLS for smtp.gmail.com doesn't work for me; it still complains
about either "server error" or "mail transport failed".
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388068
--- Comment #7 from Stephen Anthony ---
OK, checked port and restarted Akonadi. Got a popup saying that the message
was sent successfully. On the console where I restarted Akonadi, I got message
saying "org.kde.pim.ksmtp: Socket error: 2"
https://bugs.kde.org/show_bug.cgi?id=388068
--- Comment #19 from Stephen Anthony ---
Tangentially related to this issue; is it better to use SSL or TLS when a
server offers both? I've changed to TLS to 'work around' this current issue,
but I wonder if I should just leave it that
https://bugs.kde.org/show_bug.cgi?id=352464
--- Comment #20 from Stephen Anthony ---
As of the following updates to Ubuntu 15.10 (backported from 16.04):
Version 5.0.2
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
this problem is fixed for me. I don't know if it was th
