Fedora :: Gnome: Screen Dims And Locks Up Processes?
Jun 8, 2010
This is a bit complicated to discribe because I don't know the cause, but this problem has been happening for some time (over a few years and generations of kernals), with different Gnome distributions, including Ubuntu (and family) and Fedora. When using Gnome (and only Gnome), I frequently see the screen dim. At the same time, all processes will be locked up. This may happen for a second or two, or it make require a reboot. The mouse can usually move and the underlying program GUIs are still visible, it's just that one or more of the GUIs will be dimmed. This is usually most noticeable with a browser, but that may just be a coincidence.
The whole screen goes dim for any of the below examples. running "compiz --replace" fixes it until any of the below happens again. When the screen is dim, a new window opened (ex: firefox new window or a new gnome terminal) is full brightness while the rest of the screen stays dim.
Following causes the screen to go dim: In the screen saver - hit the delete key to backspace when the password field is empty. in firefox - ^f to find on a page - start typing and as soon as the find field has text that does not exist anywhere on the page "Phrase not found" the screen dims. in gnome terminal - the profile has the terminal bell checkbox ON - hit backspace on a bash input line with no text on it.
I have enabled compiz on my mum's 64 bit Ubuntu desktop. It works well, but the screen dims significantly once I click the mouse button to rotate the cube. Releasing the mouse button brings the screen brightness back to normal. Is there a setting that controls the screen brightness whilst rotating the cube?
I'm running openSUSE 11.3 with an Intel GM965 on-board video card. After upgrading xorg-x11-server to 7.5_1.9.0-62.2.x86_64 from Index of /repositories/X11:/XOrg/openSUSE_11.3/x86_64 after a suggestion to fix a different problem, I noticed that the screensaver seems to work fine as mentioned above. However, I've noticed now that when the screen starts to dim before applying the actual screensaver I apparently can't cancel the screensaver initiation until after the screen finishes dimming (that is, goes completely black) and the screensaver actually starts. No amount of mouse gestures, clicks or key strokes will cancel the screensaver once the screen starts to dim until the screensaver itself starts running.
I replaced my gnome with openbox some time ago, some of the gnome utilities still boots at at the start and I love and use most of them. Still few of them are causing problems, how can I selectively disable from autostarting?Also which utility takes care of mouse speed? I keeps resetting my settings?PS; I did some research and fooled around with xinit files, tried to grep them out of the init stuff, no result...
I have a Dell Latitude E5500. For some time I've been installing different distros on it to find which is best suited for my needs. I've tried Ubuntu, Kubuntu, Mandriva, openSuSE, Fedora, and several others. So far, openSuSE takes the cake in terms of what I need, speed, usability, etc. However, I have a soft spot for Fedora and I'm trying so hard to make things work, but I'm kind of at the end of the road unless you guys have some suggestions.
I was in the IRC chat for Fedora asking around, and one user was kind enough to point me in this direction, which made sense as to why I was having issues.
[url]
I was having mixed results, but I had also installed from a Fedora KDE LiveCD. I decided I'd try the full DVD release of Fedora 12 64 bit, so I installed it this evening.
To my disappointment, even the nomodeset parameter does nothing. I get to the blue screen where there's some kind of logo in the center that fills in with white. After it fills in, an F appears. That's where it stops. It just goes no further. Further adding to the confusion is the fact that the fix lists a kernel there, indicating (to me at least) that the kernel listed is when a fix was deployed. I have a newer kernel than that, and despite that I still have these issues.
So needless to say, I'm using my laptop as testing grounds to plop a different distro than Ubuntu on my laptop and 2 servers full time. I really want to make Fedora work, but at the same time I have to use what works for me. Not being able to boot and log in is kind of a big deal. :P
Is there anything I can do or try? I want to keep the OS's I run all the same, so if Fedora 12 bombs out on this laptop, it has no chance on the other servers I plan to run at work. So far openSuSE is running without a hitch but I'd really like to give Fedora 12 a chance....
Im running suse 11.2 on a gateway lt3103u during boot i noticed the screen goes dim. i thought nothing of it untill i tried to watch *ahem* educational video *ahem*. ive found that no matter what program i use xine vlc or anything else that video sets the screen to dim as if it were in power saving mode. this problem also occurs when i close the lid. it locks the screen into dim mode. in both cases i can use both Fn keys and the power management widget to reset it to bright, but this problem is annoying having to keep turning it back u to see.
After a recent "yum update", my laptop screen locks up during graphical boot. I use rhgb on the kernel line. The container on the screen fills up with charge and then the screen locks. I have to use the power button to reboot. If I press ESC when the boot splash appears (i.e., boot in text mode), it works.
If I set plymouth to "details" mode using $ plymouth-set-default-theme details --rebuild-initrd It boots up correctly. This is equivalent to a text boot screen. I doubt whether it is a video driver problem. I reinstalled the nvidia driver and it is working. I also reinstalled plymouth and plymouth-themes-*.
I noticed this weird behaviour yesterday after the last update (not sure if it's really related, but I didn't notice this before).When I do a fresh start and log in - all the gnome related processes are DOUBLED in the memory Of course it causes weird errors, applet hanging or crashes, very sensible slowness while booting and operating, etc, etc.Basically I have 2 gnome-session loaded at once - one as a child process of gdm-binary and another separate one. Both sessions have all the child process loaded, so I turned out to have 2 Nautilus, 2 Metacity, 2 Gnome-panel, 8 python processes and all the set of applets are also doubled.
In the gnome-system-monitor, on the "Processes" tab in the "View" menu, I should be able to choose between "Active Processes", "All Processes", and "My Processes". The chooses are all greyed out and I am only able to view "My Processes".I launched the app as root and had the same lack of choice.I also disabled SELinux and rebooted the machine.
I have an Emachine that my uncle gave me and I thought that Ubuntu would find a nice home in the cozy case and well.....
I have a Emachine el1200-05w AMD Athlon 64 2650e / 1.6 GHz NVIDIA GeForce 6150 SE 2.0 GB mem. and 160GB HDD
I had to fight to get it to install kept freezing and stopping. I finally got it installed. It runs fine and is fast. I like it alot and then after about 5 to 10 min. The screen locks up or will distort in multicolor stripes across the screen. I cant figure out whats going on!
I did just notice that the specs say it's a 64bit possessor and I'm running the 32bit ubuntu will that make a difference?
Specifications: Dell PoweEdge 1600SC ATI Radeon HD 2400 Pro 256MB PCI graphics adaptor Ubuntu 9.10 "Karmic Koala" Linux 2.6.31-22-generic #69-Ubuntu SMP Wed Nov 24 08:51:08 UTC 2010 i686 ATI fglrx drivers Set up for dual-head display using two Princeton 19" monitors Using the Gnome desktop and screensaver
At some point, I suspect since the last kernel upgrade, I've begun experiencing a problem when the screen locks: I tap a key on the keyboard and the monitors wake up, but I get no "unlock" dialog. I can usually Ctrl-Alt-F1, login and gracefully reboot the system, but sometimes I have to hit hard reset. For now I've disabled the screensaver in "System -> Preferences -> screensaver" (I assume that'll stop the problem), but that's not an optimal solution.
I'm running 11.3 with GNOME on my Dell Inspiron 1525 with on board Intel video card. I had 11.2 64 bit running but did a fresh install of 11.3 with the 32 bit version. When the problems started occurring (locking up, logging out by itself, applications crashing that were fine in 11.2...), I tried reinstalling. When that didn't help I tried the 64 bit 11.3 but the problems keep happening. I can't get any work done. I've noticed that these occur while the computer is idle (either screensaver or later after the display has been turned off). I'll come back to my computer and notice that either the computer is locked up (screensaver frozen, audio on a one-second-loop...) and have to restart the computer or I come back to find the login screen waiting for me (and obviously have a new session when I log in).
I often need to login into various accounts. In Debian 7 I always was able to copy and paste passwords from text files if I was asked for an input, but now the textfield for password input locks the whole system and I can't do anything else before I have supplied the password. Is there any way of restoring the old behaviour to make password input forms (like the request for GPG key passwords in Evolution) just being an addintional app-window instead of an input request, that locks everything else? I want to be able to open the proper file with the login data when prompted for it.
I know I could theoretically solve this issue by using a general system wide main key which would supply all individual login data, but I want to memorize some often needed phrases by actually typing them when I need them. I just want the possibility to open text files for copy and paste when I'm prompted for a password if this is something I don't even want to remember.
I would like to run a command when the screen locks, and another when it unlocks. I work in a shared office space. When I leave my desk (and the screen locks) I would like the webcam motion capture software 'motion' to run, in order to record anyone who uses my computer when I'm gone. Likewise when I come back and unlock the screen I would like it to pause.
When Ubuntu loads on my laptop (micron gx3, pentium 4) it freezes on the install screen. Is there something about my hardware that might cause a problem? I looked @ the other micron GX3 forums and didn't see the same case
Recently, ive been having this problem with ubuntu in which while im watching a movie and thus not doing anything else, everything locks up except for the sound (if i attempt to move mouse doens't work) and then it goes into the login screen. Previously, ubuntu would fade away into the login screen.
So is there any way to prevent ubuntu from going to the login screen if the user is not moving the mouse? non-fading login screen?
edit: oh and i also have this sometimes occuring problem where i type my password to login, it logs in, and then it immediately goes back to login screen. A second login works. probably not relevant
I'm running 10.04 and when my screen locks I can't unlock it. I enter my password and it checks my password forever. This is a recent problem. I don't know what's causing it.
I am not sure exactly what is going on, but my ASUS UL30a (X32a) keeps locking up until I press a key, then it seems to resume for a while.
At first I thought it was just the mouse, but I noticed that the screen stops refreshing also. Hitting the space key (or any other key) brings the systme back to life (until it happens again).
It is a fresh install of Ubuntu 10.10, not much seems to be going on in the top list (compiz 1%, xorg 0.5%)
I am looking for ways to try and diagnose the problem (if not fix it )
I'm using SolydX, based on Debian Jessie. XScreensaver is installed and disabled, but it still locks my netbook screen after some minutes and suspend mode. Waking the netbook up brings XScreensaver login window. I'd like lightdm login window to appear instead.
I just installed 10.04.2 Desktop. Full install, reformatted all partitions. Hardware: Dell Optiplex GX200 with Dell 781p monitor Dell mouse and kybd.
All appeared to install well and as expected.
The computer has locked up 4 times, now. Whenever I attempt to use the mouse to drag a window to a different place on the desktop the monitor goes half black (bottom half of screen) and I loose the ability to use the mouse or keyboard to provide input. The only recourse is to shut it down hard and boot up again.
I've been using Ubuntu for about a year or so and have never had any problems installing it up until now.
I can boot from live CD for 9.10, but if at any point I attempt to install it to my hardrive, it either locks up or the screen goes black. Sometimes I'm able to start the installer, but the screen will go blank. The most progress I've been able to make on the install was up to 98% before it locked up, every other time I've gotten a blank screen or a lock up around 40-60%. After a hard reboot I get an error that reads "DISK BOOT FAILURE. INSERT SYSTEM DISK AND PRESS ENTER"
This problem doesn't only occur with 9.10, but with every other linux distro I've tried on it. My first attempt was with Ubuntu Studio, but I got similar errors. I've searched literally for hours and have found nary a solution that even comes close to solving my problem. using HP Pavilion a404x desktop
I just got a wireless dongle because in my house wired is not possible, but now I am getting problems. The dongle is a tp-link that turned out to be plug&play (unlike windows) and seems to work perfectly, except when the screen locks. I have tried to download overnight several times and it seems like a few minutes after the screensaver comes on or after I lock the screen, the connection is dropped. It works completely fine normally. So what changes when Ubuntu (its maverick with all updates) locks the screen? Also, when I log back in, I have to unplug the dongle and plug it back in to get it to connect again.
This is really REALLY annoying, enough to make me switch back to windows if I can only download while I'm looking at the screen.
I have a very strange problem since I turned to kubuntu 10.4. Often, after some heavy working, my laptop works very slowly and suddenly when loading something, it locks and white lines turns all over the screen, just like curtains. Linux jumps out of KDE and logs in automatically. That's very anoying since all my work is lost and it turns back to the previously saved session.
Also, often when I boot, the load screen is also mmissed up with those white lines. The only thing I can do then is to reboot.
I tried to re-install kubuntu (in first instance, i upgraded in kpackage, then i re-installed with formatting the root en swap partitions).
I don't know how to solve it. Only thing that seems reasonable now is to downgrade, since i didn't have this problem on 9.10 (fyi: I have a dell inspiron 1501 with ATI Xpress 1150 256MB HyperMemory video card, formerly i had problems to have good graphic drivers for it on previeous versions of kubuntu (some 3d games didn't work), maybe this has someting to do with it?)
This is the second new install of 10.4 on the same machine with the same issue. After boot, as soon as user logs into the desktop, sys mon shows cpu at 100 percent and a steady climb in ram usage. several processes are spawned continuously until all ram is consumed and then moves on to use scratch space.
Using top, the process count moves into over a thousand total processes. Some investigation using top, ps, and digging into the /proc folder shows a ppid of 1 If the machine is booted to shell, top shows 120 processes and is stable. Some of the processes running repetitively are the gnome toolbar, nautilus, and I wish I was clear headed enough to write the others down before I left work. I can certainly get a more complete list in the morning.
I have swapped out ram, and the processor with no success. I have also tried apt-get purge ubuntu-desktop then installing with apt, this did not resolve it. As mentioned at the top of the post, this is the second install with these symptoms. The first install started showing the issue about 10 hours after first boot. On this second install, all was working fine for a couple days before this started in.
Acer 5250-BZ475 laptop, fresh install of Ubuntu 11.04. Boots up beautifully as long as an ethernet cable is plugged in. Otherwise, I get to the login screen and have just enough time to start typing in my password before the entire system hangs hard - no mouse, no keyboard, can't even get to a terminal, nothing. Have to hard power off the machine.
It seems to be a problem with the wireless card trying to initialize, but there doesn't seem to be a bios option to disable wireless on this laptop, so I'm a bit at a loss as to how to fix this problem. By the way, wireless works fine if I boot up with a cable connected - I can see all the wireless access points in my area no problem. I just can't boot without a wired connection, which makes my laptop more or less useless when I'm away from home with it.
I have a situation where I have several screen (/usr/bin/screen) sessions running. 2 of the screen sessions (ps1 and ps2) run a script that launched SipP with specific parameters. 1 script starts SipP and has it make 50 calls where the other makes only 20 calls. However The script is configured where we can change how many calls it makes if needed.
So the problem is, due to issues with SipP, we must restart everything every 12 hours (at maximum). So I am trying to work out scripts to stop the SipP processes cleanly. In order to do so I need to figure out which SipP process is spawned by which screen. i.e. which sipp was started by screen session ps1, and which one was started by screen session ps2.
Now I can do ps -ef | grep <number of calls configured> to find out but then I would have to change my stop script every time we reconfigure how many calls are made, and have a separate stop script for each screen session. I would much rather be able to send the screen name as a parameter to the stop script and have it work no matter how many calls SipP is configured to make.Also your standard kill -1 <PID> does not shutdown SipP cleanly. So working out those details is a bit more tricky. Anyone know how I can determine what processes are spawned from a specific screen session?
I've read threads on it and cant get it working.... I want to enable the gnome login splash screen when desktop loads up but it never shows up ? What I've done is...
Is there a way to get F10 (Gnome) to remember where my screen positions are? I keep having to move them over and over anytime I open a new application and tell it where I want it.
On attempting to load GNOME 3 with Gnome shell, the screen fades to white, stalls for a minute, then gives an error and asks to log out. "Classic Gnome with Compiz" has numerous graphical glitches such as the background not refreshing (think Windows 95), among other things. How can I get GNOME Shell working again?
Gnome shell and classic gnome load fine under other users.
