[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Changed in: unity/7.2 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
This bug was fixed in the package unity - 7.2.4+14.04.20150316-0ubuntu1 --- unity (7.2.4+14.04.20150316-0ubuntu1) trusty; urgency=medium [ Andrea Azzarone ] * Avoid running potentially dangerous code paths when the screen is locked. (LP: #1410582) * Ungrab the shoutdown dialog as soon as possible. (LP: #1398287) * Use COMPIZ_METAKEY where needed. (LP: #1363534) * disabled Pointer Barriers during lockscreen (LP: #1401911) * disabled markup for VolumeLauncherIcon quicklist menu items (LP: #1413411) * enable Dash, Hud, and session dialogs over full screen window (LP: #1159249, #860970, #1413773, #1404486) * made unity unlockable if user is in nopsswdlogin group (LP: #1413790) * skipped the animation of BGHash on startup to prevent unwanted fade- in (LP: #1241757) [ Luke Yelavich ] * extended accessible exploration of the Dash dynamic content (LP: #1066157) [ Marco Trevisan (Treviño) ] * MenuManager: make sure menus are always shown when mouse is over them or when the always-show-menus option is on (LP: #955193, #1390562, #1374942, #1312137) * PanelService: use gdbus to notfy upstart of service start/stop (LP: #1302955) -- CI Train Bot ci-train-...@canonical.com Mon, 16 Mar 2015 17:30:35 + ** Changed in: unity (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
Hello Jennifer, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Changed in: unity (Ubuntu Trusty)
Status: New = In Progress
** Changed in: unity (Ubuntu)
Importance: Undecided = Critical
** Changed in: unity (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: unity (Ubuntu Trusty)
Assignee: (unassigned) = Stephen M. Webb (bregma)
** Description changed:
- I have a user reporting an incidence that trusty unity desktop got
- unlocked on its own:
+ [Impact]
- 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!
+ Certain code paths may cause the Unity lockscreen to crash, which can
+ allow the screen to be unlocked without a password entry.
- 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:
+ [Test Case]
-
---
- --- stack trace ---
- #0 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
- No symbol table info available.
- #1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
- No symbol table info available.
- #2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
- No symbol table info available.
- #3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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
-
-
+ Unfortunately this bug only appears under certain race conditions and is
+ not reliably reproduce able.
- 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
- --
+ [Regression Potential]
- His system is Ubuntu trusty 14.04.1 LTS. Unity installed
- 7.2.3+14.04.20140826-0ubuntu1.0.1 .
+ 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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
Fix Released
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Status in unity source package in Trusty:
In Progress
Bug description:
[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
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Branch linked: lp:~bregma/unity/lp-1410582-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
Fix Released
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
Fix Released
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Changed in: unity
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
Fix Released
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
@Andrea, considering that this is a potential security bug where a
ubuntu desktop gets unlocked on its own, wouldn't it be recommended to
issue an update asap instead of with the next SRU?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Changed in: unity
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
In Progress
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
In Progress
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Description changed:
-I have a user reporting an incidence that trusty unity desktop got
+ 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!
+ 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
+ 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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
+ value = optimized out
#4 0x7ff17f401c7b 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
+ value = optimized out
+ fixup = optimized out
+ path = 0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen
#5 0x7ff17f402e7a 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
+ 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
:
+ 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
+ His system is Ubuntu trusty 14.04.1 LTS. Unity installed
7.2.3+14.04.20140826-0ubuntu1.0.1 .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
In Progress
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
In Progress
Bug 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
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
This bug was fixed in the package unity - 7.3.1+15.04.20150115-0ubuntu1
---
unity (7.3.1+15.04.20150115-0ubuntu1) vivid; urgency=low
[ Ubuntu daily release ]
* New rebuild forced
[ Andrea Azzarone ]
* Disable Pointer Barriers during lockscreen. (LP: #1401911)
* Use std::weak_ptr to avoid referencing an invalid barrier. (LP:
#1238063)
* Enable dash and hud if there is a fullscreen window. (LP: #1159249,
#860970)
* Show session dialog over fullscreen windows. (LP: #1404486)
* Avoid running pontentially dangerous code paths when the screen is
locked. (LP: #1410582)
[ Marco Trevisan (Treviño) ]
* MenuManager: make sure menus are always shown when mouse is over
them or when the always-show-menus option is on (LP: #955193,
#1390562, #1374942, #1312137)
-- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 15 Jan 2015
15:03:31 +
** Changed in: unity (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
In Progress
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
Greatly appreciate your work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
In Progress
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
@Jennifer a fix has been released in Ubuntu 15.04. You need to wait the
next SRU (few months likely) to get this fix in 14.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
In Progress
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug 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 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 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 0x7ff17f401c7b 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 0x7ff17f402e7a 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 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
