Comment 7 for bug 1335116
Revision history for this message
| Erik Devriendt (erik-devriendt) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
It appears that my answer in Comment #4 was not correct. I do have http_proxy and no_proxy variables set in the shell.
These are probably caused by setting these Network Proxy in Control Center, al least, that would be logical.
I tested the new mintupdate by following the recipe in comment #6 for creating a package and installing it (appears to be version 4.6.8).
My results:
a. when starting mintupdate from the command line, I obtain the right information in the ChangeLog tab.
b. However, when I start mintupdate from the Control Center, or by logging out and then back in and then clicking the icon in the task bar, the ChangeLog tab only shows "No changelog available".
Could it be that when starting from the command line, mintupdate takes the *_proxy variables into account, but when it is started from login or control center, these environment variables are not yet set?
Anyhow, I would expect that mintupdate takes the values configured in Network Proxy into account since it is a program specific for Linux Mint, as is the Control Center.