Trying to run LO from an ssh command line gives the following errors: [ftg@ftgme2 ~]$ soffice LibreOffice(31449)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) [ftg@ftgme2 ~]$ This used to work fine. I first noticed this trying to open LO attachments in Thunderbird running through ssh; you'd get the splashscreen popup, and then it would just silently fail. Reproducible: Steps to Reproduce:
If I issue the command in the message, soffice works.
Keywords: (none) => TriagedAssignee: bugsquad => thierry.vignaud
*** Bug 11615 has been marked as a duplicate of this bug. ***
Source RPM: libreoffice => systemd ?CC: (none) => mageiaAssignee: thierry.vignaud => bugsquadSummary: libreoffice will not run through ssh - dbus error => libreoffice/thunderbird will not run through ssh - dbus error
I've always had issues with running e.g. Firefox on a remote system because it cannot connect to the session bus. This is pretty much a by product of not starting a proper user session (e.g. launching dbus) when logging in to a remote machine. This isn't particularly a recent problem nor something with e.g. systemd, but just a by product of more things using dbus. Longer term, we *can* fix this. It'll be fixed by using systemd user sessions. This means that logging into a text session, be it via SSH or on a tty will start a user session manager in the same way X11 startup sequence starts soemthing equiv to this. Actually pam_systemd does alreayd start a systemd user session for you, but it's not yet matured to the state where it will actually be able to do things like starting dbus for you and then ensuring that's available to applications (by exporting the DBUS_SESSION_BUS_ADDRESS env var to the shell). But long term this is the goal. So not sure what to say for now... This is just the by product of more things wanting dbus.
Ping ?
CC: (none) => doktor5000
Here is a section of my ~/.bash_profile (run when a new session is created) when
CC: (none) => pablo
Here is a section of my ~/.bash_profile (run when a new session is created) when an incoming ssh and graphical session is detected, it looks if a usable dbus is present, if yes exports the DBUS_SESSION_BUS_PID, if not launches a new one. if it seems sufficiently correct/robust it could be put on /etc/profile It works very well for incoming sessions from windows (putty+Xming) # set dbus for remote connections if [ -n "$SSH_CLIENT" -a -n "$DISPLAY" ]; then machine_id=$(LANGUAGE=C hostnamectl|grep 'Machine ID:'| sed 's/^.*: //') x_display=$(echo $DISPLAY|sed 's/^.*:\([0-9]\+\)\(\.[0-9]\+\)*$/\1/') dbus_session_file="$HOME/.dbus/session-bus/${machine_id}-${x_display}" if [ -r "$dbus_session_file" ]; then export $(grep '^DBUS.*=' "$dbus_session_file") # check if PID still running ps $DBUS_SESSION_BUS_PID | tail -1 | grep dbus-daemon >& /dev/null [ "$?" != "0" ] && \ export $(dbus-launch) >& /dev/null else export $(dbus-launch) >& /dev/null fi unset machine_id x_display dbus_session_file fi
Assignee: bugsquad => pkg-bugsSource RPM: systemd ? => (none)
Working now.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Bugs and all majesty of the town are identified for the approval of the turns. The statement of the team and https://topessaybrands.com/review/academized-com-review/ is filled for the approval for the themes. The society’s engaged for the toy light for the approval for the signature for the field for members.
CC: (none) => onizar.tomi0