This sounds like a bug.

I am hitting a similar issue

Outputs:

> swaymsg -t get_outputs
Output eDP-1 'Unknown 0x243D 0x00000000'
  Current mode: 1920x1080 @ 60.030998 Hz
  Position: 1920,0
  Scale factor: 1.000000
  Scale filter: nearest
  Subpixel hinting: unknown
  Transform: normal
  Workspace: 1
  Max render time: off
  Adaptive sync: disabled
  Available modes:
    1920x1080 @ 60.030998 Hz

Output DP-4 'Unknown 27HC1R P 0x00000101' (focused)
  Current mode: 1920x1080 @ 144.001007 Hz
  Position: 0,0
  Scale factor: 1.000000
  Scale filter: nearest
  Subpixel hinting: unknown
  Transform: normal
  Workspace: 2
  Max render time: off
  Adaptive sync: disabled
  Available modes:
...
    1920x1080 @ 144.001007 Hz

Output DP-3 'Goldstar Company Ltd LG HDR 4K 0x00008594' (inactive)
  Available modes:
 ...
    3840x2160 @ 59.997002 Hz

kanshi logs:

> kanshi
applying profile 'dock'
applying profile output 'eDP-1' on connected head 'eDP-1'
applying profile output 'DP-3' on connected head 'DP-3'
applying profile output 'DP-4' on connected head 'DP-4'
failed to apply configuration for profile 'dock'

My config file:

> cat ~/.config/kanshi/config
profile dock {
 output eDP-1 enable mode 1920x1080 position 3840,0
 output DP-3 enable mode 3840x2160 position 0,0
 output DP-4 enable mode 1920x1080 position 3840,0
}

The DP-3 monitor is attached

I have the exact same issue as @rohan47 , this is the kanshi output I get:

applying profile 'home'
applying profile output 'eDP-1' on connected head 'eDP-1'
applying profile output 'DP-5' on connected head 'DP-5'
applying profile output 'DP-7' on connected head 'DP-7'
failed to apply configuration for profile 'home'

I have a similar bug with the monitors that are connected through a Thinkpad x250 docking station.

Interestingly, Kanshi recognizes my profile if I start it having the monitors connected, but fails to do so if I reconnect monitors (by undocking and docking back my monitor) while Kanshi is running.

My config file is,

profile builtin {
  output eDP-1 enable position 0,0 scale 1
}
profile docked {
  output "Goldstar Company Ltd LG IPS FULLHD 604NTDV33634" position 0,0
  output "Goldstar Company Ltd LG IPS FULLHD " position 1920,0
  output eDP-1 disable
}

Here's the demonstration of the bug (arrows are my comments),

$ kanshi -c kanshi-config
applying profile 'docked' ← The laptop is docked atm so Kanshi recognizes my profile
applying profile output 'eDP-1' on connected head 'eDP-1'
applying profile output 'Goldstar Company Ltd LG IPS FULLHD ' on connected head 'DP-3'
applying profile output 'Goldstar Company Ltd LG IPS FULLHD 604NTDV33634' on connected head 'DP-4'
running commands for configuration 'docked'
configuration for profile 'docked' applied
no profile matched
applying profile 'builtin' ← Here, I undock my laptop, Kanshi sees it and applies the right profile
applying profile output 'eDP-1' on connected head 'eDP-1'
applying profile 'builtin'
applying profile output 'eDP-1' on connected head 'eDP-1'
running commands for configuration 'builtin'
configuration for profile 'builtin' applied
applying profile 'builtin'
configuration for profile 'builtin' cancelled, retrying
no profile matched ← Here, I dock the monitor back, Kanshi doesn't recognize it, external monitors are off
no profile matched
no profile matched
no profile matched
^C ← I kill Kanshi and restart it without changing the monitors connection
io@arch tmp $ kanshi -c kanshi-config
applying profile 'docked' ← It recognizes the profile correctly
applying profile output 'eDP-1' on connected head 'eDP-1'
applying profile output 'Goldstar Company Ltd LG IPS FULLHD ' on connected head 'DP-3'
applying profile output 'Goldstar Company Ltd LG IPS FULLHD 604NTDV33634' on connected head 'DP-4'




applying profile 'docked'
applying profile output 'eDP-1' on connected head 'eDP-1'
applying profile output 'Goldstar Company Ltd LG IPS FULLHD ' on connected head 'DP-3'
applying profile output 'Goldstar Company Ltd LG IPS FULLHD 604NTDV33634' on connected head 'DP-4'
running commands for configuration 'docked'
configuration for profile 'docked' applied
running commands for configuration 'docked'
configuration for profile 'docked' applied

Is there a way I can run Kanshi with extra debugging info to get more info on what's happening here?

Ivan

There are multiple unrelated issues described here.

• OP hits an issue resulting in no profile being matches.
• rohan47 hits an issue resulting in a profile being matched, but fails to apply. Please open a separate issue.
• Ivan hits an issue where no profile is matched because make/model/serial is used and kanshi mixes up things. They sent a patch to fix it (thanks!). OP isn't using make/model/serial so sounds like a separate issue.

I also used to experience rohan47's issue with profile failing to apply. But I can't reproduce it from sometime around commit 5267594b.

Maybe #70 is the right issue for profile failing to apply.