current: windowmaker, updated it to day, it still does not work right...

BW-userx · 02-24-2018, 08:05 AM

I looked at the logs
http://www.slackware.com/changelog/c...php?cpu=x86_64

Mon Mar 20 20:43:14 UTC 2017
xap/windowmaker-0.95.8-x86_64-1.txz: Upgraded.

nothing for what just took place a minute ago, I seen window maker in the upgrade-all listings. thought it was going to fix the WPrefs.app where it is comming up empty in the launcher, and the themes and such are still empty. I know they do updates and tra la la this is current, but I'd think that being said, and that Slackware has had WindowMaker on their system for so many years that it would be something that would not get screwed up like this.

Application path and arguments section is empty then clicked on it sends up a about gui window instead.

Code:

bash-4.4$ whereis GNUstep
GNUstep: /usr/lib64/GNUstep
bash-4.4$ ls /usr/lib64/GNUstep/Applications
WPrefs.app

that is where it is at but it is not being put into the little dock app that sits on the window when one is running it.

and themes and styles , It is not even creating a home/user/GNUstep directory.

I know they got a handle on it right, or should I or someone give them a tap on the shoulder to let them know?

EDIT: this is as much as I could get off the screen (tty)

Code:



Installing WindowMaker 0.95.8 for current user...
Could not find global data files
Make sure you have installed Window Maker correctly
/usr/bin/wmaker(check_defaults(main.c:466)): warning: There was an error while creating GNUstep directory, please make sure you have installed Window Maker correctly and run wmaker.inst
wmsetbg: error while loading shared libraries: libMagickWand-6.Q16.so.2: cannot open shared object file: No such file or directory
/usr/bin/wmaker(inotifyWatchConfig(main.c:500)): warning: could not add an inotify watch on path /home/userx/GNUstep/Defaults. Changes to the defaults database will require a restart to take effect.
(II) AIGLX: Suspending AIGLX clients for VT switch
Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
(II) AIGLX: Suspending AIGLX clients for VT switch

keefaz · 02-24-2018, 10:11 AM

Did you run the wmaker.inst script as suggested?

BW-userx · 02-24-2018, 10:24 AM

Quote:

Originally Posted by keefaz

Did you run the wmaker.inst script as suggested?

no, that would be a something that should not be needed to do, as it should work "out of the box" as it does on an initial install of slack (not current). So doing that would deviate from the norm thus providing false information to the, "is it working properly yet" question.

My question was / is should I or someone tap them that are doing this on the shoulder to let them know it is not working properly yet, or do they as they should have a handle on it, so just sit and wait for them to catch up to that part of what they are working on will all of what they are working on.

I only asked this time because I seen it as an update to my upgrade-all command. whereas when I seen it initially being screwed up like this on my install of current, I put that question on hold waiting for an update of windowmaker. having seen it then installing that update, then seeing that it did not fix it, I now pose the question.

BW-userx · 02-24-2018, 11:31 AM

on a thought, that update maybe had MAYBE because I MAY have compiled wirndow maker myself and installed, it so an update showed up for it again ... as I did not find anythign in a resent change log on it, which confused me, that does not change the fact of it being screwed up like it is. that is the same. try it yourself log into windowmaker off startx run level 3 startx that is.

I might do that again I got a little time to play..

imitheos · 02-24-2018, 11:36 AM

Quote:

Originally Posted by BW-userx

I looked at the logs
http://www.slackware.com/changelog/c...php?cpu=x86_64

Mon Mar 20 20:43:14 UTC 2017
xap/windowmaker-0.95.8-x86_64-1.txz: Upgraded.

Code:

wmsetbg: error while loading shared libraries: libMagickWand-6.Q16.so.2: cannot open shared object file: No such file or directory

Do you have replaced any libraries with one from a third-party repository ? When i ldd wmsetbg (and wmaker and every other bin/lib file from windowmaker) i do not get this imagemagick dependency.

Code:

# ls /var/log/packages|grep windowm
windowmaker-0.95.8-x86_64-1

# ldd /usr/bin/wmaker /usr/bin/wmaker.inst /usr/bin/wmsetbg /usr/lib64/libWINGs.so.3.1.0 /usr/lib64/libWMaker.so.1.0.1 /usr/lib64/libWUtil.so.5.0.0 /usr/lib64/libwraster.so.6.0.0 |grep Magic

Edit: You replied before i finished writing. Maybe you compiled windowmaker against an older imagemagick library or something.

BW-userx · 02-24-2018, 11:43 AM

Quote:

Originally Posted by imitheos

Do you have replaced any libraries with one from a third-party repository ? When i ldd wmsetbg (and wmaker and every other bin/lib file from windowmaker) i do not get this imagemagick dependency.

Code:

# ls /var/log/packages|grep windowm
windowmaker-0.95.8-x86_64-1

# ldd /usr/bin/wmaker /usr/bin/wmaker.inst /usr/bin/wmsetbg /usr/lib64/libWINGs.so.3.1.0 /usr/lib64/libWMaker.so.1.0.1 /usr/lib64/libWUtil.so.5.0.0 /usr/lib64/libwraster.so.6.0.0 |grep Magic

Edit: You replied before i finished writing. Maybe you compiled windowmaker against an older imagemagick library or something.

I probably did it was just a quick attack at it to see what I'd see attempt. because as stated I do not want to do too much to it letting the powers that be that are working on this to get around to it to see how that process actually works. Instead of me hacking at current fixing everything I find not working on my side of the things.

though I do have to add that is coming from their version install of windowmaker not the one I might have done.

I know I'll just reinstall update it to current and watch it leave me where it it is at already...

bassmadrigal · 02-24-2018, 01:59 PM

Did you run slackpkg install-new? Because there were 3 new packages added in this last update.

BW-userx · 02-24-2018, 02:35 PM

Quote:

Originally Posted by bassmadrigal

Did you run slackpkg install-new? Because there were 3 new packages added in this last update.

got it had some time to i just reinstalled it fresh and did the two step turn around touch your toes update .. its copacetic now. thanks,,... but still does not answer the question, if one finds someting screwy on current other than ponce stuff just hold on and wait or try to tell someone that is part of that team to let them know so they can look into it.

Didier Spaier · 02-24-2018, 03:03 PM

Quote:

Originally Posted by BW-userx

but still does not answer the question, if one finds someting screwy on current other than ponce stuff just hold on and wait or try to tell someone that is part of that team to let them know so they can look into it.

First insure that you can reproduce the issue on a freshly installed Slackware-current, or at least on one regularly updated following the ChangeLog, without any modification or customization but with all additions, upgrade and removal that it lists applied.

If and only if you can, then post the issue in this forum.

bassmadrigal · 02-24-2018, 03:18 PM

Quote:

Originally Posted by BW-userx

got it had some time to i just reinstalled it

Did you just reinstall windowmaker or Slackware as a whole? If it was the latter, you would learn a lot more trying to solve your problems without reinstalling...

allend · 02-24-2018, 08:49 PM

Quote:

thought it was going to fix the WPrefs.app where it is comming up empty in the launcher

Your problem here is the format of ~/GNUstep/Defaults/WMRootmenu. You cannot use the WPrefs.app with the menu in plain text file format.
From ~/GNUstep/Library/WindowMaker/README

Quote:

The plmenu file is the same menu, but in the property list format.
This menu can be edited with WPrefs.app, but since WPrefs.app does not
support XIM, it will not allow you to make menus in languages such as
Japanese.

To use the menu in the property list format (plmenu), just replace the
~/GNUstep/Defaults/WMRootMenu with it.

i.e. copy ~/GNUstep/Library/WindowMaker/plmenu to ~/GNUstep/Defaults/WMRootmenu

PS - I sometimes wish that Slackware shipped with some saner defaults for WindowMaker, but as PV has said in the past, isn't configuration part of the fun?

BW-userx · 02-24-2018, 09:22 PM

Quote:

Originally Posted by allend

Your problem here is the format of ~/GNUstep/Defaults/WMRootmenu. You cannot use the WPrefs.app with the menu in plain text file format.
From ~/GNUstep/Library/WindowMaker/README

i.e. copy ~/GNUstep/Library/WindowMaker/plmenu to ~/GNUstep/Defaults/WMRootmenu

PS - I sometimes wish that Slackware shipped with some saner defaults for WindowMaker, but as PV has said in the past, isn't configuration part of the fun?

it was having the default menu that came with it. I've always used that menu Named WMRootMenu. even when using menu maker to update it. it has been my recent experience that when compiling from source to use the

''--with-gnustepdir='

to direct the dockapp that holds the path to WPref.app in order to gain access to their setup menu box that has nothing to do with the menu itself other than when one is assinigng the keyboard short cuts to the menu.

whereas in menumaker's WindowMaker.py it has to match the dir the menus are being held in in order to give both directories that the themes and styles and such are being kept. the system side and user side.

If the the path for the GNUstep is not the same as the default or set wrong somehow then the WPrefs.app path is not adjusted to match a default setting in that WMDock app so it comes up empty because the path directive is screwed up at compiling time.

this is part of my WMRootMenu in (reg) Slack as I am not in current at the moment.

Code:

 ("WindowMaker",
        ("Workspaces", WORKSPACE_MENU),
        ("Appearance",
            ("Themes", OPEN_MENU, "-noext /usr/share/WindowMaker/Themes $HOME/GNUstep/Library/WindowMaker/Themes WITH setstyle"),
            ("Styles", OPEN_MENU, "-noext /usr/share/WindowMaker/Styles $HOME/GNUstep/Library/WindowMaker/Styles WITH setstyle"),
            ("Icons", OPEN_MENU, "-noext /usr/share/WindowMaker/IconSets $HOME/GNUstep/Library/WindowMaker/IconSets WITH seticons"),
            ("Backgrounds", OPEN_MENU, "-noext /usr/share/WindowMaker/Backgrounds $HOME/GNUstep/Library/WindowMaker/Backgrounds WITH wmsetbg -u -t"),
            ("Save Theme", SHEXEC, "getstyle -t $HOME/GNUstep/Library/WindowMaker/Themes/\"%a(Theme name)\""),
            ("Save IconSet", SHEXEC, "geticonset -t $HOME/GNUstep/Library/WindowMaker/IconSets/\"%a(IconSet name)\"")
        ),
        ("Run...", SHEXEC, "%a(Run,Type command to run:)"),
        ("Save session", SAVE_SESSION),
        ("Clear session", CLEAR_SESSION),
        ("Restart", RESTART),
        ("Exit", EXIT)
    )
)

this is two seperate issues you are speaking of, you are taking about the menu and this is the placement of where the WPref.app is kept. they have to work in tandome to some extent but this is not about the RootMenu per se' which requires

Code:

place the path for the menu in ~/GNUstep/Defaults/WMRootMenu, enclosed
in double quotes ("). Ex: "~/GNUstep/Library/WindowMaker/menu"

to be placed INside of the WMRootMenu it was about the miss placement of the path to the WPref.app

allend · 02-24-2018, 10:13 PM

Maybe I am getting the wrong end of the stick here.
For comparison, this is what I have in my WMRootmenu for the Appearance entry, from where I can start the WPrefs.app.

Code:

  (
    Appearance,
    (
      "Preferences Utility",
      EXEC,
      "/usr/lib64/GNUstep/Applications/WPrefs.app/WPrefs"
    )
  ),

BW-userx · 02-24-2018, 10:44 PM

Quote:

Originally Posted by allend

Maybe I am getting the wrong end of the stick here.
For comparison, this is what I have in my WMRootmenu for the Appearance entry, from where I can start the WPrefs.app.

Code:

  (
    Appearance,
    (
      "Preferences Utility",
      EXEC,
      "/usr/lib64/GNUstep/Applications/WPrefs.app/WPrefs"
    )
  ),

I've never dug into that, I've always right clicked on that dock app select 'settings...' then edited it in there. It would be blank so I'd search for it in the terminal to where it is located then add it.

allend · 02-25-2018, 06:39 AM

For my dockapp, the command is the same.
For the WMRootmenu, you could look at the output from 'wmgenmenu'.