From: Giovanni Biscuolo <g@xelera.eu>
To: help-guix@gnu.org
Subject: dbus problems running next in my environment (LTSP), also via ssh -Y
Date: Mon, 13 Jan 2020 19:11:51 +0100 [thread overview]
Message-ID: <87ftgj2plk.fsf@roquette.mug.biscuolo.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2729 bytes --]
Hello Guix,
I suspect this is related to my environment and not to next... but don't
understand why and how to fix it
also, probably I have dbus problems for other applications too but I do
not see them because they are not blocking like in next
I installed next 1.4 via guix on two Debian 10 machines:
1. my laptop: next works fine and I'm happy
2. my LTSP app server: it does not work :-S
this is the error I get on my app server:
--8<---------------cut here---------------start------------->8---
giovanni@roquette: next -v
Arguments parsed: (VERBOSE T) and NIL
Next version 1.4.0
<ERROR> [18:38:43] next remote.lisp (ensure-dbus-session fun1 fun65) -
Failed to run (dbus-launch): dbus-launch not found
--8<---------------cut here---------------end--------------->8---
my dbus related processes on this failing machine are:
--8<---------------cut here---------------start------------->8---
giovanni 32087 0.0 0.0 11032 2276 ? S 18:34 0:00 /usr/bin/dbus-launch --exit-with-session --sh-syntax
giovanni 32088 0.0 0.0 8880 2888 ? Ss 18:34 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
giovanni 32124 0.0 0.0 3336 2852 ? S 18:34 0:00 /gnu/store/zjalyyj5v1gygqh613p3y5b3hp7rdxpj-dbus-1.12.12/bin/dbus-daemon --config-file=/gnu/store/rhx1m9ms4a856rayxdb60z776av63f18-at-spi2-core-2.32.1/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
--8<---------------cut here---------------end--------------->8---
and the related DBUS env on the failing machine is:
--8<---------------cut here---------------start------------->8---
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-X4UdsFONq5,guid=8fc98da614e6df5de9ef6fe45e1caa2d
--8<---------------cut here---------------end--------------->8---
on the laptop, where next is running fine, I have this dbus related
processes:
--8<---------------cut here---------------start------------->8---
g 2665 0.0 0.0 9088 4388 ? Ss Jan12 0:22 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
g 2878 0.0 0.0 8884 4160 ? S Jan12 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
--8<---------------cut here---------------end--------------->8---
and this dbus related env:
--8<---------------cut here---------------start------------->8---
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
--8<---------------cut here---------------end--------------->8---
Any hint please?
Thanks, Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
reply other threads:[~2020-01-13 18:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftgj2plk.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).