Fedora :: X Server - Gnome Screen Saver Cuts In And The System Remains 'as Is' Until 'woken Up' With The Mouse Or Keyboard
Dec 2, 2009
If I remain 'connected' (with the KVM) to the linux machine the gnome screen saver cuts in and the system remains 'as is' until 'woken up' with the mouse or keyboard. However, if I switch to another machine using the KVM, within a short time (maybe even minute or two) the linux machine goes dead. Now it has not crashed, as I can log in from a remote machine and do anything I need from a terminal, but the machine seems not to respond. I can't even use ctrl-alt-fn to switch to a console screen.
I initially tried entering telinit 3 from a remote machine but it made no apparent difference. However, if after telinit 3 I then killed the Xorg process and later issued a telinit 5 the X server restarted, but with a curious black 'notch' at the top of the screen. I am using an NVIDIA GeForce 7600 GS graphics card. I am now adding the backtrace from Xorg.0.log. It seems that when the KVM switches to another machine for more than a very short time the X server crashes.
My Gnome screensaver doesn't work, although it once did.
I have searched for a solution to this problem but no luck. I am running FC 11 and out-of-the-box gnome. At first the screensaver worked normally, shutting off the screen after 5 mins. Now it does not do so. I found the following command line suggestion in the forums, and it looks like it may point to a problem -- the screensaver is inactive, but how to make it active? I may be misunderstanding the term inactive, of course. Logically, the screensaver would have to be inactive if I am typing a command.
In any case, the query command shows:
Just in case the screensaver really was not running, I tried this command (which I found in another post):
But the query returns the same thing as before.
The only thing I can think of that might be an issue is that using the "appearances" background facility I added a couple dozen pictures that I thought I might use as screen background. Not long after that I discovered that my screen did not go black after 5 mins as expected. Not sure this correlation has any causal meaning, however. I then tried various things, finally returning to the plain (blue) default. That seemed to fix it for a short while, then after a couple of days, the bad or non-behavior returned -- the screensaver does not work.
(update -- I removed all the extra background pics and it makes no difference.)
My system runs all the time, but I don't want the screen to be on all the time.
I have recently installed 11.04 natty on Intel Core i3-2100 3.1 GHZ using its own graphic accelerator. When the screen is idle for a long time, more than 1 hour, I get a black screen with the mouse arrow but nothing else. the mouse moves the cursor and Ctl+Alt+F1 does work. How to fix this problem?
Have just upgraded (14-->15) using the dvd option; installed the nvidia driver (I think) and am able to startx and get to the Gnome 3 desktop (Wallpaper and top "task" bar look correct)..But, the mouse and keyboard have absolutely no affect. No matter what I click on, or what keyboard combination I use, nothing happens..(Have spent the last 3 hours researching it; and just seem to be getting nowhere.. I can do anything I need to from the CLI; but am not sure what to do..
I am trying to install fedora 10, 64 bit on computer with the following specification but the installation stops during installation (mouse , keyboard, screen freezes). Motherboard Gigabyte GA-MA790GP-ud4h rev.1.0 processor AMD phenom ii 940 I have updated the bios to the latest version.
I installed Fedora 11 on an external usb HDD (StoreJet trascend) connected to my Acer AspireOne (110 L), and it has been working marvelous for over a month. Today, something really strange happened: After I choose the booting media (StoreJet trascend) Fedora 11 freezes on the loggin screen: Both, keyboard and mouse, stop working. I have no idea what services are shoot down or not recognized since the start screen starts with the blue and fedora logo one.
I am running a SLC 5.2 with a Gnome 2.16 desktop setup for all the class room terminals. Where can I determine the status of the screensaver. The value could then be periodicaly tested within a "cron" script. If screen saver was running then a "skill" could then be called to force a complete logout releasing the terminal for another student.
Got myself in a bit of a squeeze here. I was messing around with the Xorg install on my Fedora 12 system. I ended up reinstalling it. Now my mouse and keyboard work fine in single user mode / terminal. But if I try and boot to X they dont work at the login screen. HAL and udev are booting. Ive done a udevadm monitor test in single user mode and its seeing the devices connect and disconnect. Ive also tried both USB and PS2 devices. Same issue. Ive tried playing with xorg.conf and generating it with Xorg -configure :1 I dont know to use to fix it. After banging my head against the wall for 20+ hours I decided it was time to ask for help. m just Lynxing around the web at the moment =X
It's two days now I'm in deep troubles after my last "yum update". The system boots as usual, the graphical login pops up the normal way but no input is handled by either the internal keyboard (the system is a laptop), the mouse pad, the external USB mouse and keyboard.
The hardware itself seems to be working as I can pop up the BIOS menus and even edit the GRUB booting line. But, after GRUB there's no possible input. I've tried to boot the system with the Fedora 11 DVD, rescue menu and then chroot. This in order to run a "yum update" in the hope that the problem was in some broken update. No chance: there's no update.
My questions are:
1. Is there a way to boot Fedora withou any graphical interface from GRUB (or anything else to skip the KDE)?
2. Is there a way to have the (cabled) network activated at boot *before* the graphical login?
3. What the he** is happening to my otherwise pefectly working laptop?
what program runs the Session lock and the screen saver for gnome and KDE on centos 5.5. But most importantly id like to know what the config file for the screensaver/session lock is called and where its most likely located.
The system freezes after the screen saver. 'Blank screen' is used. I can't do anything, so I reboots the machine from another terminal. I am using CentOS 5.4 x86_64.
I downloaded the Fedora 11 KDE livecd, installed it, and after the reboot when I get to that "firstboot" screen, I can't move the mouse, the keyboard doesn't work, I have to hold down the power button to turn off the computer.
I have recently loaded Ubuntu 9.10 which runs perfectly, except for the power management system.I go into the GUI power management screen and tell it to use the screen-saver after ten minutes, but NEVER suspend/ hibernate but it suspends/hibernates anyway,sometimes after an hour, sometimes hours later.Is it possible to keep the screen-saver but disable the rest of the power management system?
My keyboard has suddenly stopped working in Gnome (Ubuntu 10.4 LTS, Toshiba satellite laptop, P300). It works fine to logon, and with KDE.
The last thing I did before it stopped working was to hold down a shift key for too long, while I was thinking about what I wanted to do. The 'sticky keys' prompt popped up, which I killed. After that the keyboard has died - in *all* applications (e.g. gedit, terminal etc.)
The mouse still works. If I logout of Gnome, it comes alive again to type in the logon password. I had a look in messages, but without any enlightenment.
does F12 have screen saver like windows..or what? how can i prevent from auto locking users? I run some program that need times to perform and so it need to be stay log in users acc.
As the title says i have this error on both my main computer and my laptop. For my main computer see this post, that is when it happened. viewtopic.php?f=30&t=65743
I run the updates on my laptop a while ago and decided to restart it to check if everything went okay. It seems not.
The only way i can get on the desktop, is to choose the recovery mode, su to user and startx.
This is a common error during booting on both computers. Starting the hotplug events dispatcher: udevderror binding control socket, seems udevd is already running
It seems a little strange, same error on both computers.
I know that by pressing CTRL+SHIFT+NUMLOCK I can use the number pad as a pseudo mouse, but is it possible to force this condition at boot without needing to enter a key press?
(I'm putting a computer in my car running Ubuntu and have decided to do away with both the mouse and keyboard and control it from a joystick on the steering column. This has been wired to the circuit out of an old keyboard to mimic the arrow keys on the numeric keypad.)
So it's a beautiful day and I'll be happily using my computer when I realise that the screen is no longer showing that I'm typing or moving my mouse (or finger across a touch-pad). I can leave my computer in this frozen/crashed state for hours. My only recourse is to drain the battery or hold down the power button until the computer shuts down. The computer is a Dell Inspiron 6400 laptop/notebook. As my memory serves, it has an ATI graphics thingy. Radeon 1400, maybe. But I've had the computer for years and this behaviour has emerged only the past couple of months, with seemingly increasing frequency.
The OS is # uname -a Linux polaris 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux (aka Squeeze?)
Sometimes this happens within minutes of turning the computer on and logging into Gnome. Sometimes this happens only hours after I've started using the computer (mainly just surfing the web). Sometimes it is preceded by a loud boop sound and the following if I have console open, sometimes not. So maybe that's unrelated. But that happened just now so I thought I'd throw it in.
One weird thing: Usually this happens within an hour of starting to use the computer, but one occasion I noticed I had not had the problem for several hours. On that occasion, the only thing I noticed I was doing that was also unusual: I had turned on and forgotten about a kvm virtual machine. After I shut down the vm, I had about only a minute before the freeze. I'm surprised now that it hasn't frozen since I started typing thing. Maybe I should always keep this forum open in a browser window.
I have a Logitech Wave keyboard and mouse for my computer. I am not sure which version of Ubuntu I am running on but I think it is 6.10. When I boot up my computer I can go into the BIOS and earlier today it would even let me press escape to seee which operating systems I could boot. Now it no longer lets me see the operating system I have (which is why I cant say which version of Ubuntu I have). It takes me to the log in page and asks for the username and password but I cant type and I cant move the mouse. Earlier I could also use Alt+F1-F12, but this is no longer working either so it just sits at the login page and nothing works at all. The computer that is having this problem is very old it is a Proteva and when I opened up the actual computer the processor says:
At startup the computer says that the processor is a: AMD K-6
I know that the BIO's are to old for Ubuntu to run properly because at startup it also says that: "ACPI : BIOS age (1998 ) fails cutoff (2000), acpi=force is required to enable ACPI" it also says that: "ACPI : unable to load the System Description Tables."
I have'nt used this computer for about a year or two, but the last time I used it it worked perfectly fine. I have been seeing questions on the forums similar to mine, but their problems are on other versions of Ubuntu and their mouse's are said to work fine. I cant try any of the solutions for the problems I have read about because I cant open the prompt that you get when you are at the log in screen and press F2. I have no idea what to do.
I have 2 computers running Ubuntu 10.04, One of them have a screen, keyboard and mouse connected (all wired)I want to control the other computer in some way, like a virtual PC in a window, via my network or a cable.
When I start ubuntu I can't use my mouse and keyboard. It works in a second when the log in screen appears but then it freeze. It works in bios, grub and safe mode. I use mx518 and ace kl 400.
I am COMPLETELY new to Linux.I started a computer class recently and I started teaching myself PERL.My teacher had mentioned to me that it's far better for some reasons (he did not elaborate) to write code in a Unix system. So I got Ubuntu 10.10.I installed it along side my windows 7.After I setup my windows (had to reformat the disk) I decided to boot up into Ubuntu to set that up. I installed the necessary drivers that it required, and the updates. I was asked to restart the system so I did so.
It did not even shut down or restart my system.I waited patiently 15 minutes...30 minutes 1 hour... until I finally decided to hit the reset button on my PC. Then when I'd boot back in to Ubuntu afterwards, it would stay at the log in screen and my mouse wouldn't budge and nor is my keyboard recognized by Ubuntu.Im really frustrated and I've been searching for answers for the whooole day and I just can't seem to find something well explained. Im completely new to Ubuntu so I don't know where to enter any code in a cmd line or such.
1)Reformatted my harddrive to install windows 7 on it 2)Set up windows 7 and then booted into Ubuntu. 3) Set up Ubuntu and installed necessary drivers and updates 4) Reset the computer and waited for an hour for the reset to happen but nothing happened. 5) Manually reset my pc and booted into ubuntu 6) Stuck at log in screen with mouse and keyboard not functioning (unable to use ubuntu).
I'm on a LG E500-VAP36P, with 3gb RAM, 250 Gb SATA HDD (Kubuntu Hardy kernel 2.6.27-9-generic), and my keyboard and my usb mouse don't work at the login screen. My touchpad works and my keyboard works in command-line session. This is my xorg.conf. I also attach a relevant part of my syslog.
I know that in previous versions of OpenSuSE one could be in front of the screen/KBD/mouse get things started, and log into another session and get things started there and run some apps, and so on. Now with OpenSuSE 11.x I see no means in which to do so. Is there another way? Point being is that I want to run one application as one user session and another application in yet another user session. Either one I can get to by switching user accounts at one screen/kbd/mouse. Or through VNC. No need to run something like xen or VMWare and incur additional overhead. (It is next on my list to try though.
First I tried VNC. Easy install through Ubuntu GUI, but I could only see a still picture of the Ubuntu-desktop that wouldn't update. I could see on the Ubuntu monitor that the cursor was moving and the keyboard did work, but on my Windows computer, the screen didn't refresh. Then I read a bit on the forums and people seemed content with nomachine NX or freenx. After a bit of hazzle I finally managed to get a connection between my Windows and Ubuntu-machine. But the same thing happened here. I get to see a still picture of the Ubuntu desktop, mouse and keyboard working, but the screen doesn't refresh..!
I downloaded and burnt the Kubuntu 10.04 release to a CD. I tried to install it. First time, couldn't find the disks and eventually it froze. Ok, second try, when it's contacting the "time server" (or whatever) another freeze, but this time I notice everything is running fine and then get a nice little image with the current time (increasing seconds and all). Third attemp, clicked the "update this installer" and it went fine. "Yay!" I thought. Well, a few minutes in my beautiful 10.04 system and again, another freeze. Hit the power button and to my surprise a "Shutdown" dialog shows up with a countdown. After 30 seconds it logs out and mouse is working again. I log back in and come here to write this long post, and as I was writing the title "Random mouse/ke..." guess what? Yeah, it froze again. And the little bar that goes after the writing continued happily blinking. Hit the power button but this time mouse and keyboard were still frozen in the login screen.
Short version: mouse and keyboard randomly freeze while the rest of the system apparently work fine.
