Debian Multimedia :: Disabled XScreensaver Still Locks Screen
Apr 14, 2015
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 have set up minimal debian installation with pekwm, tint2, xscreensaver and friends. When I press Fn+F4 on my thinkpad or run pm-suspend from root terminal, it suspends just fine (yay), but when I resume, I get instantly logged in into my account. What I'd like to have, is that xscreensaver locks my session after suspend, so that I have to type in my password in order to continiue working.
PS. In /etc/default/acpi-support I have LOCK_SCREEN=true
I'm using Debian Squeeze with Fluxbox and I'm having a problem with xscreensaver. I've set to blank screen after 10 minutos of inactivity, but the problem is that when I'm watching a movie, the screen is blanked after 10 minutes too. So I have to manually kill xscreensaver before starting to see a movie, or I have to move my mouse / press keyboard every 10 minutes to activate the screen again.
I've done some search before posting and I only found something about a SMPlayer's option named "Disable screensaver", but it is already on and it has no effect preventing xscreensaver to work. Here is a screen shoot of my SMPlayer configuration window:
[URL]
Apparently, xscreensaver isn't being able to recognize that another program is running. Could it be related to dbus?
PS: I had a dbus problem when I first upgraded to squeeze, my multimedia keys stoped working in banshee (whenever I clicked to play/pause/next etc, another banshee process was started), but I solved it by adding this line to my ~/.xinitrc: eval "$(dbus-launch --sh-syntax --exit-with-session)"
On my 11.3 desktop I was annoyed by what I thought was the screen saver locking my session after an idle period, requiring my password to unlock. Well, I didn't want this behaviour and it wasn't supposed to do that, I had disabled every place in the desktop configuration that seemed to be related. I even looked into the KDE4 rc files with a text editor and they all seemed to be in order.
Eventually after some searching I found the answer: It's the setting "lock screen on resume" in the advanced settings > power daemon. Once I turned it off, it was fine; this desktop doesn't need suspend+resume anyway.
It seems that this is not a case of counterintuitive naming; it seems that in some configurations there is a bug where a stray event can trigger a screen lock by the powersaved (?). I don't really understand it, but you can start your investigation here if you are interested:
For some reason I cannot figure out, xscreensaver does not have permission to control my screen. It's present in memory, so the settings app thinking it is not present and asking if I want to start it is odd. Could the the necessity of using VESA BIOS controls to get around bugs in the VIA/S3/Unichrome chipset be the source of the problem? Are there other Linux screensavers that might work differently and might still be able to blank my screen?
My supposedly stable system was crashing. The problem was one or more specific screensavers--xscreensaver, the display manager (lightDM), and X itself are innocent as far as I can tell.
I'm on a Thinkpad T400 with Debian Jessie (8.4)/MATE/lightDM. I have libreboot and not proprietary BIOS. I like variety, so in addition to installing xscreensaver itself (the unofficial patched jessie version without the "out of date" nag, which I got from https://angband.pl/debian/pool/main/x/xscreensaver/), I also installed some extras from the official repository (xscreensaver-gl-extra, xscreensaver-data-extra, xscreensaver-screensaver-bsod). I enabled all the installed screensavers and asked xscreensaver to randomly cycle through them.
To my dismay, after variable lengths of time (usually within 20-60 minutes), when a random screensaver has been on for a little while (I'm guessing as it's about to go to the next random one), X crashes to a black screen. The only way to make the black screen go away is to kill X (which I mapped to Control + Alt + Backspace) then log back in. There are no useful logs anywhere except some cryptic IO error 11 entry in ~/.xsessionerros.
Now for the troubleshooting:
1) First I tried installing a more up-to-date version of xscreensaver (5.34-2), which I grabbed from the sid repository. This didn't work--same problem as described above. Therefore, I went back to the patched version for jessie (5.30-1 from angband.pl).
2) To exclude that the lightDM middleman was the problem, I disabled it and was logging in with startx. Problem did not go away. (I then rigged systemd to log me in automatically and for startx to run automatically once I'm logged in--who needs middlemen?)
3) To exclude screensavers butting heads, I uninstalled mate-screensaver and disabled anything from X that could be interfering (by running these commands in a startup script: xset -dpms; xset s 0 0; xset s noblank; xset s off). Problem did not go away. I kept this startup script nevertheless.
4) Finally, to exclude individual xscreensaver module(s) being the problem, I unchecked them all. Then I wrote down the names of my 20 favorite modules (which include some from gl-extra, some from data-extra, and bsod) and tested them in small batches, running xscreensaver with only 5 favorites checked at a time. After testing four batches of 5 and witnessing all 20 favorites both display and load without any X crashes, I went ahead and selected all 20 favorites. I left the laptop on overnight and in the morning (about 12 hours later) it's still going strong.
One or more particular xscreensaver modules are crashing X, probably at the time they are being loaded to be the next one to show. I think I already spent enough time on this, so don't really care to identify +/- troubleshoot the offending modules.
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 just installed Xubuntu 10.10 after killing my previous one w/ manual changes. Anyway, a moment after starting XScreensaver, the screen will blank. When i move my mouse, the cursor is visible, nothing else. the only thing i've been able to do is unlock, move cursor to the logout button, and logout.
So I'm using xscreensaver on Fedora 13 and was wondering if I could use a different screen-saver on each of my monitors (I have two). I don't know how or if I can do so, but I'm confident that someone here will.
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?
Using squeeze here. Until recent updates to xserver, my numlock worked as expected, but now the damn thing won't stay on anymore. Numlockx is still broken as it's always been for me in that it turns the numlock on but not the led on the keybord. I'm using slim as a login manager which everytime it's updated they set the numlock option to disabled for whaterver reason, but then that doesn't work if I enable it anyway (why have it?). So what is it with debain/(Linux) and their obsession with disabled numlocks at login, I don't get it?
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
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....
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 )
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-*.
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.
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?)
After jerking around with that utterly useless iceWeasel " XYZ has been disabled for your protection" and the other useless Epiphany " mousey no worky y preferences ? No you don't have any. I wiped that garbage clean and stuck Google Chrome on here. Everything works pleasingly well. I screwed around with it and didn't care for the beta. " Stable"
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 just upgraded to 10.04 and now my Sansa Fuze does not get mounted. The Fuze screen says connected and then writing, but then locks up.\ I have to disconnect it and do a reset before I can use it. I did get an error message on from Ubuntu. As I recall it looked like this:
DBus error org.gtk.Private.Remove Volume Monitor.Failed: An operation is already pending Anybody else tried to use their Fuze with 10.04?
Suffering with a log in problems for user accounts but I have compounded it by accidentally disabling local log in!
Using CentOS 5 and from within the local root user I opened the log in screen preferences and then opened the Security tab. I then opened the "configer Xserver" and I have unchecked the "logins are handled by this computer". Now Since I have logged out of root all I have is the X cursor on a black screen and no log in. Obviously logins are not handled by this computer as I unchecked it! Is there anyway to get this back on as I cannot access this from another PC.