Scrobbling through proxy does still not work in RC 1

[Jeff Mitchell]

Leo Franchi wrote:
> On 1 Dec 2008, at 12:07, Jeff Mitchell wrote:
> 
>>> Jan Holthuis wrote:
>>>> Hi!
>>>> Some time ago I reported, that Last.FM scrobbling through doesn't  
>>>> work (→ http://mail.kde.org/pipermail/amarok/2008-October/006961.htm 
>>>> l). Unfortunately, it does still not work in Amarok 2 RC1  
>>>> »Narwhal«, which is a bit disappointing, because it's the only  
>>>> bug that prevents me from using Amarok2 every day. Is there any  
>>>> chance »scrobbling through proxy« will make it into Amarok 2.0  
>>>> Final?
>>>>
>>>> PS: Is it possible, that it's not amarok's fault, but related to  
>>>> bug #155707 (→ http://bugs.kde.org/show_bug.cgi?id=155707) ?
>>>>
>>>> Thanks in Advance,
>>>> Jan Holthuis
>> This isn't our fault, really.
>>
>> We use KDE network settings, and KDE still does not have working proxy
>> settings in 4.1.  I know it was a task for 4.2 but I have no idea if
>> they have actually fixed it or not.
>>
>> When KDE in general gets working proxy support, then Amarok's  
>> scrobbling
>> and other http lookups (like Wikipedia) should work too.
> 
> Sorry Jeff, but this is incorrect. For scrobbling, we are using the  
> liblastfm provided by Last.Fm, which will soon be released  
> independently. As this is a Qt-based lib (and not KDE-based), it does  
> not use KIO to do its network connections, but rather the  
> QNetworkAccessManager framework.
> 
> There will be a way to set a QProxy for the library to use. However, I  
> have so far been unable to figure out how to actually *retreive* a  
> QProxy or similar description of the proxy settings from the KIO libs.
> 
> So that is the blocker which we need to solve before scrobbling will  
> work through proxies. It has nothing to do with network settings  
> directly in 4.1.

OK, but it's a related issue.  One of the reasons, AFAIK, that KDE has
it difficult doing proxy stuff is that while Qt network classes can uses
proxies, they don't look at the existing proxy info on the various
platforms, so they have to always be specified manually, which means you
need config dialogs and the like.

I imagine we'll run into the same issue using Qt proxies directly.

--Jeff