Weird downloaded media filenames
Closed this issue · 15 comments
I usually download mp3 files from "Media browser" without issues. However, when I was looking for that files in the folder where QMP2 download files, I didn't find my recently downloaded files by their names. The, I noticed the names assigned are not as usually:
Any suggestion?
It takes part of URL as a name.
What do you mean? That always worked fine. Maybe is a change in myfreemp3.
That's weird issue, works on Qt5, doesn't work on Qt 6.8.0. I'll investigate...
Looks like Qt 6.8.0 bug (didn't check 6.7.3 yet) or they intentionally changed behavior making software works differently after Qt update?
So, will it be fixed in next release?
Yes. Temporarily you can use older Qt.
Reverting to previous versions of QT is becoming increasingly complicated because some databases (like akonadi or digikam) change structure and there is no backward compatibility, so I will have to wait for your next version.
Thank you very much for resolving it so quickly.
I can see you use SUSE package, maybe maintainer could backport this fix: f6ffb5f before new release?
For me, it's a madness to try to contact maintainer (I tried some times and I have no success). I'm using Tumbleweed version, so I expect it will not take too much.
Ok!
I think it's because of Qt 6.8.0 QML change mentioned in change log:
14bb25f69c QJSEngine: Treat empty string literals as non-null, empty QStrings Assigning an empty JavaScript string to a property of type QString now produces only an empty QString, not a null QString.
I was checking for null QString - this behavior has been changed in 6.8.0, so it changes application behavior. Bad from Qt side to do such things. IMHO they should do it for Qt 7.0.0 and communicate this change better...
Unfortunately, I have a lot of experience with KDE's communication problems with users. The latest has been that they suddenly made an application (Knotes) disappear, without even providing a valid solution for all of us who used the application. And that is just one of many changes that periodically affect the user who has to figure out how to solve the problems they are not even aware they create. The worst part is that if you communicate the problem to them, their "priorities" are for other things...
I see 😅
KDE is based on Qt, Qt is developed mostly by different people, but they has similar problems with breaking things (even if it is maybe better now - breaks compatibility with just an update, not major version change).
KDE removed ksysguard, but luckily there's a Qt6 fork available on AUR which works maybe better than official Qt5 app 😄
It should be working correctly in Qt 6.8.x and 24.12.06!