1. There are no settings (any longer) in amarok itself.

2. The proxy settings of KDE are not applied to / used by amarok.

Under these considerations, I wonder how I could use amarok behind a strict Forefront TMG firewall?

Thanks,

Uwe

No need to post duplicate entries...
Did you try restarting KDE after you changed your proxy settings? Amarok uses what is provided by the system.

Mamarok wrote:No need to post duplicate entries...
Did you try restarting KDE after you changed your proxy settings? Amarok uses what is provided by the system.

Is this a dup? Then my excuses. I am posting so many things these days, because so many things don't work ... .

Yes. I have restarted the PC. I have as well filed this behaviour as bug. It turned out that it is a known bug, that the system-wide proxy settings are simply discarded by all applications on KDE (and likewise on Gnome, by the way).
Exactly therefore my question, what to do? Should I file a 'RFE'; although the proxy settings have been removed rather recently from amarok?

Uwe

Well, you submitted this thread twice, so I remove one.

Amarok 2.x never handled proxy itself, it always relied on what the system provides. Also, Amarok 2.x is a complete rewrite, so nothing has been removed.

Please file a bug here: https://bugs.kde.org/enter_bug.cgi?prod ... Management

this is definitely not an Amarok problem.

Thanks, but I had filed that bug, and was actually hoping to be able to *use* amarok, before the bug will eventually go away.
I know that amarok 2.x is a rewrite. I meant the proxy settings that used to be available in 1.x.

Thanks a bunch anyway,

Uwe

udippel wrote:Thanks, but I had filed that bug, and was actually hoping to be able to *use* amarok, before the bug will eventually go away.
I know that amarok 2.x is a rewrite. I meant the proxy settings that used to be available in 1.x.

Thanks a bunch anyway,

Uwe

Actually you can use amarok under a proxy, but you have to launch it :

$ http_proxy="http://proxy:port/" amarok

MuLLeR wrote:
Actually you can use amarok under a proxy, but you have to launch it :

$ http_proxy="http://proxy:port/" amarok

If you read the whole thread, you might have noticed that this *does not* work, when the organisation uses strong passwords (NTLMv2).
Your solution applies only to transparent proxies without *any* authentication.

Uwe

udippel wrote:

MuLLeR wrote:
Actually you can use amarok under a proxy, but you have to launch it :

$ http_proxy="http://proxy:port/" amarok

If you read the whole thread, you might have noticed that this *does not* work, when the organisation uses strong passwords (NTLMv2).
Your solution applies only to transparent proxies without *any* authentication.

Uwe

Have you tried like

Code: Select all

$ http_proxy="http://domain\\user:pass@server.xx:port" amarok


MuLLeR wrote:Have you tried like

Code: Select all

$ http_proxy="http://domain\\user:pass@server.xx:port" amarok


Yep. Alas, this does *not* support NTLMv2 authentication. (Everyone has been suggesting this all the time - I feel like yelling *this does not work with NTLMv2*.)
My request stems from the fact, that only cntlm and ntlmaps support this strong authentication. Both work as 'additional' proxies, and work well. So an application needs to be able to set its own proxy settings to 127.0.0.1:[portnumber]. Since Amarok cannot, no Amarok in any organisation with strong proxies.
(This applies to *all* KDE applications, by the way, because the built-in system-wide proxy has 2 major problems:
- One cannot enter username/password
- KDE does not respect its settings
If you don't believe me, search the bug database. These are confirmed bugs.)

As a consequence: no Amarok in any organisation world-wide with strong authentication. And, to be complete, no other KDE-web-application either.
That's 2010, the year of Linux on the desktop for you.

Uwe

Sorry, but putting the blame of a company policy imposing strong encryption on a proxy on Amarok is a bit harsh... how about asking the company sysadmins to give it a web access exception? Did you even think of the possibility that the strong encryption is enforced exactly for the reason to prevent people using Amarok?

The correct place for the blame is kio_http ( part of kdelibs ) in this case, which only supports NTLMv1 I believe.

I never seen a case where KIO does not follow its own proxy preferences however. Which operations in Amarok do not work?

bcooksley wrote:The correct place for the blame is kio_http ( part of kdelibs ) in this case, which only supports NTLMv1 I believe.

I never seen a case where KIO does not follow its own proxy preferences however. Which operations in Amarok do not work?

True (NTLMv1)

I don't understand your question, though. Amarok doesn't play, that's all, because it can't reach the Internet (I used to use it for streaming audio).
Had it a proxy setting, I could set it to my cntlm.

And the 'tight' settings are not to prevent me from using the Internet, but our unauthorised visitors.

Uwe

I gather you are trying to play streamed content then? ( like from Last.fm or Jamendo )

bcooksley wrote:I gather you are trying to play streamed content then? ( like from Last.fm or Jamendo )

Exactly. France Musique, that is. It is streaming (32k); as the transmission evolves. No problem before that new proxy came in (we had a transparent proxy without authentication).

Does Last.fm scrobble correctly? This is likely an interaction bug between liblastfm and KDE / Amarok.