Bug 24219 - If you have proxy set for http during update kmail will try to use this to connect to an IMAP server
Summary: If you have proxy set for http during update kmail will try to use this to co...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-21 19:43 CET by Dag Nygren
Modified: 2020-08-16 22:26 CEST (History)
3 users (show)

See Also:
Source RPM: kmail-17.12.2
CVE:
Status comment:


Attachments

Description Dag Nygren 2019-01-21 19:43:29 CET
Description of problem:
Updated Mageia 6 with tha last update. After that the connection from akonadi
to the local IMAP server generated an error "Connection to server lost  8".

Unsetting all the system proxy settings (http_proxy, https_proxy and ftp_proxy)
suprisingly made it possible to connect again.

But after setting the proxies back it STILL (??) works.

Version-Release number of selected component (if applicable):
kmail-17.12.2

How reproducible:
Always after upgrade (?)

Steps to Reproduce:
1.Use your email normally
2.Upgdate Mageia with newest updates
3.Find that IMAP connection will not work

This is really more of a hint for the others that are seeing the same problem but if there is something the distro can do to prevent it would have saved me some hours of tracing and debugging.
Comment 1 Dag Nygren 2019-01-21 20:03:21 CET
Tested a bit more and:

- The critical setting is http_proxy

- After a relogin this can always be repeated even after the upgrade
  which elevates this to a real bug, not an annoyance.

- And it is the "system proxy" that affects this not the KDE proxy setting (which was set to "No proxy") Checked with something else set here and it doesnt make a difference

Severity: minor => normal

Comment 2 Marja Van Waes 2019-01-22 14:58:40 CET
Does this only happen with kmail, or also with other e-mail clients?

How exactly did you set your http proxy?

CC: (none) => kde, marja11
Keywords: (none) => NEEDINFO

Comment 3 Dag Nygren 2019-01-22 15:21:15 CET
Only in kmail.
Saw some vague hints on the web about the kf5 socket interface behving strangely lately.
Might be related to that.

http_proxy set in drakconf.
Comment 4 Marja Van Waes 2019-01-22 15:42:20 CET
(In reply to Dag Nygren from comment #3)
> Only in kmail.
> Saw some vague hints on the web about the kf5 socket interface behving
> strangely lately.
> Might be related to that.
> 
> http_proxy set in drakconf.

Thanks, assigning to the KDE maintainers and CC'ing the Mageia Tools maintainers.

Assignee: bugsquad => kde
CC: kde => mageiatools

Marja Van Waes 2019-01-22 15:42:29 CET

Keywords: NEEDINFO => (none)

Comment 5 Aurelien Oudelet 2020-08-16 22:26:23 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien


Note You need to log in before you can comment on or make changes to this bug.