minor issue with k3b being ported to plasma5

I am using the latest tumbleweed iso and have just updated the 3 k3b packages from the packman repo. These have now been ported over to kde frameworks 5.17.

The minor issue is that everytime I start k3b I get the warning message 'no mp3 decoder plugin' found. These are actual shown under k3b config screen. I put a tick in the don't show me this warning message again but this is ignored. Is there are setting file which I can amend - so k3b either stops doing this check or realises that the plugins are installed? Thanks.

Install kb3 and extra codecs package from packman

Thanks for positing. I already have the k3b-codecs package (from packman) installed - it is just not being reconised (following the move of k3b to frameworks) on starting up

May be a bug then but if you have the extra codecs package it should not do that

Quote:

---

Originally Posted by dth2

I am using the latest tumbleweed iso and have just updated the 3 k3b packages from the packman repo. These have now been ported over to kde frameworks 5.17.

The minor issue is that everytime I start k3b I get the warning message 'no mp3 decoder plugin' found. These are actual shown under k3b config screen. I put a tick in the don't show me this warning message again but this is ignored. Is there are setting file which I can amend - so k3b either stops doing this check or realises that the plugins are installed? Thanks.

---

I'm having the same issues here witk K3B on Tumbleweed after a "zypper dup" a couple of days ago, K3B was upgraded and now "mp3" support is not working anymore, was working fine before doing the upgrade!:(

Well I'll wait a couple of days to see if it get fixed!.

I am on it (put a qDebug() to receive the error):

Code:

---

Loading plugin "MAD-Dekodierer" failed. Error: "Plugin verification data mismatch in '/usr/lib64/qt5/plugins/k3bmaddecoder.so'"

---

Fixed:

https://quickgit.kde.org/?p=k3b.git&a=commit&h=046a102
https://pmbs.links2linux.de/package/...ev=base&rev=54

Am I being dozy or do the last posts to this thread mean that the issue has been reported to the packman website and that the problem will be corrected in a future k3b rpm?