Request for man page to note use of $XDG_CONFIG_HOME/adwm

[mxmilkiib]

I tried adwm briefly before, but I couldn't wrap XDE around it in the correct way and ended up moving from i3 to give enlightenment another go, but, composited pager thumbnails aside, I'd like to give adwm another try, but I'm currently getting this when trying to start adwm from xinitrc;

           PID: 11366 (adwm)
           UID: 1000 (milk)
           GID: 1000 (milk)
        Signal: 6 (ABRT)
     Timestamp: Mon 2018-04-30 13:56:58 BST (9min ago)
  Command Line: adwm
    Executable: /usr/bin/adwm
 Control Group: /user.slice/user-1000.slice/session-c1.scope
          Unit: session-c1.scope
         Slice: user-1000.slice
       Session: c1
     Owner UID: 1000 (milk)
       Boot ID: 275716c9ddb440b2a4f25f07036e17b5
    Machine ID: 868484078e134905a6dcbc0fdd2079bb
      Hostname: rose.local
       Storage: /var/lib/systemd/coredump/core.adwm.1000.275716c9ddb440b2a4f25f07036e17b5.11366.1525093018000000.lz4
       Message: Process 11366 (adwm) of user 1000 dumped core.

                Stack trace of thread 11366:
                #0  0x00007f0d77fc6efb raise (libc.so.6)
                #1  0x00007f0d77fc82c1 abort (libc.so.6)
                #2  0x00007f0d780099d7 __libc_message (libc.so.6)
                #3  0x00007f0d7800ffda malloc_printerr (libc.so.6)
                #4  0x00007f0d780117fc _int_free (libc.so.6)
                #5  0x00005579a1c4afae freekey (adwm)
                #6  0x00005579a1c4b727 freekey (adwm)
                #7  0x00005579a1c4baeb initkeys (adwm)
                #8  0x00005579a1c0ef48 initialize (adwm)
                #9  0x00005579a1c0802d setup (adwm)
                #10 0x00007f0d77fb39a7 __libc_start_main (libc.so.6)
                #11 0x00005579a1c082ea _start (adwm)

[mxmilkiib]

If I try adwm --help, I get:

usage: adwm [-v] [-f conf]
adwm: E:       adwm.c +1241 : eprint() :        adwm(dumpstack+0x3e) [0x55d460b4093e]
adwm: E:       adwm.c +1241 : eprint() :        adwm(eprint+0xc1) [0x55d460b41141]
adwm: E:       adwm.c +1241 : eprint() :        adwm(main+0x8bf) [0x55d460b3ef9f]
adwm: E:       adwm.c +1241 : eprint() :        /usr/lib/libc.so.6(__libc_start_main+0xe7) [0x7f41149d99a7]
adwm: E:       adwm.c +1241 : eprint() :        adwm(_start+0x2a) [0x55d460b3f2ea]
zsh: abort (core dumped)  adwm --help

Core dump info

           PID: 15617 (adwm)
           UID: 1000 (milk)
           GID: 1000 (milk)
        Signal: 6 (ABRT)
     Timestamp: Mon 2018-04-30 14:13:30 BST (1min 49s ago)
  Command Line: adwm --help
    Executable: /usr/bin/adwm
 Control Group: /user.slice/user-1000.slice/session-c2.scope
          Unit: session-c2.scope
         Slice: user-1000.slice
       Session: c2
     Owner UID: 1000 (milk)
       Boot ID: 275716c9ddb440b2a4f25f07036e17b5
    Machine ID: 868484078e134905a6dcbc0fdd2079bb
      Hostname: rose.local
       Storage: /var/lib/systemd/coredump/core.adwm.1000.275716c9ddb440b2a4f25f07036e17b5.15617.1525094010000000.lz4
       Message: Process 15617 (adwm) of user 1000 dumped core.

                Stack trace of thread 15617:
                #0  0x00007f41149ecefb raise (libc.so.6)
                #1  0x00007f41149ee2c1 abort (libc.so.6)
                #2  0x000055d460b41147 eprint (adwm)
                #3  0x000055d460b3ef9f main (adwm)
                #4  0x00007f41149d99a7 __libc_start_main (libc.so.6)
                #5  0x000055d460b3f2ea _start (adwm)

[bbidulock]

Uhuh. There is no --help option, so it aborted. Aborts dump core.

[mxmilkiib]

Fair enough, ignore the second comment, though I still can't get adwm to start.

[bbidulock]

I think you have a corrupt keysrc file floating around. The key parser is not robust against multiple definitions for the same key (I think it does a double free). If

startx /usr/bin/adwm

doesn't work, try moving $XDG_RUNTIME_DIR/adwm, $HOME/.adwm and $XDG_CONFIG_HOME/adwm aside and try again. Then it should only use the /usr/share/adwm/keysrc file.

[mxmilkiib]

Bingo! Thanks :) The man page didn't mention XDG_CONFIG_HOME/adwm so I was trying exec adwm -f ~/.config/adwm/adwmrc and then just exec adwm.

[bbidulock]

I think you will find it right at the top of adwm-config(5).