![]() Registered Member ![]()
|
(I assume that the information I provide are not enough for submitting it to bugs.kde.org; a quick search did not return a report on this, though I might have chosen the wrong search terms) maybe someone knows this behaviour or feels up to assissting me in gathering any information missing?)
Using: Amarok 1.4.9.1 from the Ubuntu repos. What did I do? After clearing my mp3player, I transferred songs from the collection to the device using amarok's "Transfer to Media Device"-feature. Accidentally, I selected an entire artist for transferring rather than just the songs I wanted, which left me with 1.5GB in the queue, exceeding the mp3player's capacities by roughly 1GB (500MB or so were already transferred; its nominal capacity is 1GB). I weeded out the queue, started the transfer and received "can't copy file ... to ..." for two of the songs. Fair enough; halfway through the transfer, though, I noticed an odd behaviour: The reported queue size jumped from a few hundred MB to 16 777 216TB. It stayed like this after the transfer had completed, leaving me with the two failed songs in queue reported as having an incredible size... (after dis- and reconnecting -using the buttons in amarok-, the reported queue size remained but I could finish the transfer) [update] I just watched the transfer of another album: Its original size was correctly reported at 10 songs/40.8MB, during the transfer the filesize went down faster than the track count, leaving me with 6 songs/4MB before it jumped to 5 songs/16 777 216TB...
Last edited by see-g on Mon Jul 07, 2008 10:36 am, edited 1 time in total.
|
![]() Moderator ![]()
|
This has been mentioned here before, and doesn't seem to affect functionality...
See http://amarok.kde.org/forum/index.php/t ... l#msg21223
"There are two theories to arguing with women. Neither one works."
. If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss" |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot]