I upgraded another machine (my laptop) to login 4.1.5-1, which was enough to
reproduce the bug.

Is everyone who upgrades seeing this, or is it specific to a particular
configuration?




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to