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
[code]....
When i log in as root, and try to click the lock screen button, lock screen doesnt work? Is it disabled by default?is there anyway to lock screen when logged in as root
View 6 Replies View RelatedI'm using Fedora 15 with Gnome 3 on my laptop. I don't restart the system unless there's an update that requires me to, preferring to use the Suspend feature instead. However, I noticed that after an uptime of a few days, the screen doesn't lock anymore. Neither the shortcut 'Ctrl+Alt+L', nor the terminal command 'gnome-screensaver-command --lock' seem to work. I'm sure restarting the system will enable me to lock again, but I don't think I should restart just to get this feature back.
Does anyone know why this happens? Is there some other way to lock the screen?
To change the GDM image all you really have to do is right click on the desktop and hit "Change Desktop Background" and select the picture you want and then hit the "Make Default" button and both will change naturally. (The lock screen and GDM Login background)Then just switch it back to your usual desktop wallpaper and go on about your day.
View 5 Replies View RelatedI just installed Fedora 12 earlier today using preupgrade. Everything seems to work alright, but I do have a couple of problems. I've had this happen twice already, but when I'm booting up, my machine will freeze once the Fedora logo is shown right before I get into the login screen. Another problem I've had is when I do boot into KDE I'll see an ! icon next to the clock telling me that there has been a crash in the kernel.
Edit: Update- It only hangs when I reboot. If I restart in windows and try to boot fedora, it hangs, if I restart in Fedora, it will hang after the restart. The only way I can boot Fedora is from a cold boot
Edit: I seemed to have fixed the problem after searching Google for 20 minutes. I just ran this command as root.. #chcon -t system_dbusd_exec_t /bin/dbus-daemon
Is there a way to get a simple 'lock screen' function and Icon that will allow one to lock the screen etc by simply clicking a button? This used to be available in 'xscreensaver' but I cannot figure out how to get a similar function through 'gnome-screensaver'.
View 5 Replies View RelatedI'm running Gnome on Fedora 15 (currently in failback mode). I've installed the Fedora provided xscreensaver RPMs and ensured that xscreensaver is running when I login (not gnome-screensaver). The problem is, when I try to lock my screen using one of the multiple "lock screen" icons nothing happens. The following line does appear in my ~/.xsession-errors file when the icon is clicked.
** (gnome-panel:3548): WARNING **: Could not ask screensaver to lock: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkn own: The name org.gnome.ScreenSaver was not provided by any .service files
This line appears regardless of whether or not the gnome-screensaver RPM is installed. I've tried with both gnome-screensaver installed and without it installed with the same result.
Running "xscreensaver-command -lock" from the command line does successfully lock the screen.
Also, the screen lock icons do work when gnome-screensaver is installed and is set as the default screensaver. Anyway, I just upgrade to Fedora 15 recently (I've used all previous version of Fedora) and this is the first time I've run into this problem.
In Redhat Linux Enterprise Linux AS 4, how can i lock the screen without losing any program running.
View 5 Replies View RelatedI have experienced that the button in my main menu "Lock Screen" does nothing, so I can not lock my screen. What could be the problem? Is there any command in terminal what I could write, so I can see is there an error output or something?
I am using Ubuntu 9.10, GNOME.
I'm getting a HDD Lock screen or Disk Controller Failure at boot up. (Compaq Armada) The HDD stops the system dead. The controller failure will allow me to boot Fedora or Puppy from the CD drive.
View 1 Replies View Related1. When you lock a package shouldn't updates be ignored? I locked a few but the update-manager keeps bothering me about them.
2. Seems like randomly the checkbox for treat recommended packages as dependencies turns true. It has seemed that way for at least a year.
I keep starting up Fedora and I'm not able to get far (although it's not always at the same time) before my screen will go black, except it shows the mouse/cursor - but it's frozen, and thhen the caps-lock light starts blinking and I can't do anything or get it to recover. Sometimes it happens after 30 seconds, sometimes 40+ seconds and sometimes within 15 or so seconds.
How do I stop this and diagnose this?
I've tried, in the boot-startup to choose an older kernel version, butt the same thing occurs!
I have:
Fedora 11
Kernel: 2.6.29.6-217.2.16.fc11 i586
Asus EEE PC 1002HA
One other thing, it does always seem to happen after I've turned on wireless. And I've been using F11 for months now with no issue.
I keep starting up the computer and I'm not able to get far (although it's not always at the same time) before my screen will go black, except it shows the mouse/cursor - but it's frozen, and then the caps-lock light starts blinking and I can't do anything or get it to recover. It ONLY occurs after I log in to wireless network. Using a wired connection, this problem never occurs.How do I stop this and diagnose this?I've tried, in the boot-startup to choose an older kernel version, but the same thing occurs! And this was working for months and now is not.
View 1 Replies View RelatedAs a newcomer to Linux I recently installed F12 (2.6.31.5-127) from a full installation DVD and all worked well until I decided to download a bunch of updates. When I next booted up I had a second kernel (2.6.32.9-70) and the usual other option for my XP dual boot (which still works!).Selecting either kernel leads to the Fedora logo on a blue screen and then a black screen with a small underscore cursor in the top left and no other text. This is not a command line or a text editor but it simply displays key depressions - the alpha/numeric section of the keyboard in upper and lower case as normal and then the function keys and numeric key pad as control codes commencing with As both kernels yield the same behaviour, am I right in assuming that it is one of the program updates that is causing the problem? The only way I have found to get out of this screen is ctrl.alt.del which gives a short list of programs being stopped and then the machine reboots. I don't know how to pause this screen to get the details before they disappear.I have been through loads of stuff on this forum but nothing seems to fit. From the command line terminal off the boot options screen I tried su -c yum clean all and also yum clean all but all I get from Grub is error 27 unrecognised command.
As you can tell I'm a complete beginner, but I am willing to learn. The thing is I don't know where to go from here. All I want for now is to get back to the Gnome environment I can handle, then I can explore the command line at my pace instead of being thrown in at the deep end!
I' installed Fedora 12 from an installation DVD, repartitioned my hard drive etc.... After the installation has finished, there were 505 updates to install.
Here my problems started. Everytime I selected "all updates" I've got an error.
So i decided to install first all the updates with "rpm" - "yum" and "packages"
After this I could select all the other updates and install them.
During the installation my pc freezed. Rebooted and after the login there were always sessions "starting file manager" that was trying to start, one after the other... I proceeded my updates, and those processes stopped.
Ok, finally, all updates were installed and as good as I'm I rebooted my pc.......
My pc boots normaly, but the moment my logon-window should apear, I've a black screen... nothing else....
I can reboot with kernel 2.6.31.5-127.fc12.i686.PAE but how can I fix the error with my kernel 2.6.32.11-99.fc12.i686.PAE???
someone who knows the solution???
I found one who told me to install following packages:
- kmod-nvidia-PAE.i686
- xorg-x11-drv-nvidia-libs.i686
After this I've got my previous problem (before my complete reinstallation). Just booting till GRUB and nothing more.
I'm running Fedora 13 64 bit. Everything has worked fine, until today. The latest updates killed the video.
As the bar at the bottom of the screen starts to go across and say Fedora 13 the whole bar starts to flash then goes solid white. No errors or nothing, just a black screen. What causes this?
Nvidia drivers are installed. Maybe it's them. I've had trouble with video after updates with the last 4 versions of Fedora.
How to fix this mess?
I just downloaded OpenOffice 3.2.1 from the openoffice.org weebsite. I followed the instructions precisely and everytime ended up in the same error message - 'error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission denied)'. I am using Fedora 13.
View 2 Replies View RelatedAfter applying the latest round of updates last night, I turned on my laptop this AM (ATI X1300 Mobility graphics running the default drivers), selected the latest kernel in GRUB, and waited to log in....only problem is that instead of seeing a normal loading screen (Blue with Fedora icon filling in), I instead get a black screen mostly covered in multicolored rectangles. I don't believe there was a graphics driver update, so I'm rather confused as to what went wrong/how to procede. I can still boot using a previous kernel.
View 1 Replies View RelatedI hadn't used my laptop in a month or so and it had a couple hundred updates to install. Everything went fine and upon reboot I am met with a bizarre login screen. It shows my like every process and program in a list, my username is in the list as is root. I can login as either, but when I do it only boots to terminal.
View 1 Replies View RelatedWhen I hit Alt+Ctrl+L my system is starting the ScreenSaver but not locking the screen. The keybinding is correctly set. This is happening in only root account but in another user account it works perfect !
View 1 Replies View RelatedI ran the latest updates this week (including the new kernel and the new kmod-nvidia update) and I got a blank screen when I rebooted. (I get the Fedora bar across the bottom of the screen, then after that the screen goes blank) I assume this is when the xorg server is trying to start..
I went into single user mode , backed up and then removed the xorg.conf file but still got a blank screen upon reboot.
I rebooted into single user mode, copied the /var/log/Xorg.0.log file to a safe location, and then restored the system back to its original state.
I've since rsync'd my system back to where it was before the update.
Here's my Xorg.0.log file:
I've posted this to the fedora mailing list with no response, my apologies if it's been addressed here...
I have an IBM Thinkpad with an Nvidia card ( nVidia Corporation GT218 [NVS 3100M] (rev a2) )
I currently have the nouveau driver black listed in my grub.conf setup: rhgb quiet nouveau.modeset=0 rdblacklist=nouveau
I did the update which installed/updated the following:
---> Package kernel.i686 0:2.6.35.14-95.fc14 set to be installed
---> Package kernel-devel.i686 0:2.6.35.14-95.fc14 set to be installed
---> Package kernel-headers.i686 0:2.6.35.14-95.fc14 set to be updated
---> Package kmod-nvidia.i686 1:280.13-2.fc14 set to be updated
However when I reboot the system boots to a blank screen, and even the previous kernel boots to a blank screen. I tried installing akmod-nvidia but get the same results
I've restored the system back to before the update for now..
I have been installing these updates on Fedora 12 and so far, my computer now has 3 more fedora sub-versions "not sure if that IS their name". So when I first boot the pc, the 3 versions appear. Normally, that wouldn't seem like a problem "although I don't know why don't the new ones simply delete the old ones"..However, the new ones don't work. Only the oldest form which I installed through a CD is the one that works. The others just cause the computer screen to flash a couple of times and freezes.
View 3 Replies View RelatedWhat happens is that I resorted to deleting my .kde directory after my kid destroyed my profile where title bar, menu, konsole get broken. After deleting, I login again thus regenerating the .kde directory. To avoid my kid from messing my desktop, I tried to lock it. It does not lock.
It just need a KDE full restart perhaps since when I login the other day, it now works.
I'm updated to Slackware current for almost a month already and have not played a lot on KDE desktop (busy programming stuff).
However, on day I tried to lock the desktop in KDE to avoid the kid from destroying my cool desktop setting, but it didn't lock. Cool, so I tried screen saver and add an option to lock the screen.
When I test screen saver, it displays. But when I wait for 1 minute(I set it that way), it doesn't fire up. Not even after 15 minutes which I think the default.
It usually work before (several months ago) using the lower version of KDE. It is just last Saturday that I noticed it.
I tried to dig the profile management but I could not find anything relevant there.
When my laptop wakes up from suspend I often find that my screensaver have not locked my desktop. Does you see the same problem or is it just me?
View 5 Replies View RelatedI'm trying to use 'gnome-screensaver-command --lock' to lock my computer so that when my girl is on it I can **** her off
I can run the command from the terminal and it works just fine, but when I ssh into my computer and try to do it, I get the error
Code:
** Message: Failed to connect to the D-BUS daemon: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed. It'd be nice to be able to lock my screen from wherever.
I am using Ubuntu 10.04 LTS. I leave the pc for only a few minutes and when I come back the screen is black. I press a a key or pass the cursor over and it opens but I have to enter my password then press the unlock button.I am none to happy with this happening each time I happen to step away from my computer for a couple of minutes. I would like to know if there is a way to disable or turn off this function
View 3 Replies View RelatedPossibly a silly question, but here goes...In 11.1 and below I set a key shortcut to lock the screen when I push Meta+L. However, I can't seem to find a way to do this in 11.2. I tried the following:* I looked in the keyboard shortcuts settings page and didn't see an option for screen locking* I tried right-clicking on the screen lock button on the panel and setting the shortcut, but that doesn't seem to have taken effect* I googled and searched this forum, but no luckThe default key combo seems to be Ctrl + Alt + L, which works, but I have years of muscle memory for pressing Meta + L, so I'd like to preserve that if possible
View 3 Replies View RelatedSometimes after I enter my password after the screensaver has locked the screen, it will not take my password (even though entered correctly). It seems to lock up. After about 2 mins it says something about a time-out (wish I could do screencaps). Then it will reset and have a gray window the same size as the password input window but on the upper portion of the screen, and a password entry window as normal, but in the lower part of the screen. This time, it accepts the password and logs me in.This is a 2-part post.First, how to bypass having to wait for the timeout (for whatever is timing out).The second is to see if anyone knows an answer to the problem and a fix.After it freezes, hold CTRL-ALT and tap F1.This will taking you to a virtual terminal. Log in with your username and password. Then type:
Code:
$ pkill screensa
This will match gnome-screensaver and kill the program that is frozen. You then need to type
[code]....
I upgraded to latest 10.04 live x64 desktop today. Clean, fresh install.Before I was using 9.04 and had the same issue at first.I don't want the password lock screen when resuming from suspend.I disabled everything, lock in screensaver settings, all lock entries in gconf-editor. I also tried setting LOCK_SCREEN in /etc/default/acpi-support to false.Nothing helps Is this maybe a bug, since it's still beta? I don't know what else to do
View 1 Replies View Related