Bug 135786 - Aborting resumed podcasts, after they are completed, crashes amarok.
Summary: Aborting resumed podcasts, after they are completed, crashes amarok.
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: Podcast (show other bugs)
Version: 1.4.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-17 04:50 UTC by Phill MV
Modified: 2008-08-04 17:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phill MV 2006-10-17 04:50:07 UTC
Version:           1.4.0 (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
OS:                Linux

Background info: I have a shitty ISP. 
When I max out, or come close to maxing out, my outbound bandwidth for long periods of times for some reason every connection will then timeout for some  amount of time before everything starts working again. 
I *have* to use "wget -c --retry-connrefused -t inf --timeout=30" to get large files overnight, or else I'll have a very small partial file in the morning waiting for me.

Bug occurs whenever I do the following:
1. I merrily download several podcasts at a time (i.e. TVO Big Ideas, CBC3 Podcast, CBC Radio Best of Ideas, etc). I merrily watch the download meter slowly but surely increase.

2. My internet connection times out, and starts working again. Gaim drops. I reload whatever page was loading in Firefox. 

3. Amarok isn't made aware of this issue, or at least doesn't know how to handle connection time outs. The files download bars stop dead in their tracks. (For purposes of illustration, let's say I have podcast "foo" at 47% and podcast "bar" at 62%)

4. Being lazy, I don't click the abort file dialog from the status bar download indicator. I sigh and right click (in the playlist sidebar) to resume the podcast download. Foo and Bar resume normally, and finish downloading. This creates two new entries in the download resume tab; Foo and Bar, which increment normally, and Foo and Bar, stalled at 47% and 62%.

5. The entries in the 'download' tab, in the status bar, that refered to the download that I _resumed_ disappear when the files download. The entries that were there when the downloads originally stalled stay put.

6. I click 'abort' on the entries that stalled.

7. A message window pops up telling me that it couldn't find KMail (Ubuntu defaults to Gnome, so that's quite to be expected). Amarok continues to work quite normally until I click "Ok" in this message window, which closes amarok with it.

--
This is somewhat hard for me to reproduce, but it's happened some 3 or 4 times now. I think my program 'expectations' still hold up tho.

What I expected: Amarok should've had some reasonbly small connection time out timer, and retried, I don't know, 90 secs later without bothering me about it until there are x many connection timeouts. Whatever wget defaults to is probably a same measure.

What actually happened: Something in Amarok decided it was healthy to crash, although there was no real reason for it to do so.

(Thanks for an otherwise mostly totally awesome music player.)
Comment 1 Phill MV 2006-10-17 04:53:22 UTC
Right, I forgot to mention more specifically. I get amarok from the apt-get repo http://kubuntu.org/packages/amarok-14. Not quite the "Ubuntu sources". 1.4.0 is still the most recent one from there.
Comment 2 Martin Aumueller 2006-10-17 08:55:17 UTC
Could you please use the dapper backports repository for installing Amarok? This will give you 1.4.3. Please check with that version if you still have this problem.
Comment 3 Myriam Schweingruber 2008-08-04 17:08:27 UTC
Closing due to lack of feedback.
Amarok 1.4.x is no longer actively maintained as all the focus is on Amarok 2.0. Feel free to report any bug you come across in Amarok 2.0-