Bug 240249

Summary:	cover should show same image as podcast tool automatically
Product:	[Applications] amarok	Reporter:	missive
Component:	Podcast	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bart.cerneels, stuffcorpse
Priority:	NOR
Version:	2.3.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	2.3.1

Description missive 2010-05-31 18:04:41 UTC

Version:           2.3.0 (using KDE 4.4.2) 
OS:                Linux

When I add a podcast in the podcast pane, an image is automatically shown in the same place that an album cover would show in the collection browser. However, in the other views (Current Track and Playlist for example) the cover shows as the default blank cover.

Ideally, the podcast image should also show as the cover in those other views.


Reproducible: Always

Steps to Reproduce:
Add podcast.
Image shows up in podcast browser automatically.
Pick a podcast episode and play it.


Actual Results:  
Image in Current Track view and Playlist shows default "no image" image.

Expected Results:  
Image in Current Track view and Playlist shows same image as in podcast browser.


OS: Linux (i686) release 2.6.32-22-generic
Compiler: cc

Comment 1 Myriam Schweingruber 2010-06-01 01:03:05 UTC

This is fixed in the new Amarok 2.3.1.

Comment 2 missive 2010-08-11 18:19:30 UTC

I have updated to 2.3.1 (Kubuntu ppa packages -- although strangely, the "About Amarok" shows using KDE 4.4.2 instead of 4.5) and podcasts still show the default image instead of the automatically downloaded podcast image.

Version 2.3.1
Using KDE 4.4.2 (KDE 4.4.2)
Build Date: May 31 2010

Comment 3 Myriam Schweingruber 2010-08-12 00:18:48 UTC

I shows here, just not for downloaded podcasts, but that is a different bug 229391. Please check if you test with a downloaded podcast, that would be a different bug, then.

Comment 4 missive 2010-08-12 00:29:23 UTC

Ok. Yes, I usually download before listening, so this bug is a duplicate of Bug 229391.

Thanks for the info.

*** This bug has been marked as a duplicate of bug 229391 ***