Bug 134544

Summary:	Cover manager: errors in writing covers aren't handled gracefully
Product:	[Applications] amarok	Reporter:	Frans Englich <frans.englich>
Component:	Collection Browser	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	LO
Version First Reported In:	2.0-SVN
Target Milestone:	2.3.1
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Frans Englich 2006-09-23 18:29:08 UTC

Version:            (using KDE KDE 3.5.4)
Installed from:    Compiled From Sources
OS:                Linux

When "Fetching Missing Covers", I happened to run out of disk space(I found out, after a long time of mucking about). It seems Amarok doesn't handle out of disc space conditions, and possible also other errors(such as permission errors).

Amarok simply continued fetching covers but weren't able to display them.

I propose that 1) file errors are detected; and that 2) the cover fecthing is aborted; and 3) the user is informed.


Frans

Comment 1 Lydia Pintscher 2008-08-05 23:51:23 UTC

Can someone check this for Amarok 2 please?

Comment 2 Myriam Schweingruber 2009-08-13 11:06:13 UTC

Changing severity, else our query doesn't detect that.

Same problem as bug 189581 although not a direct duplicate.

We need more error messages when a destination is not writable, be this because of lack of space or permissions.

Comment 3 Myriam Schweingruber 2009-09-14 00:32:13 UTC

Setting target.

Comment 4 Myriam Schweingruber 2009-09-27 14:09:57 UTC

Marking as duplicate, since this would be solved if an error message would warn that nothing can be written.

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