Lock screen shortcut not working after update of Fedora 16
I recently ran a bunch of updates (I didn't pay attention to which, I was just prompted to update a bunch of stuff), and after running them, the lock-screen shortcut (CTRL-Alt-L) no longer works. I tried modifying the keyboard shortcut in the keyboard system settings to no avail. Does anyone know what the problem might be or how I can find out?
fedora screensaver screen-lock
edited Aug 12 '13 at 22:50
slm♦
251k69529685
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
add a comment |
I recently ran a bunch of updates (I didn't pay attention to which, I was just prompted to update a bunch of stuff), and after running them, the lock-screen shortcut (CTRL-Alt-L) no longer works. I tried modifying the keyboard shortcut in the keyboard system settings to no avail. Does anyone know what the problem might be or how I can find out?
fedora screensaver screen-lock
edited Aug 12 '13 at 22:50
slm♦
251k69529685
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
New updates haven't been produced for Fedora 16 for about a year; did you mean 18 or 19? Or did you have a system sitting there without updates and vintage F16 updates still hadn't been applied? (I'm not judging, just making sure!)
– mattdm
Aug 13 '13 at 4:16
Yes, vintage F16 updates had not been applied, and I finally applied them. I fixed this by runninggnome-screensaver &, since I guess this was removed from a list of startup apps. It's not ideal because I have to run that each time I restart or manually put it in my login file (seems like I should not have to do this).
– jonderry
Aug 16 '13 at 18:39
add a comment |
I recently ran a bunch of updates (I didn't pay attention to which, I was just prompted to update a bunch of stuff), and after running them, the lock-screen shortcut (CTRL-Alt-L) no longer works. I tried modifying the keyboard shortcut in the keyboard system settings to no avail. Does anyone know what the problem might be or how I can find out?
fedora screensaver screen-lock
edited Aug 12 '13 at 22:50
slm♦
251k69529685
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
I recently ran a bunch of updates (I didn't pay attention to which, I was just prompted to update a bunch of stuff), and after running them, the lock-screen shortcut (CTRL-Alt-L) no longer works. I tried modifying the keyboard shortcut in the keyboard system settings to no avail. Does anyone know what the problem might be or how I can find out?
fedora screensaver screen-lock
fedora screensaver screen-lock
edited Aug 12 '13 at 22:50
slm♦
251k69529685
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
edited Aug 12 '13 at 22:50
slm♦
251k69529685
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
edited Aug 12 '13 at 22:50
slm♦
251k69529685
edited Aug 12 '13 at 22:50
slm♦
251k69529685
edited Aug 12 '13 at 22:50
slm♦
251k69529685
251k69529685
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
asked Aug 12 '13 at 19:47
jonderryjonderry
76421119
76421119
New updates haven't been produced for Fedora 16 for about a year; did you mean 18 or 19? Or did you have a system sitting there without updates and vintage F16 updates still hadn't been applied? (I'm not judging, just making sure!)
– mattdm
Aug 13 '13 at 4:16
Yes, vintage F16 updates had not been applied, and I finally applied them. I fixed this by runninggnome-screensaver &, since I guess this was removed from a list of startup apps. It's not ideal because I have to run that each time I restart or manually put it in my login file (seems like I should not have to do this).
– jonderry
Aug 16 '13 at 18:39
add a comment |
New updates haven't been produced for Fedora 16 for about a year; did you mean 18 or 19? Or did you have a system sitting there without updates and vintage F16 updates still hadn't been applied? (I'm not judging, just making sure!)
– mattdm
Aug 13 '13 at 4:16
Yes, vintage F16 updates had not been applied, and I finally applied them. I fixed this by runninggnome-screensaver &, since I guess this was removed from a list of startup apps. It's not ideal because I have to run that each time I restart or manually put it in my login file (seems like I should not have to do this).
– jonderry
Aug 16 '13 at 18:39
New updates haven't been produced for Fedora 16 for about a year; did you mean 18 or 19? Or did you have a system sitting there without updates and vintage F16 updates still hadn't been applied? (I'm not judging, just making sure!)
– mattdm
Aug 13 '13 at 4:16
New updates haven't been produced for Fedora 16 for about a year; did you mean 18 or 19? Or did you have a system sitting there without updates and vintage F16 updates still hadn't been applied? (I'm not judging, just making sure!)
– mattdm
Aug 13 '13 at 4:16
Yes, vintage F16 updates had not been applied, and I finally applied them. I fixed this by running
gnome-screensaver &, since I guess this was removed from a list of startup apps. It's not ideal because I have to run that each time I restart or manually put it in my login file (seems like I should not have to do this).– jonderry
Aug 16 '13 at 18:39
Yes, vintage F16 updates had not been applied, and I finally applied them. I fixed this by running
gnome-screensaver &, since I guess this was removed from a list of startup apps. It's not ideal because I have to run that each time I restart or manually put it in my login file (seems like I should not have to do this).– jonderry
Aug 16 '13 at 18:39
add a comment |
1 Answer
1
active
oldest
votes
Double check that the ability to lock the screen is still enabled in GNOME. You can do this using the gconf-editor tool. After launching it go to the following menu item "lockdown" under this branch in the tree:
/ → desktop → gnome → lockdown
Once in the "lockdown" leaf node of the tree you can enable/disable the ability to lock the screen. The item is "disable_lock_screen".
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f86476%2flock-screen-shortcut-not-working-after-update-of-fedora-16%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Double check that the ability to lock the screen is still enabled in GNOME. You can do this using the gconf-editor tool. After launching it go to the following menu item "lockdown" under this branch in the tree:
/ → desktop → gnome → lockdown
Once in the "lockdown" leaf node of the tree you can enable/disable the ability to lock the screen. The item is "disable_lock_screen".
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
add a comment |
Double check that the ability to lock the screen is still enabled in GNOME. You can do this using the gconf-editor tool. After launching it go to the following menu item "lockdown" under this branch in the tree:
/ → desktop → gnome → lockdown
Once in the "lockdown" leaf node of the tree you can enable/disable the ability to lock the screen. The item is "disable_lock_screen".
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
add a comment |
Double check that the ability to lock the screen is still enabled in GNOME. You can do this using the gconf-editor tool. After launching it go to the following menu item "lockdown" under this branch in the tree:
/ → desktop → gnome → lockdown
Once in the "lockdown" leaf node of the tree you can enable/disable the ability to lock the screen. The item is "disable_lock_screen".
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
Double check that the ability to lock the screen is still enabled in GNOME. You can do this using the gconf-editor tool. After launching it go to the following menu item "lockdown" under this branch in the tree:
/ → desktop → gnome → lockdown
Once in the "lockdown" leaf node of the tree you can enable/disable the ability to lock the screen. The item is "disable_lock_screen".
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
edited Aug 12 '13 at 22:50
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
answered Aug 12 '13 at 22:44
slm♦slm
251k69529685
251k69529685
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f86476%2flock-screen-shortcut-not-working-after-update-of-fedora-16%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
New updates haven't been produced for Fedora 16 for about a year; did you mean 18 or 19? Or did you have a system sitting there without updates and vintage F16 updates still hadn't been applied? (I'm not judging, just making sure!)
– mattdm
Aug 13 '13 at 4:16
Yes, vintage F16 updates had not been applied, and I finally applied them. I fixed this by running
gnome-screensaver &, since I guess this was removed from a list of startup apps. It's not ideal because I have to run that each time I restart or manually put it in my login file (seems like I should not have to do this).– jonderry
Aug 16 '13 at 18:39