Package Details: libappindicator-gtk2 12.10.0-10

Git Clone URL: (read-only)
Package Base: libappindicator
Description: Allow applications to extend a menu via Ayatana indicators in Unity, KDE or Systray.
Upstream URL:
Licenses: LGPL3, LGPL2.1
Conflicts: libappindicator
Provides: libappindicator
Submitter: City-busz
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 424
Popularity: 10.735042
First Submitted: 2011-02-02 15:19
Last Updated: 2016-08-07 12:12

Required by (40)

Sources (2)

Latest Comments

LKHN commented on 2016-07-11 18:42

Oh man you made my day! I remember that when i am replacing gcc with gcc-multilib my internet connection disconnect (or someting happens cant remmeber) gcc uninstalled but gcc-multilib have not installed. İn short installed gcc-multilib and updated libappindicator package perfectly. Thank you very much i appreciate that :)

WoefulDerelict commented on 2016-07-11 18:13

LKHN: In a rather unexpected turn of events the build is complaining that it can not find an appropriate compiler on your system. GCC is part of base-devel and generally should be installed on the system before attempting to build anything. Many users install the base-devel group as part of their initial pacstrap. It doesn't follow that you should have been able satisfy the make dependencies for this package without a compiler as the libdbusmenu and libindicator packages would have needed it.

I suspect the first place to start would be to verify if you have a compiler on your system. You could start by asking pacman if GCC is there with: pacman -Q gcc

pacman has a log file that you can check to see if things have been installed/uninstalled.

LKHN commented on 2016-07-11 15:47

I have same problem at libappindicator-gtk2 , libappindicator-gtk3 , libappindicator-sharp . Please help me

Error when installing -

libappindicator-gtk2 config.log -
libappindicator-gtk3 config.log -
libappindicator-sharp config.log -

Rhinoceros commented on 2016-07-01 02:10

Thank you! It builds perfectly now.

WoefulDerelict commented on 2016-07-01 01:25

Rhinoceros: It appears I broke the mono bindings. I've reverted that change and it should build now. Seems it only wants to build against gtk-sharp-2. Figures given the default for this is still gtk2.

Rhinoceros commented on 2016-06-30 23:05

New PKGBUILD doesn't build for me.

make[4]: Entering directory '/tmp/libappindicator/src/libappindicator-12.10.0/bindings/mono'
sed '/signals\[X_NEW_LABEL\] /,+6d' ../../src/app-indicator.c > app-indicator.c
no app-indicator.sources.xml
make[4]: no: Command not found
make[4]: *** [Makefile:793: libappindicator-api.raw] Error 127
make[4]: Leaving directory '/tmp/libappindicator/src/libappindicator-12.10.0/bindings/mono'
make[3]: *** [Makefile:481: all-recursive] Error 1
make[3]: Leaving directory '/tmp/libappindicator/src/libappindicator-12.10.0/bindings/mono'
make[2]: *** [Makefile:353: all-recursive] Error 1
make[2]: Leaving directory '/tmp/libappindicator/src/libappindicator-12.10.0/bindings'
make[1]: *** [Makefile:409: all-recursive] Error 1
make[1]: Leaving directory '/tmp/libappindicator/src/libappindicator-12.10.0'
make: *** [Makefile:339: all] Error 2
==> ERROR: A failure occurred in build().

WoefulDerelict commented on 2016-06-30 21:42

macieks: Thanks very much for pointing out the issue. This was entirely my fault as I'd adopted a patch from lib32 that removed the python bindings. I'm sure there was a reason for it at the time; however, I can't manage to recall it or raise some record so I doubt any excessive modifications are necessary. I've dropped that patch and the python bindings have returned.

I've also fiddled with the mono bindings and the sharp sub-package's dependencies. It should now be building properly against GTK3's mono bindings and as such the dependencies have been modified to reflect that. This should be much cleaner for the average user and hopefully behaves more consistently.

macieks commented on 2016-06-30 10:25

Problem mentioned by @begemot69 is caused by missing python binding for libappindicator.

The root cause of the problem is the python module not included in any of the libappindicator packages. Probably it stopped building?

To fix that libappindicator-gtk could be changed to create python2-appindicator package. PKGBUILD including this fix can be found here:

dflt commented on 2016-06-10 21:30

WoefulDerelict commented on 2016-06-02 04:42

dflt: I can't reproduce your error in any of my test environments and there isn't enough in your output snippit to really tell me what was going on or why it failed. If you could capture the entire build and link it via a text host like gist or a paste bin it would aid in diagnosing the issue.

begemot69: I can barely parse your comment. You have not provided enough information to facilitate a conversation or any kind of diagnosis. I'm not familiar with the application you're using or the error you are experiencing.

All comments