Arch Linux User Repository

In ~/.config/twmn/twmn.conf opacity is by default set to 100, but in this way I still get some transparency. I could solve and obtain a solid notification by setting opacity to 99. I couldn't find any documentation on this tool that explains how opacity is treated.

@cyrozap conda -- conda was the reason I was getting that build failure. I'm very sorry for the noise.

@bluehood: I'm not sure why you're having these build issues, but I just tried building it in a fresh archlinux:latest Docker container and it built without any errors, so there's probably something wrong with your build environment.

For the sake of completeness--I don't expect anyone to try building the package this way--this is the Dockerfile I used when doing the test build:

FROM archlinux:latest
RUN pacman -Sy && pacman -S --noconfirm base-devel git
COPY . /package/
WORKDIR /package/
RUN useradd -G wheel build
RUN echo '%wheel ALL=(ALL) NOPASSWD: ALL' >> /etc/sudoers
RUN chown -R build:build .
USER build
RUN makepkg -Ccsi --noconfirm

Tried to build today, got a compilation error:

In file included from widget.h:9:0,
                 from main.cpp:7:
message.h:4:10: fatal error: boost/optional.hpp: No such file or directory
 #include <boost/optional.hpp>
          ^~~~~~~~~~~~~~~~~~~~

Hi, i tried to build the package today and it failed to apply the werrors-fix.patch. I solved the problem by creating a new patch file from inside the git repo. Just a heads up so it can get fixed.

Hi, this package don't compile anymore because all warning are treated as errors. The warning say that some functions are deprecated. Maybe it's work with qt51-base package but, like other, I cannot build it.

Every time I started the service, it would just fail with a core dump. After rebuilding it with some debugging information, I discovered that the error was "could not connect to display" because $DISPLAY was not set. I fixed this by adding Environment=DISPLAY=:0 to the unit file, but I realized in this pursuit that starting it with systemd was kind of a bad idea because it relies on X. Now I just start it with twmnd & in ~/.xinitrc. The author even considers service deprecated.

@chestm007: I personally don't run twmn as a service, but that seems to make sense (and is slightly more secure, anyways). I've pushed the change and bumped the pkgver as well.

is /usr/lib/systemd/service/twmnd.service supposed to be in /usr/lib/systemd/user/twmnd.service? after moving the unit file to there and enabling the unit systemctl --user start twmnd it worked, but as a system service is wasnt recieving notifications.

@cyrozap: Brilliant, thanks!