pcdshub / Bug-Reports-and-Requests

Issue Tracking for PCDS Software
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

QStandardPaths: XDG_RUNTIME_DIR not set #40

Closed ZLLentz closed 4 years ago

ZLLentz commented 4 years ago

Bug Report

This prints for me on any ipython session that sets up the qt backend for matplotlib, interfering with the first line of input. It is very annoying, and affects the hutch python sessions.

Expected Behavior

I don't even care if Qt is doing something weird, I don't have to know about it... we want this to not print, either by solving the issue or hiding the warning.

hhslepicka commented 4 years ago

What do you have on:

env | grep XDG

And

export -p | grep XDG

?

ZLLentz commented 4 years ago
zlentz@psbuild-rhel7-01:~$ env | grep XDG
XDG_SESSION_ID=1520
XDG_RUNTIME_DIR=/run/user/14059

zlentz@psbuild-rhel7-01:~$ export -p | grep XDG
declare -x XDG_RUNTIME_DIR="/run/user/14059"
declare -x XDG_SESSION_ID="1520"

It's not clear that I still have this problem, my hutch-python session did not complain at all today...

hhslepicka commented 4 years ago

Probably that got fixed at the OS level.

klauer commented 4 years ago

I'm curious how these variables get injected into the environment (ssh/PAM?) - but it does happen automatically, regardless of X forwarding settings or ssh-agent settings.

Poking around ``` [klauer@psdev02 klauer]$ env |grep XDG XDG_SESSION_ID=30849 XDG_RUNTIME_DIR=/run/user/14884 [klauer@psdev02 klauer]$ loginctl show-user klauer Name=klauer Timestamp=Wed 2020-09-30 11:37:44 PDT TimestampMonotonic=11616235242400 RuntimePath=/run/user/14884 Slice=user-14884.slice Display=30849 State=active IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 Linger=no [klauer@psdev02 klauer]$ loginctl session-status Since: Wed 2020-09-30 11:37:44 PDT; 3min 23s ago Leader: 10848 (sshd) Remote: ... Service: sshd; type tty; class user State: active Unit: session-30849.scope ├─10848 sshd: klauer [priv] ├─10854 sshd: klauer@pts/101 ├─10855 -bash ├─11569 loginctl session-status └─11570 loginctl session-status ```

My best guess here is that your variables got unset somehow, rather than failed to be set initially.

ZLLentz commented 4 years ago

I think I'm going to close this for now, re-open if it pops up again