Arch Linux

Another thing, when I send a dbus command I always get this message:

method return sender=:1.172 -> dest=:1.301 reply_serial=2

Same here... ./configure seems to be ok, but it's complaining about many undefined dbus_* references and it won't compile.

Hi, unfortunately it don't wont to build on my arch64 :/ This is build log: http://gist.github.com/211318
Regards, Marcin

Now it works (build as a root), thank You sjakub!

This is a bug in fakeroot. Try building this package as root.
Or you could try preloading GL libraries, as described here: http://bugs.archlinux.org/task/12592

There is compile error with kdelibs3, ./configure returns error message like this:
"checking for kde-config... /opt/kde/bin/kde-config
configure: error: /opt/kde/bin/kde-config --prefix outputed the non existant prefix '' for kdelibs.
This means it has been moved since you installed it.
This won't work. Please recompile kdelibs for the new prefix."
I'm not sure about the source (lapsus or kdelibs) of the problem, so I'm posing it here.

Regards, Marcin

Daemon requires qt as well. It doesn't require KDE.

The daemon doesn't requires kde/qt, right? Is it possible to build it without kde/qt?

Even though running `/opt/kde/bin/kde-config --prefix' output "/opt/kde", the compiler kept erroring out with the message:

...
checking for kde-config... /opt/kde/bin/kde-config
configure: error: /opt/kde/bin/kde-config --prefix outputed the non existant prefix '' for kdelibs.
This means it has been moved since you installed it.
This won't work. Please recompile kdelibs for the new prefix.


I had to modify the PKGBUILD to use /opt/kde as its prefix before it would compile:

./configure --without-arts --prefix=/opt/kde

Yes, or Qt4 app ;)
It actually might make more sense... :P

Roger that! ;)
But how about moving that effort to a standalone qt (4?) client so that KDE4 and other WM users can configure lapsus too ;)

There is only KDE3 applet for now.
There might be something for KDE4 as well (when I find time ;) ), but since I don't use Gnome I am not planning to write anything for it. Patches and code is accepted though ;) So if someone decides to contribute there might be gnome client as well.

If acpid is running, multiple programs can connect to acpid to receive ACPI events. If there is no acpid, lapsus tries to use ACPI events file directly. The problem with that file is, that only one program can use it at a time. So if there is any other program already using it (and it's not acpid), lapsusd can't work.
Running acpid IS recommended ;) But it's not necessary, as there might be a setup where only lapsus is listening for such events. I would expect to HAL use that file too (through acpid or directly, just like lapsus does), so the easiest solution is to install acpid and start it before lapsus starts. But it's not a dependency...

Mine refused to start without acpid running, that's why I said that. So if it doesn't depend on acpid, how can one start it without acpid?

Btw, is there anyway to run the client on gnome or kde4?

No, it doesn't depend on acpid. Acpid is needed only if you want more than one program to receive ACPI events, but it's not necessary.

This also depends on acpid/dbus(hal) and they have to be running for lapsusd to start.

Good to know. I have update the package. Thanks!

That fixed it. Thank you.

./configure --without-arts

Can you try modifying PKGBUILD by adding '--without-arts' to see if it helps? I am using kdelibs3 compiled with arts, so it might be different.

I am not able to compile this package successfully due to dependency problems.

checking for mcopidl... not found
configure: error: The important program mcopidl was not found!
Please check whether you installed aRts correctly or use
--without-arts to compile without aRts support (this will remove functionality).

make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed.
Aborting...

I don't have the PKGCONFIG problem either, but a friend of mine do. I just guessed...

Thanks for the fixes gcarrier!

I don't have a problem with pkgconfig, so I
can't really test if it helped, but I guess this change won't brake anything either ;)

As for the stdlib.h problem, it is fixed in 0.0.6 version.

xbrunox, before launching compilation:
export PKG_CONFIG_PATH=/usr/lib/pkgconfig/:$PKG_CONFIG_PATH

Then, you have to edit PKGBUILD to add before ./configure:
sed '25s_.*_&\n\#include \<stdlib.h\>_' -i daemon/sys_ibm.cpp

I'd love to maintain this package.

It includes that version.
The file content:

refix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
system_bus_default_address=unix:path=/var/run/dbus/system_bus_socket
sysconfdir=/etc
session_bus_services_dir=/usr/share/dbus-1/services

Name: dbus
Description: Free desktop message bus
Version: 1.0.2
Libs: -L${libdir} -ldbus-1
Cflags: -I${includedir}/dbus-1.0 -I${libdir}/dbus-1.0/include
----

What is inside "/usr/lib/pkgconfig/dbus-1.pc" file?
It should include something like "Version: 1.0.2"

When i try to build this package, i get this message:
----
checking for DBUS... configure: error: D-BUS >= 0.90 was not found! D-BUS is required to build kdbus.
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build lapsus package.
----
But dbus is running....

Yes, this is due to qt 3/4 names change.
I have corrected the PKGBUILD.

I just tried to build this on my machine, and I got the following error:

./PKGBUILD: line 18: /etc/profile.d/qt.sh: No such file or directory
Error: Makepkg was unable to build lapsus package.

Upon inspection of /etc/profile.d/* I see that there is now qt3.sh instead of qt.sh. I can only assume that this is because of the qt4/qt3 switch-a-roo.

However, if I modifiy that line in PKGBUILD to /etc/profile.d/qt3.sh it seems to build just fine.

lapsusd can run without acpid.
If acpid is not present, or not started, it will print an error message, but it will run without it.

When acpid is running, it provides a socket for different programs to connect and receive acpi events. That's the preferred behaviour, because many programs can receive acpi events at the same time.

When there is no acpid running, the program needs to open /proc/acpi/event file, but only one program can open that file at a time. When Lapsusd can't find acpid's socket it will access /proc/acpi/event file directly, making it unavailable for other programs (unless something else opened that file before).

So, acpid is not real dependency, but using it is preferred. Also, even when you have acpid installed, but not running, it is as if you didn't have it at all.

I think that acpid should be dependency because without it, lapsusd won't start.

Some more fixes.

0.0.5 version

Corrected dbus configuration file, so it treats users in lapsus group properly. I have no idea why it worked and suddenly stopped... maybe some dbus change?

0.0.4 release. Lacks some features of svn version though...