| Summary: | Too much lines in the playlist browser .... | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | maxime.haselbauer |
| Component: | Playlists/Saved Playlists | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | andrew.crouthamel, arjan.ten.hoopen, bart.cerneels, vedant.kota |
| Priority: | NOR | ||
| Version First Reported In: | 2.8.0 | ||
| Target Milestone: | 2.9 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Picture of the bug | ||
|
Description
maxime.haselbauer
2013-08-18 08:43:21 UTC
Created attachment 81767 [details]
Picture of the bug
Look on the left side, too much empty lines in the playlist view
You are very welcome to give a hand in testing, we have only 24/7 in a day and do this in our free time. Of course this should have been reported earlier, but apparently nobody has a setup that allows to actually show this. I have many more saved playlists and this simply doesn't show in my use case. Testing all possible use-cases is simply impossible as there are as many as there are users. If you want your specific use case to be tested, I am afraid you will have to give hand during the beta testing. I was able to reproduce this with any number of songs in a playlist. There are as many extra lines as there are actual songs in every playlist. However, when I clicked on merged view this bug was visible. *And* when I went back to normal view the issue was resolved. I was not able to reproduce it again. Which makes it extra difficult to debug, as it is not reproducible in a reliable way. I am a bit pissed of that every time I post a bug on amarok I get as a response " Sorry but it is not the way WE are using amarok, also we will not solve this bug" Let me ask a question: Is it necessarily a good software design to have soooo much possible "usecases" that you can not test more than 0.000001 % of the software? If you don't have the manpower to develop&test it than why not reduce the wingspan (aka in this case: propose less possible view and way to filter them but make them reliable....) So far as the time arugment is concerned, we only have 24/7 but we have no deadline to respect (aka we should only release when ready), hence, there is no reason why it should be a problem;) And by the way if it is only due to my setup, then at least propose another one ;) Nobody said we would not fix it, else this would have been closed as WONTFIX, which is not the case. But you don't understand one important thing: this is apparently not reproducible in a reliable way, so it is very hard to debug. And to fix a bug it needs to be reproducible every time. A propos Not reliable: "Which makes it extra difficult to debug, as it is not reproducible in a reliable way." I just fresh installed Kubuntu 12.04 then upgraded to kde 4.11.1 from backports I did not change anything to the "out of the factory" configuration and guess what I can reproduce the bug ;) So again, it IS reproducible, no matter one want to accept it or not ;) cheers please place this bug on confirmed since I managed to on 3 machines with 3 Kubuntu release version thank you (sorry for your statistics by the way ........) Maxim, you don't understand: we can't reproduce this bug, so unless you can provide exact steps on how to reproduce this, there isn't really much we can do about. For a bug to change status as confirmed it needs to be reproducible by more than one person. So please, provide exact steps so we can at least try to reproduce it. With the information provided so far, I can't reproduce this with current amarok from git, v2.8.0-330-g3b5c6b2, Kubuntu 14.04, KDE 4.13.1, Qt 4.8.5 *** Bug 363992 has been marked as a duplicate of this bug. *** All, If you save a playlist to the amarok db then this behavior is *NOT* reproducible. However, if you save a playlist to disk this behavior *IS* reproducible. At least this is what I can reproduce on my machines. Hope this helps in reproducing the bug in various different environments. Kind regards, Arjan Closed per request of reporter. |