On Thu, Dec 23, 2010 at 13:54, Vish <email address hidden> wrote:
> During the UDS session, <
> https://blueprints.launchpad.net/ubuntu/+spec/other-dx-n-indicator-session
> >
> It was mentioned that the fix for the dpkg part landed and all that remains
> is to fix it in the indicator-session. I dont know the commit #. Folks
> present during the session are on vacation, we can probably clarify after
> the holidays..
the reboot_required flag being set should not be the sole condition for the
Session Menu Indicator to turn red.
as long as an apt lock is engaged, the session menu should not signal any
such thing!
that should be the condition, and i don't think we need dpkg to figure that
out for us.
On Thu, Dec 23, 2010 at 13:54, Vish <email address hidden> wrote:
> During the UDS session, < /blueprints. launchpad. net/ubuntu/ +spec/other- dx-n-indicator- session
> https:/
> >
> It was mentioned that the fix for the dpkg part landed and all that remains
> is to fix it in the indicator-session. I dont know the commit #. Folks
> present during the session are on vacation, we can probably clarify after
> the holidays..
the reboot_required flag being set should not be the sole condition for the
Session Menu Indicator to turn red.
as long as an apt lock is engaged, the session menu should not signal any
such thing!
that should be the condition, and i don't think we need dpkg to figure that
out for us.
curious to hear what exactly was fixed in dpkg ..