@@ -1,3 +1,60 @@
1+unity8 (8.00+14.10.20140822-0ubuntu1) utopic; urgency=low
2+
3+ [ Albert Astals ]
4+ * More stable dash overview tests
5+ * PreviewExpandable: "widgets" is a model, not an array
6+
7+ [ Alberto Aguirre ]
8+ * Proxy inactivity timeout values from gsettings into Unity.Screen
9+ (LP: #1230345)
10+
11+ [ Gerry Boland ]
12+ * Cancel open PAM interactions on shutdown - fixes hang on logout on
13+ desktop (LP: #1353041)
14+
15+ [ Diego Sarmentero ]
16+ * Show progress bar on payment button click The payment process has a
17+ small delay before the UI comes up which might cause confusion. Show
18+ a progress bar with unknown value to indicate activity. (LP:
19+ #1354139)
20+
21+ [ Mirco Müller ]
22+ * Made notification qml-test pass again by using Component.onCompleted
23+ instead of onOpacityChanged for the time being.
24+
25+ [ Michael Zanetti ]
26+ * Implement new lockscreen designs
27+
28+ [ Michael Terry ]
29+ * Show the SIM unlock dialog immediately after booting, and enable its
30+ emergency call button.
31+ * Always keep indicator/launcher locked state in sync with whether the
32+ user is authenticated. (LP:# 1357230) (LP: #1357230)
33+ * Allow logging into a desktop or tablet session again, by properly
34+ dismissing old PAM conversations. (LP: #1350878) In a desktop or
35+ tablet, we were accidentally starting two PAM conversations in
36+ sequence on startup. Which is a small bug; it shouldn't normally be
37+ a problem, since each new PAM conversation should kill the old
38+ one.But the way we were killing the old one was subject to a thread
39+ race condition. See, a PAM conversation thread won't exit until all
40+ its prompts are answered. And what we do when we kill a PAM
41+ conversation is to answer all prompts with empty strings.But it's
42+ possible that when we want to kill a PAM conversation that it hasn't
43+ actually gotten to the point of prompting us yet. And when those
44+ prompts do come through, we were treating them as prompts for the
45+ new PAM conversation.So I've changed the PAM conversation logic to
46+ include a pam_handle and compare the handle with the current handle
47+ when being prompted. If it's an old handle, we just dismiss the
48+ prompt with an empty string response.Oh, and I fixed the bug that
49+ caused two prompts on startup in the first place. (But we still need
50+ the above logic anyway, for when you switch users quickly.) (LP:
51+ #1350878)
52+
53+ [ Martin Pitt ]
54+ * Mark for using language packs.
55+
56+ -- Ubuntu daily release <ps-jenkins@lists.canonical.com> Fri, 22 Aug 2014 09:29:41 +0000
57+
158unity8 (8.00+14.10.20140820-0ubuntu1) utopic; urgency=low
259
360 [ CI bot ]