8000 libaosd Installation Error · Issue #2 · ztuowen/bilicom · GitHub
[go: up one dir, main page]

Skip to content

libaosd Installation Error #2

Closed

Description

@MathLens

The program crashed in a few seconds after pressing shortcut key "n".
Version: 3.4.0
Error message:

Error: write EPIPE
    at errnoException (net.js:901:11)
    at Object.afterWrite (net.js:718:19)

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)

Activity

  1. changed the title [-]JS error after pressing shortcut key "n"[/-] [+]libaosd Installation Error[/+] on Jan 18, 2016
  2. ztuowen commented on Jan 18, 2016

    @ztuowen
    Owner

    This is the symptom of having an "invalid" installation of libaosd.

    When having this error, you most likely compiled it from source either yourself or using some script that does the compilation (such as that from Archlinux's PKGBUILD).

    How do I know if mine is working?

    • If it doesn't give the error as above :), JK
    • If you could run aosd_cat in shell

    How do I fix it

    Check what is actually the problem

    • Remember when you run ./configure --prefix=<somepath>?
      • Is <somepath>/bin in your $PATH?
      • Is <somepath>/lib in your library path?
    • Well it is in the path but how come it does not have aosd_cat in it?
      • Lack of certain libraries can still compile for libaosd
      • When you ./configure there is a list at the end says Configuration
      • At least glib-2.0, Pango-Cairo should be yes

    I got the source of libaosd how do I install

    1. ./autogen.sh
      • This would need automake
    2. ./configure --prefix=<somepath>
      • I prefer <somepath>=/usr/local
    3. make
      • Check dependencies
    4. make install
      • Use sudo if necessary

    Are there any scripts that I can use

    _There is none that I know of_, but a good starting point would be PKGBUILD from AUR

    This is just too complicated for me, and on screen notification isn't that big a deal anyway

    Well, no problem. This program can run without on screen display.

    Fixed: _I've add a feature in 3.4.2 that should automatically disable on screen notification, in case of a buggy libaosd installation._

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0