-
I was trying to run notify_rust which throws this error:
The backtrace isn't particularly useful (it never leaves core/main.rs even with full backtrace) and the message could definitely be improved in general. So I had to manually figured it out. The error seems to happen when using a session address while on Unix, ZBus will look at
The files with While my Unix and programming knowledge has lead me to figuring out this symptom of the problem, I have no idea what to do to solve it. Are there any tips or perhaps improvements to zbus that could be made to fix this? I have some suspicions that it might just be a limitation in https://github.com/microsoft/wslg and I seriously debated between here, wslg, and rust_notify for where to report but I decided to start here since I figure at the very least the error when you do try could turn from "No such file or directory" to "WSL is not supported" or something. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The backtrace is just unwinding the underlying I/O error but I think
That's actually a fallback. There really should be
I'd suggest to first make sure you've a session bus running. If it is, I'd check why the relevant env is not set. If the session bus is running, what would be needed in zbus is to make the fallback about socket path guessing work on WSL env. |
Beta Was this translation helpful? Give feedback.
The backtrace is just unwinding the underlying I/O error but I think
notify_rust
can and should present a better error: "Failed to connect to session bus: "That's actually a fallback. There really should be
DBUS_SESSION_BUS_ADDRESS
env set if you have session bus running. If you launch that manually, you may need to set and/or export this env manually as well.