FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I did some updates yesterday and now I cannot lock my screen via the keyboard shortcut (Ctrl+Alt+L) or the panel.
Using fedora 12 and gnome.
Here is the Yum log for the updates...
May 23 10:35:29 Updated: transmission-common-1.93-1.fc12.i686
May 23 10:35:34 Updated: initscripts-9.02.2-1.i686
May 23 10:35:34 Updated: transmission-cli-1.93-1.fc12.i686
May 23 10:35:37 Updated: transmission-gtk-1.93-1.fc12.i686
May 23 10:35:38 Updated: 12:dhclient-4.1.1-16.fc12.i686
May 23 10:35:39 Updated: 2:tar-1.22-13.fc12.i686
May 23 10:35:41 Updated: stunnel-4.33-1.fc12.i686
May 23 10:35:41 Updated: system-setup-keyboard-0.7-3.fc12.i686
May 23 10:35:46 Updated: groff-1.18.1.4-21.fc12.i686
May 23 10:35:48 Updated: ppp-2.4.5-8.fc12.i686
May 23 10:35:49 Updated: transmission-1.93-1.fc12.i686
May 23 10:35:51 Updated: logwatch-7.3.6-51.fc12.noarch
May 23 10:35:52 Updated: 3:ypbind-1.20.4-23.fc12.i686
May 23 10:35:53 Updated: yp-tools-2.9-9.fc12.i686
Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.
I normally start mine manually when I need to lock the screen. But I'm a bit of a minimalist. If I'm not actively using it (or couldn't find some way to disable it), I'm not running it. To include cron, inetd, and other staples.
I normally start mine manually when I need to lock the screen. But I'm a bit of a minimalist. If I'm not actively using it (or couldn't find some way to disable it), I'm not running it. To include cron, inetd, and other staples.
Thanks shadow, but there are no processes with that name.
Which could be your problem. No screen saver, no locking mechanism. I have to enable xscreensaver before I can lock my X session. But I'm running IceWM.
Which could be your problem. No screen saver, no locking mechanism. I have to enable xscreensaver before I can lock my X session. But I'm running IceWM.
Yes, I understand that is my problem, I just can not figure out how to get it to start at boot. I can add it to rc.local or something similar, but I would rather fix the problem instead of using a work around.
Or maybe some form of dpkg-reconfigure. Is changing your background image a work around? You could always add it to .xinitrc or something. Or if you're running KDE it has some administrative control (kontrol) abilities to set that setting. It's not really a work around, just how your system is configured. You changed some apps and it changed your configuration. With a little bit of knowledge you can track down who/what changed. Not that it'd be a good use of time, but it'd let you know which package maintainer caused you some grief.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.