Skip to main content ↑ ↓
Topic: windowmaker and lxdm failure (Read 867 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

windowmaker and lxdm failure

On this last update this morning there was an update of imagemagic.   That usually forces me to recompile windowmaker with is the main desktop I like to use and which is in the arch AUR.    This also happened earlier in the week. 

When I tried to compile the AUR earlier in the week, it stubbornly refused to recognize the new Imagemagik libraries.  I finally downloaded the original source from http://www.windowmaker.org and compiled it by hand from that source and it worked.

That was last week.

This morning with yet another imagemagic update, wmaker predictably failed.  So I reopened the source and recompiled again with autoconf and it compiled.  I thought it was working but it wouldn't start from lxdm.  I could only start it with startx (which I haven't done in many years). 

the version that came up with startx of wmaker seemed to have different settings.  My xterms defaulted to white instead of reverse.  Something was very different.

So, a number of moving parts are now in play.  First. I suppose startx  starts X up (like with xinit).  I am not sure what lxdm is doing.  Maybe it is using wayland?

I couldn't see anything in the logs that was stopping wmaker from starting up or to bomb.  I just saw normal pam entries which I didn't really understand.

I finally use yay again this morning and installed wmaker from the AUR and now it is working from lxdm with the normal configuration.  It is an odd thing.

I don't know why when Imagemagic is updated that windowmaker can't be updated as a dependency.  It seems to be a sticking point.  There are dozens of dependencies to windowmaker but this one seems to get it most often.

How do I debug all of this?  Scanning /var/log seemed to not give any useful hints.

Is lxdm using X or is it using wayland?

How does lxdm change the environment for windowmaker?

Re: windowmaker and lxdm failure

Reply #1 –
Quote from: mrbrklyn – on
I don't know why when Imagemagic is updated that windowmaker can't be updated as a dependency.  It seems to be a sticking point. 
Because Imagemagic is a dependency of windowmaker not the other way round.
It's expected to have to rebuild AUR packages when their dependencies get updated.
Normal  repo packages are rebuilt by their maintainers when required and distributed as binaries. Aur packages are only distributed as source (PKGBUILD's) and the user has to rebuild them when required.

If you look at  https://github.com/ImageMagick/ImageMagick/releases you can see what happened.
7.1.1-40 was released 2 weeks ago. It broke the ABI and 7.1.1-41 was released 4 days ago fixing that.
Quote
7.1.1-41 Latest
What's Changed

    Fix compiler identification with Clang on Darwin by @Un1q32 in #7773
    revert map changes breaking ABI by @remicollet in #7768
https://github.com/ImageMagick/ImageMagick/pull/7768/commits/8de691a078d95e1f2b75ac2fe940fd2478d6b99f

Installing anything into the system with
Code: [Select]
./configure
make install
or similar is a bad idea but you may have gotten away with it ?

Re: windowmaker and lxdm failure

Reply #2 –
why would it fail to work with lxdm?

Re: windowmaker and lxdm failure

Reply #3 –
While it doesn't answer why it works differently, if you haven't done something similar already, installing the "rebuild-detector" package from the Arch extra repo might help point out when it needs a rebuild. There are some other packages with similar functionality in the AUR as well.
Does Window maker even support Wayland? Perhaps there might be some settings files in your homedir under .dirs that aren't getting read, you might be able to add something to your xinitrc or bashrc, don't know what though.

Re: windowmaker and lxdm failure

Reply #4 –
As far as I know, imagemagick can be disabled during compilation.

Code: [Select]
./configure --disable-magick

This disable ImageMagick's MagickWand support in WRaster, used to support for image formats.

Re: windowmaker and lxdm failure

Reply #5 –
Quote from: Ogis – on
As far as I know, imagemagick can be disabled during compilation.

Code: [Select]
./configure --disable-magick

This disable ImageMagick's MagickWand support in WRaster, used to support for image formats.


I don't think turning off imagemagick support is a good idea.  It is a basic tool kit for raster images.

Darn if I understand why it behaves so differently from startx to being launched by the xdm analog.

Re: windowmaker and lxdm failure

Reply #6 –
Quote from: mrbrklyn – on
Darn if I understand why it behaves so differently from startx to being launched by the xdm analog.

"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "
 

Re: windowmaker and lxdm failure

Reply #7 –
It looks cool.  What are you showing me exactly?

Re: windowmaker and lxdm failure

Reply #8 –
Quote from: mrbrklyn – on
It looks cool.  What are you showing me exactly?

There are no problems with lxdm and windowmaker.
So I can't really understand the thread.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: windowmaker and lxdm failure

Reply #9 –
Quote from: lq – on
Quote from: mrbrklyn – on
It looks cool.  What are you showing me exactly?

There are no problems with lxdm and windowmaker.
So I can't really understand the thread.

Well, I find troubles  on updates.    It has to do with the Imagemagic libraries. 

So I reopened the source and recompiled again with autoconf and it compiled.  I thought it was working but it wouldn't start from lxdm.  I could only start it with startx .


The window maker configuration that came up with startx seemed to have different settings.  My xterms defaulted to white instead of reverse.  Something was very different.

So, a number of moving parts are now in play.  First. I suppose startx  starts X up (like with xinit).  I am not sure what lxdm is doing.  Maybe it is using wayland?

I couldn't see anything in the logs that was stopping wmaker from starting up or to bomb.  I just saw normal pam entries which I didn't really understand.

How do I debug all of this?  Scanning /var/log seemed to not give any useful hints.

Is lxdm using X or is it using wayland?

How does lxdm change the environment for windowmaker?

Re: windowmaker and lxdm failure

Reply #11 –
Quote from: mrbrklyn – on
How does lxdm change the environment for windowmaker?

It would be interesting to know what you have written in your ~/.xinitrc.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: windowmaker and lxdm failure

Reply #12 –
Quote from: lq – on
Quote from: mrbrklyn – on
How does lxdm change the environment for windowmaker?

It would be interesting to know what you have written in your ~/.xinitrc.
flatbush:[ruben]:~$ cat ~/.xinitrc
# Window Maker default X session startup script

PATH="$PATH:/usr/bin"

# If you login from xdm, uncomment this to make error messages appear
# in the console window.
#
# tail -f "/home/ruben"/.xsession-errors > /dev/console &

exec wmaker

Re: windowmaker and lxdm failure

Reply #13 –
Quote from: mrbrklyn – on
I am not sure what that little widget is that shows different desktop managers is?  I have never seen in it windowmaker.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "