Package Details: windowmaker 0.95.8-6

Git Clone URL: (read-only)
Package Base: windowmaker
Description: An X11 window manager with a NEXTSTEP look and feel
Upstream URL:
Licenses: GPL, custom
Submitter: Barthalion
Maintainer: bidulock (Refutationalist)
Last Packager: bidulock
Votes: 9
Popularity: 0.529817
First Submitted: 2018-01-07 16:15
Last Updated: 2018-05-28 09:57

Latest Comments

1 2 Next › Last »

bidulock commented on 2018-10-12 20:11

@Beebo, no those are pretty standard warnings for installing to a non-null DESTDIR with libtool.

Beebo commented on 2018-10-12 00:14

I logged the build process and I receive this warning towards the end of the make on the package:

libtool: warning: '../WINGs/' has not been installed in '/usr/lib'

libtool: warning: '/tmp/pakku-nep/windowmaker/src/WindowMaker-0.95.8/WINGs/' has not been installed in '/usr/lib'

libtool: warning: '/tmp/pakku-nep/windowmaker/src/WindowMaker-0.95.8/wrlib/' has not been installed in '/usr/lib'

libtool: warning: '../WINGs/' has not been installed in '/usr/lib'

libtool: warning: '../wrlib/' has not been installed in '/usr/lib'

Could this be the cause of the pixmaps not generating and some WINGS notification windows not having the "x" close graphic displaying properly?

Beebo commented on 2018-10-07 05:01

Is anyone else having trouble getting the app icon pixmaps working in WindowMaker? I'm not sure if it's an upstream bug or a package bug, however the WM doesn't seem to be creating a pixmap cache. Instead the docked apps are being represented as gray boxes when it's not running.

abarbarian commented on 2018-05-31 00:07

@bidulock I updated today with pacaur and windowmaker installed perfectly.I will get around to finding another aur helper. Or I may just try and build the few aur packages I need myself. Thanks for maintaining windowmaker as a aur package. It is a shame that it was dropped from the official package list. ;-)

bidulock commented on 2018-05-29 17:29

Verified that .SRCINFO and PKGBUILD match in version. I don't think AUR would let me upload if they differed. Yaourt is easy to use. I build all my packages in an up-to-date clean chroot to validate dependencies. I have binaries at if you do not want to build it. Also 32-bit at

abarbarian commented on 2018-05-29 09:20

@misanthropist Thanks for the heads up regarding pacaur. It has been working ok for me for quite some time and still seems to do a good job with no problems. I am too busy at the moment to change to another helper program but will do so later in the year. WindowMaker appeared in the updates today but did not build due to,

:: windowmaker package(s) failed to install. :: ensure package version does not mismatch between .SRCINFO and PKGBUILD :: ensure package name has a VCS suffix if this is a devel package

From what I have read it is a minor problem but it takes me some time to digest and understand new information. ;-)

misanthropist commented on 2018-05-27 14:33

@abarbarian In a recent comment on another package, it was said that pacaur is unmaintained, and that using another AUR helper may be advisable.

abarbarian commented on 2018-05-27 09:50

misanthropist thanks for the reply. You are correct X quits gracefully. I tracked back and my fail did occur after the 22nd May updates. I update via pacaur and have never tried to manually build a program. I'll give it a go though but it may take me some time. ;-)

misanthropist commented on 2018-05-26 08:59

@abarbarian Are you sure that X actually fails? Doesn't it just quit gracefully when Window Maker fails? libMagickWand is part of the libmagick package, and it was last updated on May 22. X doesn't depend on it, but Window Maker does. Try rebuilding Window Maker, and you should be fine, but please note that if you're building in a clean root, it needs to have the same library versions as your main system.

abarbarian commented on 2018-05-25 17:27

Hi , I updated my system a couple of days ago and rebooted. Window Maker failed to load as did X. It seems that " " could not be found. I have tried to find information on this file but am hitting a brick wall. I think the problem is caused by a recent imagmagick update but am not 100% sure that is the case.

Thanks in advance if you can help.