Bug 134544 - Cover manager: errors in writing covers aren't handled gracefully
Summary: Cover manager: errors in writing covers aren't handled gracefully
Status: RESOLVED DUPLICATE of bug 126283
Alias: None
Product: amarok
Classification: Applications
Component: Collection Browser (show other bugs)
Version: 2.0-SVN
Platform: Compiled Sources Linux
: LO normal
Target Milestone: 2.3.1
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-23 18:29 UTC by Frans Englich
Modified: 2009-09-27 14:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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 ***