Summary: | 2.1 -2.2: different behaviour of event Amarok.Engine.trackFinished | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Rico Zienke <zonken> |
Component: | Tools/Script Manager | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | peterzhoulei |
Priority: | NOR | ||
Version: | 2.3-GIT | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Rico Zienke
2009-10-24 19:43:51 UTC
Created attachment 37891 test1 Created attachment 37892 test2 Created attachment 37893 test3 i close no reaction and I'm living now with 2.2 behaviour Please close this correctly if you decide so. Amarok is by no means unmaintained. (In reply to comment #5) > Amarok is by no means unmaintained. I do not understand this. I think my bug was not invalid otherwise I would mark it as invalid. There was no response and the new behaviour seems to be stable. The amarok releases are faster then this report belonging to one special release, that no one takes care. So I guess unmaintained fits more then invalid. which is pure rubbish, just because nobody answered your report Amarok is not unmaintained. But I think it is pointless to change this back and forth *sigh*. Changing status, according to this forum post: http://forum.kde.org/viewtopic.php?f=117&t=83115#p156336 |