On Tue, Jan 10, 2017 at 12:39:40PM -0000, Jean-Baptiste Lallement wrote:
> I've tested dbus 1.10.6-1ubuntu3.2 on frieza xenial/arm64 and it renders
> the device completely unusable (cf bug 1654241)
>
> Marking as verification-failed.
That's fair, but note that this is *not* a bug with this SRU. Something
is starting a dbus-daemon and setting its address in the environment. It
then is terminated and not available in the session. This SRU makes dbus
not start a new bus if the environment is saying there already is one.
Yes, it should be held out of -updates until that is fixed. But the fix
is elsewhere.
On Tue, Jan 10, 2017 at 12:39:40PM -0000, Jean-Baptiste Lallement wrote: failed.
> I've tested dbus 1.10.6-1ubuntu3.2 on frieza xenial/arm64 and it renders
> the device completely unusable (cf bug 1654241)
>
> Marking as verification-
That's fair, but note that this is *not* a bug with this SRU. Something
is starting a dbus-daemon and setting its address in the environment. It
then is terminated and not available in the session. This SRU makes dbus
not start a new bus if the environment is saying there already is one.
Yes, it should be held out of -updates until that is fixed. But the fix
is elsewhere.
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]