Comment by ~nathanblair on ~scoopta/wofi
Sorry! Didn't know making that comment would re-open the issue!
REPORTED
RESOLVED INVALIDComment by ~nathanblair on ~scoopta/wofi
Would you consider making a note of this in the README?
sway
andmako
, for instance, make note of having dbus as a runtime dependency. For example,mako
calls out:| If you are using elogind, you might need to manually start a dbus user session: dbus-daemon --session --address=unix:path=$XDG_RUNTIME_DIR/bus
^^ That's how I was able to resolve this issue (coincidentally I was trying to resolve a
mako
issue haha - ended up killing two birds with one stone!)
RESOLVED INVALID
REPORTEDComment by ~nathanblair on ~scoopta/wofi
I've gotten it to work by launching a dbus session (rather than the dbus system, which is enabled and running by default when
up
ping the void linux dbus service). I don't know much about how dbus works so I can't explain why this works or if this was the way it was intended?
Comment by ~nathanblair on ~scoopta/wofi
Still committed on resolving this. I was able to tackle a couple other issues I was having with
wofi
, which I had hoped would eliminate some variables in tracking down why this still isn't working.I did look more into the reddit thread; unfortunately the related post just mentioned his issue was 'related to dbus' and didn't give much resolution.
I have tried tinkering around with dbus, namely disabling it completely, and was unable to affect any desired behavior.
For a little more context, here is what
wofi
relays to me while starting an application indrun
mode, while still showing itself:
(wofi:4422): GLib-GIO-CRITICAL **: 23:26:20.100: g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
I'm unsure if that is at all related to why
wofi
isn't closing after launch? I did clone the repo, and this is with awofi
build from292:71ee23539399
, again on void-linux.I tried taking a look at the source too, but I'm not much of a C programmer and am pretty unfamiliar with the GIO and GTK libraries :(
Comment by ~nathanblair on ~scoopta/wofi
AND I had to symlink /usr/bin/xterm to my actual terminal. Honestly, what's the point of a desktop spec if the spec isn't applicable outside of the gnome desktop environment?
Comment by ~nathanblair on ~scoopta/wofi
The error of the
sh: 1 xterm not found
was because I didn't have thegsettings org.gnome.desktop.default-applications.terminal exec
key set correctly. Gnome is such a PITA :/.
Comment by ~nathanblair on ~scoopta/wofi
I can definitely check into if dbus is interfering. Do you have that reddit thread link?
Comment by ~nathanblair on ~scoopta/wofi
Saw your mention of this thread in the other issue, which I believe may be very closely related. I'm going to try and follow along with that discussion and see how it progresses. If you're not already following it, I'll follow up with the progress I see from it.
Comment by ~nathanblair on ~scoopta/wofi
exact -> exit*
Comment by ~nathanblair on ~scoopta/wofi
Okay, I am mistaken. It does in fact exact on key_submit while in
run
mode. So no issue there, only indrun
mode.This is from the void package, currently
v1.1.1
obtained fromhttps://github.com/void-linux/void-packages/blob/master/srcpkgs/wofi/template
Specifically, the x64-musl built version. The 1.1.2 version hasn't shown up yet in the
xbps
package manager for me yet.