On Thu, 2016-07-07 at 17:55 +0100, Simon McVittie wrote:
> So if you use "xprop -id 4194305" (in this case) to inspect that window,
> you should hopefully find a consistent address and pid attached to it.
From .xsession-errors:
+ eval
On Thu, 07 Jul 2016 at 15:56:15 +0200, Yves-Alexis Perez wrote:
> When running the second time, I get:
>
> corsac 28763 0.0 0.0 43696 388 ?S15:52 0:00
> /usr/bin/dbus- launch --exit-with-session --sh-syntax
>
>
> so no dbus-daemon
On Mon, 2016-07-04 at 17:48 +0100, Simon McVittie wrote:
>
> These indicate that something in your session, whose controlling terminal
> is /dev/pts/0 (?!), used D-Bus and started a dbus-daemon as a side-effect
> ("autolaunching", pid 30347/30348); and in addition, dbus-launch was run
> during
On Mon, 04 Jul 2016 at 21:22:01 +0200, Yves-Alexis Perez wrote:
> One thing I've noticed is that system --user session keeps running after the
> session is ended
It keeps running as long as any processes from your login-session (look
for "session-*.slice" in systemd-cgls output) are still
On lun., 2016-07-04 at 17:48 +0100, Simon McVittie wrote:
> For a session startup less closely resembling a Rube Goldberg machine,
> consider installing dbus-user-session. This makes a semantic change
> to the meaning of "D-Bus session", which is why it is not the default:
> it is meant to be
5 matches
Mail list logo
