Back to bug 5950

Who When What Removed Added
astrand 2016-08-09 11:01:28 CEST Target Milestone --- NearFuture
astrand 2016-08-09 11:03:48 CEST Blocks 5829
ossman 2016-08-25 10:17:08 CEST Target Milestone NearFuture PoolTodo
derfian 2016-08-25 17:32:19 CEST Blocks 5829
Target Milestone PoolTodo ---
ossman 2016-08-30 10:23:47 CEST Target Milestone --- Future
ossman 2017-02-27 15:52:48 CET Summary many gnome applications fail to start with new systemd many applications fail to start with new systemd (common dbus)
ossman 2017-03-09 15:16:38 CET Blocks 6190
derfian 2018-05-09 13:54:53 CEST Target Milestone LowPrio ---
ossman 2018-05-15 13:58:36 CEST Target Milestone --- PoolTodo
ossman 2018-07-04 15:41:08 CEST Attachment #876 Attachment is obsolete 0 1
ossman 2018-10-02 10:50:07 CEST Assignee derfian ossman
Acceptance Criteria * We should not start a new dbus if $XDG_RUNTIME_DIR/bus exists (even if $DBUS_SESSION_BUS_ADDRESS isn't set)

* dbus or systemd activated user programs should get the correct $DISPLAY and $XAUTHORITY between tl-dbus-launch.sh and tl-run-profile

* dbus or systemd activated user programs started after tl-run-profile should get the same environment as the program started by tl-run-profile (except for below)

* Session specific variables should not be exported ($XDG_SEAT, $XDG_SESSION_ID $XDG_VTNR)

* Variables not matching the filter rules should not be exported (see comment #20)
Target Milestone PoolTodo 4.10.0
ossman 2018-10-02 11:02:24 CEST Acceptance Criteria * We should not start a new dbus if $XDG_RUNTIME_DIR/bus exists (even if $DBUS_SESSION_BUS_ADDRESS isn't set)

* dbus or systemd activated user programs should get the correct $DISPLAY and $XAUTHORITY between tl-dbus-launch.sh and tl-run-profile

* dbus or systemd activated user programs started after tl-run-profile should get the same environment as the program started by tl-run-profile (except for below)

* Session specific variables should not be exported ($XDG_SEAT, $XDG_SESSION_ID $XDG_VTNR)

* Variables not matching the filter rules should not be exported (see comment #20)
* We should not start a new dbus if $XDG_RUNTIME_DIR/bus exists (even if $DBUS_SESSION_BUS_ADDRESS isn't set)

* dbus or systemd activated user programs should get the correct $DISPLAY and $XAUTHORITY between tl-dbus-launch.sh and tl-run-profile

* dbus or systemd activated user programs started after tl-run-profile should get the same environment as the program started by tl-run-profile

* Both profiles and $TLCOMMAND should get this export

* The export should happen even without the help of the desktop environment

* Session specific variables should not be exported ($XDG_SEAT, $XDG_SESSION_ID, $XDG_VTNR)

* Variables not matching the filter rules should not be exported (see comment #20)
ossman 2018-10-02 11:14:25 CEST Acceptance Criteria of the desktop environment

* Session specific variables should not be exported ($XDG_SEAT, $XDG_SESSION_ID, $XDG_VTNR)

* Variables not matching the filter rules should not be exported (see comment #20) * We should not start a new dbus if $XDG_RUNTIME_DIR/bus exists (even if $DBUS_SESSION_BUS_ADDRESS isn't set)

* dbus or systemd activated user programs should get the correct $DISPLAY and $XAUTHORITY between tl-dbus-launch.sh and tl-run-profile

* dbus or systemd activated user programs started after tl-run-profile should get the same environment as the program started by tl-run-profile

* Both profiles and $TLCOMMAND should get this export

* The export should happen even without the help
tl-run-profile should get the same environment as the program started by tl-run-profile

* Both profiles and $TLCOMMAND should get this export

* The export should happen even without the help of the desktop environment

* Session specific variables should not be exported ($XDG_SEAT, $XDG_SESSION_ID, $XDG_VTNR)

* Variables not matching the filter rules should not be exported (see comment #20) * We should not start a new dbus if $XDG_RUNTIME_DIR/bus exists (even if $DBUS_SESSION_BUS_ADDRESS isn't set)

* dbus or systemd activated user programs on older systems (lacking dbus-update-activation-environment) should get the environment from when dbus-launch was run (generally from tl-dbus-launch.sh)

* dbus or systemd activated user programs should get the correct $DISPLAY and $XAUTHORITY between tl-dbus-launch.sh and tl-run-profile

* dbus or systemd activated user programs started after
ossman 2018-10-02 17:09:41 CEST Keywords upstream relnotes
ossman 2018-10-03 15:34:22 CEST Status NEW RESOLVED
Resolution --- FIXED
samuel 2018-10-05 09:24:28 CEST Keywords samuel_tester
CC samuel
samuel 2018-10-15 15:50:29 CEST Status RESOLVED CLOSED

Back to bug 5950