| 2015-01-13 23:47:54 |
Jennifer Pan |
bug |
|
|
added bug |
| 2015-01-14 00:12:30 |
Andrea Azzarone |
branch linked |
|
lp:~andyrock/unity/fix-1410582 |
|
| 2015-01-14 02:04:19 |
Andrea Azzarone |
unity: status |
New |
Triaged |
|
| 2015-01-14 02:04:22 |
Andrea Azzarone |
unity (Ubuntu): status |
New |
In Progress |
|
| 2015-01-14 02:04:25 |
Andrea Azzarone |
unity: status |
Triaged |
In Progress |
|
| 2015-01-14 02:04:31 |
Andrea Azzarone |
unity: importance |
Undecided |
High |
|
| 2015-01-14 02:04:33 |
Andrea Azzarone |
unity: assignee |
|
Andrea Azzarone (andyrock) |
|
| 2015-01-14 02:04:35 |
Andrea Azzarone |
unity: importance |
High |
Critical |
|
| 2015-01-14 02:04:38 |
Andrea Azzarone |
unity (Ubuntu): assignee |
|
Andrea Azzarone (andyrock) |
|
| 2015-01-14 02:58:41 |
Andrea Azzarone |
unity: milestone |
|
7.3.1 |
|
| 2015-01-14 09:39:14 |
Marco Trevisan (Treviño) |
unity/7.2: importance |
Undecided |
Critical |
|
| 2015-01-14 09:39:14 |
Marco Trevisan (Treviño) |
unity/7.2: status |
New |
In Progress |
|
| 2015-01-14 09:39:14 |
Marco Trevisan (Treviño) |
unity/7.2: milestone |
|
7.2.4 |
|
| 2015-01-14 09:39:14 |
Marco Trevisan (Treviño) |
unity/7.2: assignee |
|
Andrea Azzarone (andyrock) |
|
| 2015-01-15 15:46:05 |
Jennifer Pan |
information type |
Private Security |
Public Security |
|
| 2015-01-15 15:56:36 |
Margarita Manterola |
description |
I have a user reporting an incidence that trusty unity desktop got unlocked on its own:
"Well, I didn't unlock/lock the system before the auto-unlock that morning.
What I mean is that, on that morning after coming to my desk, I started
working on my Mac and just press the space bar on my desktop to get the
monitors woken up. The monitors came up with the locked screen and then
after a while it got unlocked to my surprise!"
There was compiz crash file on his system at that time. However, I don't have the right debug symbols to which file (or function) it crashed into. Here is the top part of the stack trace when I ran apport-retrace -s on his crash file:
---------------------------------------------------------------------------------------------------------------
--- stack trace ---
#0 0x00007ff17ed06608 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x00007ff17ed06cf3 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x00007ff17ed04e2d in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x00007ff17f3fdd02 in g_settings_backend_read (backend=<optimized out>, key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", expected_type=0x7ff1877135a0 <g_variant_type_info_basic_chars>, default_value=default_value@entry=0) at /build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
value = <optimized out>
#4 0x00007ff17f401c7b in g_settings_read_from_backend (settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
value = <optimized out>
fixup = <optimized out>
path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
#5 0x00007ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, key=0x2087618 "disable-lock-screen") at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c "disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length = 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 <g_variant_type_info_basic_chars>, minimum = 0x0, maximum = 0x0, default_value = 0xb9c5b30, ref_count = 0}
value = <optimized out>
__FUNCTION__ = "g_settings_get_value"
-----------------------------------------------------------------------------------------------------------------
The top part of the trash file when viewed in TextEdit has the information :
-------------------------------------------------
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Dec 12 10:16:52 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1405349348
ProcCmdline: compiz
--------------------------------------------------
His system is Ubuntu trusty 14.04.1 LTS. Unity installed 7.2.3+14.04.20140826-0ubuntu1.0.1 . |
I have a user reporting an incidence that trusty unity desktop got unlocked on its own:
"In the morning, after coming to my desk, I just pressed the space bar on my desktop to get the monitors woken up. The monitors came up with the locked screen and then after a while it got unlocked to my surprise!"
There was compiz crash file on his system at that time. However, I don't have the right debug symbols to which file (or function) it crashed into. Here is the top part of the stack trace when I ran apport-retrace -s on his crash file:
---------------------------------------------------------------------------------------------------------------
--- stack trace ---
#0 0x00007ff17ed06608 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x00007ff17ed06cf3 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x00007ff17ed04e2d in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x00007ff17f3fdd02 in g_settings_backend_read (backend=<optimized out>, key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", expected_type=0x7ff1877135a0 <g_variant_type_info_basic_chars>, default_value=default_value@entry=0) at /build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
value = <optimized out>
#4 0x00007ff17f401c7b in g_settings_read_from_backend (settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
value = <optimized out>
fixup = <optimized out>
path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
#5 0x00007ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, key=0x2087618 "disable-lock-screen") at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c "disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length = 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 <g_variant_type_info_basic_chars>, minimum = 0x0, maximum = 0x0, default_value = 0xb9c5b30, ref_count = 0}
value = <optimized out>
__FUNCTION__ = "g_settings_get_value"
-----------------------------------------------------------------------------------------------------------------
The top part of the trash file when viewed in TextEdit has the information :
-------------------------------------------------
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Dec 12 10:16:52 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1405349348
ProcCmdline: compiz
--------------------------------------------------
His system is Ubuntu trusty 14.04.1 LTS. Unity installed 7.2.3+14.04.20140826-0ubuntu1.0.1 . |
|
| 2015-01-15 20:38:27 |
Launchpad Janitor |
unity (Ubuntu): status |
In Progress |
Fix Released |
|
| 2015-01-17 21:39:52 |
Andrea Azzarone |
unity: status |
In Progress |
Fix Committed |
|
| 2015-02-11 16:12:32 |
Stephen M. Webb |
unity: status |
Fix Committed |
Fix Released |
|
| 2015-03-11 02:47:54 |
Stephen M. Webb |
unity/7.2: milestone |
7.2.4 |
7.2.5 |
|
| 2015-03-11 18:42:20 |
Launchpad Janitor |
branch linked |
|
lp:~bregma/unity/lp-1410582-trusty |
|
| 2015-03-17 17:40:22 |
Stephen M. Webb |
unity (Ubuntu Trusty): status |
New |
In Progress |
|
| 2015-03-17 17:40:29 |
Stephen M. Webb |
unity (Ubuntu): importance |
Undecided |
Critical |
|
| 2015-03-17 17:40:33 |
Stephen M. Webb |
unity (Ubuntu Trusty): importance |
Undecided |
Critical |
|
| 2015-03-17 17:40:41 |
Stephen M. Webb |
unity (Ubuntu Trusty): assignee |
|
Stephen M. Webb (bregma) |
|
| 2015-03-17 17:40:45 |
Stephen M. Webb |
description |
I have a user reporting an incidence that trusty unity desktop got unlocked on its own:
"In the morning, after coming to my desk, I just pressed the space bar on my desktop to get the monitors woken up. The monitors came up with the locked screen and then after a while it got unlocked to my surprise!"
There was compiz crash file on his system at that time. However, I don't have the right debug symbols to which file (or function) it crashed into. Here is the top part of the stack trace when I ran apport-retrace -s on his crash file:
---------------------------------------------------------------------------------------------------------------
--- stack trace ---
#0 0x00007ff17ed06608 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x00007ff17ed06cf3 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x00007ff17ed04e2d in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x00007ff17f3fdd02 in g_settings_backend_read (backend=<optimized out>, key=key@entry=0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen", expected_type=0x7ff1877135a0 <g_variant_type_info_basic_chars>, default_value=default_value@entry=0) at /build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
value = <optimized out>
#4 0x00007ff17f401c7b in g_settings_read_from_backend (settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
value = <optimized out>
fixup = <optimized out>
path = 0xab011c0 "/org/gnome/desktop/lockdown/disable-lock-screen"
#5 0x00007ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, key=0x2087618 "disable-lock-screen") at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c "disable-lock-screen", is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length = 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 <g_variant_type_info_basic_chars>, minimum = 0x0, maximum = 0x0, default_value = 0xb9c5b30, ref_count = 0}
value = <optimized out>
__FUNCTION__ = "g_settings_get_value"
-----------------------------------------------------------------------------------------------------------------
The top part of the trash file when viewed in TextEdit has the information :
-------------------------------------------------
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Dec 12 10:16:52 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1405349348
ProcCmdline: compiz
--------------------------------------------------
His system is Ubuntu trusty 14.04.1 LTS. Unity installed 7.2.3+14.04.20140826-0ubuntu1.0.1 . |
[Impact]
Certain code paths may cause the Unity lockscreen to crash, which can allow the screen to be unlocked without a password entry.
[Test Case]
Unfortunately this bug only appears under certain race conditions and is not reliably reproduce able.
[Regression Potential]
The change in the code simply assumes that if a screen is already locked, then it is lockable this avoiding certain operations that are inherently racy. It is possible that this fix does not avoid all possible crash conditions in the lockscreen and there may still be unaccounted-for crashes in the lockscreen.
[Other Info]
This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu "Vivid Vervet" dev release where it has been in testing for some time. |
|
| 2015-04-08 08:38:08 |
Adam Conrad |
unity (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-04-08 08:38:11 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-04-08 08:38:16 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2015-04-08 08:38:22 |
Adam Conrad |
tags |
trusty unity |
trusty unity verification-needed |
|
| 2015-04-14 13:32:18 |
Marco Trevisan (Treviño) |
tags |
trusty unity verification-needed |
trusty unity verification-done |
|
| 2015-04-15 20:04:42 |
Launchpad Janitor |
unity (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-04-15 20:06:16 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-04-16 12:10:26 |
Christopher Townsend |
unity/7.2: status |
In Progress |
Fix Committed |
|
| 2015-04-16 16:19:09 |
Christopher Townsend |
unity/7.2: status |
Fix Committed |
Fix Released |
|
