Package Details: deadbeef-plugin-lyricbar-git r74.g015379a-1

Git Clone URL: (read-only, click to copy)
Package Base: deadbeef-plugin-lyricbar-git
Description: DeaDBeeF lyric bar plugin
Upstream URL:
Licenses: MIT
Submitter: dpirate
Maintainer: dpirate
Last Packager: dpirate
Votes: 3
Popularity: 0.000001
First Submitted: 2019-01-26 06:39
Last Updated: 2020-04-07 13:37

Dependencies (5)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

dpirate commented on 2019-01-27 05:54

So, I think I found the problem. I use Gtk+ 3, and lyricbar loads the Gtk+ 3 version of the plug-in just fine sometimes when the Gtk+ 3 plug-in ends up being loaded first. But I always get a warning that deadbeef can't load the Gtk+ 2 plugin. So I looked at the source code, and there are separate plugin ids when the plug-in is built either for Gtk+ 2 or Gtk+ 3. What is presumably happening here is that the Makefile has no dependencies for rebuilding the Gtk+ 2 version, so it just links the already built object files for Gtk+ 3 against gtkmm for Gtk+ 2 without changing the plug-in id. So the Gtk+ 2 plug-in ends up with the id of the Gtk+ 3 plug-in. I'm working on a patch to the Makefile to fix this.

dpirate commented on 2019-01-26 08:37

Ok. I will do that. Thanks.

VolkMilit commented on 2019-01-26 08:36

Oh, and also, answer your question: I think you should request for deletion deadbeef-plugin-lyricsbar-git for prevent confusion. GitHub repository is down forever, so it's pointless to keep it here.

VolkMilit commented on 2019-01-26 08:30

Yes, I have both.

dpirate commented on 2019-01-26 08:27

Also, do you have both gtkmm and gtkmm3 installed?

dpirate commented on 2019-01-26 08:26

I'm going to experiment with changing the internal plug-in name and if that doesn't solve the problem, then subpackage.

VolkMilit commented on 2019-01-26 08:23

I experimented a little, and yes, GTK3 version conflicts somehow with GTK2. That doesn't explain why it didn't work before tho, because I was build gtk2 only. So I think you need to separate them.

VolkMilit commented on 2019-01-26 08:06

Well, I don't know. As I said before, I was able to build it without problem and use it for a while about 3 hours ago. Now it, oddly, doesn't work.

EDIT: Now it's works again. Magic.

dpirate commented on 2019-01-26 08:02

So should I just remove the gtk+2 plug-in for now?

VolkMilit commented on 2019-01-26 07:59

Nope, I make only gtk2 version, without PKGBUILD. undefined symbol: _ZN3Gtk10TextBuffer16insert_with_tagsERKNS_8TextIterERKN4Glib7ustringERKSt6vectorINS4_6RefPtrINS_7TextTagEEESaISB_EE

Odd. When I build it last time, it works. Now it doesn't.