OpenSUSE :: Forcing Screensaver To Unlock Using Blueproximity
Dec 11, 2009
Back when I used openSUSE 10.3 with KDE 3.5.x I used the KDE-specific version of blueproximity found here: K-Blueproximity KDE-Apps.org. The thing that made it great was that it integrated kscreensaver.
It hasn't been updated in a couple years and isn't compatible with 4.3.x so I'm using the non-KDE-ified standard blueproximity package. For the most part it works. Based on comments I found somewhere I'm running the following command to lock the screen:
Code:
qdbus org.kde.screensaver /ScreenSaver Lock ; xset dpms force off
and to unlock:
Code:
xset dpms force on ; killall -9 krunner_lock kblankscrn.kss
.
The problem is that the unlock command doesn't work. My monitors will reactivate and the screensaver will display but in order to actually unlock I have to hit a key/move the mouse and enter my password.
what the command should be to actually unlock the screen since the above doesn't work.
I have an Xubuntu 10.10 File server / Media centre which I have set up to automatically lock the screen at 1am so the teenagers dont stay up all night watching movie and then being tired for school.My problem is I dont know how to automatically unlock it or how to unlock it through SSH.Usually I just manually unlock it every morning as I walk out the door but sometimes I forget and then can't unlock it from home.Kids come home from school while I'm at work and then cant watch movies or shows.How do I get it to automatically unlock the screensaver / screen lock?How do I unlock it through SSH without using VNC?BTW I cant get VNC working anymore since I upgraded to 10.10 with a fresh install either.
I am on Ubuntu 10.04, and I think I have had this problem since I installed it. When I type my password into gnome-screensaver and click "Unlock," all the buttons become disabled and the cursor turns into the "busy" look. I have to go into one of the virtual terminals and do "killall gnome-screensaver." This happens maybe 75% of the time when the screen locks.
Also, this last week or two there is a new problem where the gnome-screensaver covers only part of the screen and I can still see and use most of the desktop.
I'm trying to create a portable flash-drive from the openSUSE-11.3-KDE-LiveCD-x86_64.iso-file. I can boot and run it, but everytime I use Yast to install something (language, ...) everything but the mouse just freezes, forcing me to restart the laptop.
I got the blank screen when trying to install openSUSE 11.3 x64, so I was able to successfully install by choosing: Kernel (F6) > Safe Mode
Now I am trying to build my wireless driver, and I also notice that my touchpad is not scrolling. I had this OS installed in Windows 7 through VirtualBox before doing the clean installation, and I remember the touchpad scrolling.
I am thinking that by choosing Kernel Safe Mode to install openSUSE, that it did not install all the repositories, and it is why I am running into some difficulty.
what I need to do to fix my installation as if I had not installed in Safe Mode.
There's an OSS screensaver on windows that I love called PixelCity (links:blog post, github). it's pretty cool. and it runs fine on my Ubuntu (Karmic 9.10) with wine.Is there a way I can tell the gnome-screensaver about it so I can use it as one of my screensavers? I'm still fairly new to Gnome and the whole "screensavers as themes" thing is still confusing me.I've found my themesdir and tried to create a .desktop file for it, but obviously I've gotten something wrong as it just doesn't show when I open the screensaver prefs dialog, no error, no message, it's just not there.
Installing the xscreensaver packages added the extra screensavers I was missing, and I'm a pixelcity away from perfection..Of course the perfect solution would be if someone ported the screensaver natively to linux, which shouldn't be too hard as the source is open, it already runs on openGL and tries to confine most windows stuff to a single file. But I don't know C++ or 3D code or win/linux internals so I wouldn't know where to start..
I used playonlinux for a manual install of a game that needs more than one cd. I can't eject to install the next cd in line. How do I unlock the drive? I'm now in the middle of installing.
I had to force kill the yast, however, it didn't had chance to unlock the files it lockes while it workes. I know there is a way to manully unlock them, but don't know how to do it
I just did a fresh install of 11.4 My system auto-logs in and I know there's a bug in seahorse that doesn't like that method.
Anyway, I tried to unlock my "Passwords: login" in seahorse, but it won't budge.
The details about this user are that I re-used an 11.3 /home/$user directory. Could that be the reason? I logged out of the Desktop and back in using my password manually. I can sudo with my password. I can change the system with my password everywhere except in seahorse. The password is exactly the same in 11.4 as it was in 11.3.
The .gnupg/ directory is 600 and its contents are all 600 except for agent.info which is 644.
Following a year old post, I got this from shell code...
When I unlock the screen, I'm presented with an opaque dialogue (white box), regardless of whether I have a screen-saver or not. This is a cosmetic issue only because I can type my password to unlock the screen successfully, but I'd like a solution. I'm using oS 11.2 with KDE 4.5 (but the issue predates updating to 4.5).This is the only "issue" I've experienced since migrating my laptop (was Windoze 7) and desktop (was MS SQL server 2003) to oS
I'm still fairly new to Suse(and Linux) I have an account on my system that is locked when i run passwd -S accountname i get 'accountname lk' as the response. However when i try to unlock it using passwd -u accountname i get 'Cannot unlock the password for accountname!'.Any ideas on why i can't unlock the account?
I had this problem at times with 11.2 as well; I use GNOME. I have intermittent lockups when invoking the screen saver either while idle or soon afterward while using Firefox; problem seems to not show up if I do not use a screen saver when idle.
Few weeks ago after updating vlc player from 1.0.5 to 1.1.4 (now) it stopped disabling screen saver and while watching movies (DVD or file) I have to hit a key or mouse every few minutes because the screen saver goes on.I had no such problem before. It happen after updating and I'd like to add that I have checked the box 'Disable screen saver' in vlc settings.I run on OpenSuse 11.2, KDE 4.3.5, VLC 1.1.4, kernel Linux 2.6.31.12-0.2-desktop x86_64
So I've tried finding a solution to this on my own for the past few days (believing it is a simple solution), but for the life of me I can't figure it out. I'm running 11.2 and I have Evolution as a start-up program and I have finally got my wireless working, so it connects automatically at start-up also. I figured out how to have network manager automatically unlock the default keyring, but...
Each time evolution starts up I am prompted to unlock the default keyring. How can I give Evolution permission / access to the default keyring automatically so it can check me email upon start-up without me having to type in my password?
I've just installed opensuse 11.2 kde 64 bit and when I try to set a screensaver the whole program crashes. What's wrong with it?How do you fix the screensaver program?
I'm using Gnome on openSUSE 11.3. I wonder. How do you edit screensaver properties? For example get phosphor to display a stream of news? You could specify in Fedora and Ubuntu.
Suse 11.2 and kde, I'm trying to set up a screensaver. All the facilities seem to be there when I go System>Desktop and set the required details, but then I find the screensaver is non-operative, the screen just going blank after the preset time delay.
The set-up system does do the demo of the screensaver OK, so the software for it must be there and at least partly accessible. But it doesn't seem to get through to the system.
My screen saver crashes.Even trying to look at the screensaver in the desktop settings crashes.The crashhandler says "This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. System configuration startup check disabled.
I'm running 11.2. My screen saver has been working fine since the begining in December, but now when I run VLC or fldigi my screen saver will kick on for only a few minutes then it will pop back to the log in screen as if I had moved my mouse or hit a key on the keyboard.
VLC about shows : gcc version 4.4.1 [gcc-4_4-branch revision 150839] fldigi is latest version
I get a lot of these in var/log/messages: unix2_chkpwd: gkr-pam: couldn't unlock 'login' keyring: 1 unix2_chkpwd: pam_env(gnome-screensaver:setcred): non-alphanumeric key 'alias sox=padsp sox' in /etc/environment', ignoring unix2_chkpwd: pam_env(gnome-screensaver:setcred): non-alphanumeric key 'alias aumix=padsp aumix' in /etc/environment', ignoring unix2_chkpwd: pam_env(gnome-screensaver:setcred): non-alphanumeric key 'alias timidity=timidity -Oe' in /etc/environment', ignoring
If I reboot, it works corectly until I run one of those two. Not sure about any other audio type of program. Bad updates, virus, or something else?
I am using opensuse 11.2 Gnome. Screensaver is spoiling video streaming and I have to manually stop it every time. There are options in media players to stop screensaver but when I watch videos online it seems like there is no global option to stop it. Is there a way to resolve this issue?
I've just installed 11.1 and so far things seem to work OK. When I left the machine the screen saver kicked in and wouldn't let meback on with my password I chose during installation (and the only password I chose!) Re-booting the machine sorted the problem...until next time! I have now disabled the lock out for the screen saver so things ought to work now, but why did it do this? New with openSuse!
Does anyone now if SMplayer is able to disable screensaver when playing video? There is an option to have SMplayer to do so within the settings menubut that does nothing, screensaver is still being activated after 5 min. Anyone managed to have the player do this? I am on KDE4 by the way.Kaffeine does disable screensaver but I do not like the KDE4 Kaffeine.
I think it is very annoying, that kde slideshow screensaver does not rotate images according to the jpeg exif information. I've found a bug report from 2005 for this topic Bug 103282 - no exif-rotation in slideshow) but as far as I see it still does not work. Any idea how can I set up kde to rotate the images?
got a suspend problem with OpenSuse 11.3. I configured the powersave module that whenever I close down the screen of my laptop it suspends to ram. Works fine so far except when the screensaver is active. It just stays on when I close down the lid.
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.
When I resume my computer from suspend (or after it goes to screensaver), I am sometimes unable to log back in. The message on the lock box simply says 'Timeout has expired' or something to that effect.There is no way to get around that, all I can do is cold-boot loosing all the work I was doing (unsaved).I do not have desktop effects enabled.Running Gnome 2.32, OpenSUSE 114., n550 proc and x3150 Intel GMA
when attempting to open screensaver settings in LXDE, the window pops up briefly for a second and then closes. Anyway I can fix this? I would post a debug log if I knew how to open this app from within terminal
So im not sure exactly what caused this but when playing movies through the xine-ui has stopped keeping my system active causing my monitor to turn off. This started happening about a week ago and I cant remember installing any xine related updates, but was wondering if anyone knows how to make xine keep the system active to prevent this. I could have sworn there was an option for this but I cant seem to find it anymore.
Today I found out how to change theme in OpenSuse 11.3 64 bit. I'm running KDE 4.4. Naturally I went to KDE-Look.org and trawled it through for eye-candy. I got this HAL-9000 boot splash: HAL-9000 KDE-Look.org
Its a .gz file and uncompressed its called .xpm, I think its just an image, that I should put somewhere, but I don't know where. I tried the bootloader settings through yast, though it didn't tell me anything.
Secondly I got a screensaver, which I'm supposed to compile and install: KCometen4 KDE-Look.org
I tried following these instructions, as best as I could:
Code:
KCometen4 also comes with a simple configure script that should work for a generic local install. If it doesn't suit your needs, you will need to edit the cmake settings by hand.
Quick installation steps:
Cmake's equivalent to 'make distclean' is 'rm -rf build'.
If you do a local installation, you might not see KCometen4 in the Screen Saver Settings module. In that case, you will need to do one of two things.
First, you can set the $KDEDIRS environment variable in your X session startup script so it includes your local installation prefix:
Or second, you can set this for all users by adding your local installation prefix to /etc/kde4rc:
After that, you may need to manually refresh the system configuration cache by running 'kbuildsycoca4'. KCometen4 should now appear in Screen Saver Settings.
So I installed kdebase-workspace-devel but I couldn't find libqt-opengl-dev, but it didn't seem to be a problem, according to the console output:
Code:
It mentions some Q_WS_WIN, Q_WS_QWS and Q_WS_MAC, that it doesn't find. Could that be the problem.
I tried to see if the new screensaver got into the screensaver menu, it didn't.
