Gnome-screensaver ignores input when fading to black

Hi,
I'm experiencing the following bug:
https://bugzilla.gnome.org/show_bug.cgi?id=594082
It looks like it's now fixed in Fedora. Anyone having the same problem?
Thanks.

Fair enough but it's not clear from that if it got fixed by a Fedora dev or upstream... either way, bug reports should go to gnome-screensaver bugzilla.
Also see this:
https://bugzilla.redhat.com/show_bug.cgi?id=629419
https://bugzilla.redhat.com/show_bug.cgi?id=626472
Would be nice to know if Fedora applied any patches in F11, but I don't get where to look that up atm (stopped here.
Something else, what graphics are you using? nvidia proprietary here.
typo
Last edited by hokasch (2010-09-03 13:34:12)

Similar Messages

Gnome-screensaver versus xscreensaver

Some where along the line, I think when Gnome was updated to 2.22, gnome-screensaver was installed in addition to the existing xscreensaver. From what I have read on the internet, it seems that gnome-screensaver is a replacement for xscreensaver and that gnome-screensaver is not dependent upon xscreensaver. Correct?
When I select "System" --> "Preferences" --> "Screensaver", it brings up the preferences dialog for gnome-screensaver. However, when I do a ps -e command, it lists xscreensaver as running and doesn't list gnome-screensaver. So it appears as though only xscreensaver is running.
What is the recommendation on this? Should I be running one or the other and un-install the one not being used?
I have been experiencing random hard lock ups which just started recently. I always notice these lock ups after the screensaver kicks in and I am trying to go back to the active mode. At this point I have a totally black screen and the computer is locked up. Can't ssh into it, can't use Ctrl-Alt-F1 to get to a console screen or anything. The only thing I can do is hit the reset button. Could this be a conflict between gnome-screensaver and xscreensaver? I know other threads have suggested that these lock ups are kernel releated, but could this be part of the problem also?
Any guidance here would be appreciated.
Thanks
Pudge

They are separate screensavers now, not related to each other.
I would say that if you are running gnome, go with gnome-screensaver, it is integreated to gnome quite well nowdays.
If running with other DE or window manager, stick with xscreensaver and ditch gnome-screensaver. You can keep both installed, but running both in same time would cause problems. If you have only one running, that should not cause problems.
Try to configure xscreensaver to use only blank screen and see if it still crashes?

Help, where is "Ignore accidental input when typing" checkbox on the PC?

Hi all,
I'm new to Macs and just got myself a new MBP Corei7. It's running Windows 7 great, however I find the track pad just too sensitive when I type on the keyboard, I keep inadvertently touching the track pad with my palm or thumb as I type causing the cursor to jump.
Under the Bootcamp help, there's an entry:
"Change the following under “Palm Rejection”:
Ignore accidental input when typing: Select to make the computer ignore the trackpad while you type."
But my Trackpad tab in the Bootcamp settings within Windows 7 doesn't have this option/check box. I made sure that I did have the latest BootCamp 3.1 drivers. But I can't find it anywhere. It says on a support thread here on the Mac side that that option has been removed on the Mac side of the Track Pad settings and enable by default (on late 2009 MBP)- can anyone confirm that for the PC side of things, because I've already done 4 typos on this message due to accidentally touching the pad while typing!
Thanks,

Upon further examination, I don't believe it's accidental trackpad touching that is the culprit here. I am typing in such a way that I am very VERY mindful of not touching the trackpad and occasionally I still get the "cursor jump" to another portion of the screen (even though I am aware that I have no part of my hand in contact with the trackpad. I fact I believe that "ignore accidental input when typing" is enabled by default across both PC and Mac trackpad drivers, I can rest my palms and upper thumbs on the track pad and it still has no effect on my typing. I think this cursor jumping might be something else. If I un-check all the trackpad options in the BootCamp track pad tab (ie; tapping...) then the problem goes away - which leads me to believe maybe the tapping is sensing some part of my hand (even though its not touch) that the poximity of some part of my hand is triggering a click to some portion of my screen.

Can't unlock gnome-screensaver, dialog won't come up.

Hi all,
I'm having an issue with gnome-screensaver, when the computer locks, it won't unlock, 4 times out of 5. The unlock dialog never appears, it acts as if I don't even send any input. In order to get past the screensaver, I need to switch to tty1, log in, and killall gnome-screensaver. It does occasionally give me the unlock dialog, and I'm not sure why it does that 20% of the time. My issue seems to be a duplicate of this, although I don't want to bump an old thread.
$ gnome-screensaver --debug --no-daemon 2>&1 | tee gnome-screensaver.txt
http://pastebin.com/aZmLK3yF
Edit: I should say, this started a few weeks ago, seemingly without reason; I was using gnome-screensaver 2.30.0-?, but yesterday pacman updated gnome-screensaver to 2.30.0-5, and this issue is still occurring.
Any help or suggestions would be appreciated.
Last edited by sargk (2010-09-29 15:16:39)

Ok, so does it only happen when it times out or if you issue the command xscreensaver-command -lock?
Which screensaver do you have running?
I was just thinking that perhaps another program is being run when the screensaver activates that is stealing that focus from the screensaver.
I know that there are some that you have to move the mouse to a certain corner or press a certain key combination in order for it to release it's lock. (can't think of any names though. )

Gnome-screensaver Fade Stopped Working

Hey guys,
Just did a pacman upgrade (after about two months without net access!), and one of the funny things I've noticed is that gnome-screensaver no longer fades to black when locking the screen. After a couple of seconds it just goes black. I think it's the same issue that's been listed for Ubuntu here: https://bugs.launchpad.net/ubuntu/+sour … bug/522806, however on that bug report it says the problem was fixed in version 2.29.90-0ubuntu2 (presumably an Ubuntu-specific fix), while I'm running 2.30.0-1. I am running nVidia drivers, so it fits in with the bug description though.
Has anyone else come across this problem? Is there a fix for it yet that we can use?
'Shady

Ooops, wrong link to AUR, my bad
As gnome-screensaver is still running after the update,
it must be restarted so that new program is loaded in memory;
a "killall gnome-screensaver && gnome-screensaver" do the job, no need to restart X or the system
The xscreensaver dependency is not weird, you need it to build the package,
it is only an optional dependency for the binary/pre-built package.
You can remove xscreensaver after yaourt.

Premiere Elements 13, on Windows 7 64 bit, Problem fading to black at end of video.

With Premiere Elements 13, on Windows 7 64 bit, I am attempting to end a video with a fade to black transition. For whatever reason, it is fading to black then returning. Yes, I have tried it all three ways right, left and in between, but the it keeps fading out then in. And yes the transition is at the very end of the clip.

morrisst
I have Premiere Elements 13 on Windows 7 64 bit.
When I apply the Dip to Black video transition to the last Timeline clip, the Alignment is Left Clip. You have been there and done that.
Can you post a screenshot of what you are seeing when the Dip to Black transitions stops on your Timeline?
When I do as you have suggested I see this
Have you expanded the Timeline with the -+ slider above the Timeline and inspect the end of the clip as well as
other track content above or below, do you detect an fragments that might be a factor in what you are seeing?
If you start a new project, do you get the same result?
Could you post a screenshot displaying what you are seeing with the Dip to Black video transition placed at the end
of the last clip on your Timeline (Alignment: Left Clip)?
Thank you.
ATR
Add On..I posted this reply earlier today but somehow the last part was not included in the thread. So I am adding that now to the original content.

Gnome-screensaver 2.30.0-1 : Can't unlock the screen

Starting about two weeks ago, I haven't been able to unlock my screen after the screensaver kicks in. When I move the mouse, the desktop background image flashes for a split second, the mouse cursor is visible, and then the screensaver resumes: the prompt to unlock the screen never appears. The only way to get back to the desktop is to kill gnome-screensaver. I've tried re-installing it, and all of it's dependancies (with the exception of libgl as it conflicts with the nvidia package). As I expected, no luck there, but I didn't know what else to do...
Here's the output of "gnome-screensaver --no-daemon --debug"
http://pastebin.com/1B4UZaDj
I don't know if this helps, but here's some interesting output from LD_DEBUG=libs gnome-screensaver:
7559: /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
7559: /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: error: symbol lookup error: undefined symbol: gtk_module_display_init (fatal)
7559: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
7559: /usr/lib/gio/modules/libgvfsdbus.so: error: symbol lookup error: undefined symbol: g_module_check_init (fatal)
7559: /usr/lib/gio/modules/libgvfsdbus.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
I hope that doesn't steer anyone in the wrong direction; I just learned about LD_DEBUG last night so I don't know if it's of any help.
Any help will be appreciated.

My gtk2 was already up to date (gtk2 2.20.1-2). I tried removing it, re-installing it, and then running ldconfig, but the issue is still present.

Gnome-screensaver && slim archlinux theme

Hi all,
I'm using SLIM + the archlinux theme as my login manager. I like the very simple but beautifull layout.
As screensaver (read: as window-lock-application) I'm using xscreensaver, but I'm tired of the ugly interface. I mean, we live in 2009, not back in the nineties where those ugly interfaces were a common thing! Gnome-screensaver is a better-looking screensaver/screenlocker, but with the background and the grey login window + buttons it's still not that nice.
As you all can guess; is there a way to get gnome-screensaver having an interface just like the SLIM loginmanager + archlinux theme? The black screen + nice logo + just a simple password-field?
I would love this!
Regards

Wonder is likely correct; these are tumultuous times for GNOME fans. If KDE fans thought they had it bad during the transition to version 4, in many ways I think the jump to GNOME 3 and gnome-shell has been even more severe. With KDE, many of missing features were at least expected to be reinstated in subsequent versions; for GNOME 3, many of the features, as we know them, will simply disappear.
Last edited by thayer (2011-05-29 17:17:20)

IPhone 5 screen went green and blue and then faded to black?

I was on my iphone and had messages open and than the screen just froze and turned blue and green and than slowly faded to black and now won't turn on. When i plug it into the wall it doesn't do anything. The phone is still on because my dad called the phone and it still rings. It has a glow to it too when it is in the dark so the screen must be on or something, i don't know. Any help please!!

See Here for > Frozen or unresponsive iPhone
Try this First... No Data will be Lost...
Press and Hold the Sleep/Wake Button and the Home Button at the Same Time...
Wait for the Apple logo to Appear...
Usually takes about 15 - 20 Seconds... ( But can take Longer...)
Release the Buttons...

Inhibit gnome-screensaver

I want to inhibit gnome-screensaver from starting while I run mplayer. There is a command "gnome-screensaver-command --inhibit" which should work but even with that running I still have gnome-screensaver starting. I also can't get any dbus based commands/scripts to stop it.
I am running XFCE. Does that command work other XFCE users? How about GNOME users?

Allan wrote:
I want to inhibit gnome-screensaver from starting while I run mplayer. There is a command "gnome-screensaver-command --inhibit" which should work but even with that running I still have gnome-screensaver starting. I also can't get any dbus based commands/scripts to stop it.
I am running XFCE. Does that command work other XFCE users? How about GNOME users?
Though I use xscreensaver, I just installed gnome-screensaver to see what was up. I tested your python DBUS script, and it seems to work fine here. The inhibit cookie is being created (I threw in a print statement just to see the value), and it is being observed until the selected video finishes. As soon as the video finishes, mplayer exits and the screensaver kicks in as expected.
I'm not sure why you are getting different results, but you can run this from the command line or in a script as it might be helpful for testing:
dbus-send --session --dest=org.gnome.ScreenSaver --type=method_call --print-reply --reply-timeout=20000 /org/gnome/ScreenSaver org.gnome.ScreenSaver.Inhibit string:"MPlayer" string:"Watching video"
It's pretty much the command-line version of what you have in your python DBUS-object code.
By the way, I only passed the 'file' argument to the script when testing, meaning I did not pass mplayer any other options via the python script. I don't know if that is relevant or not.
The gnome-screensaver command-line worked as well:
gnome-screensaver-command -i -n mplayer -r test
MPlayer used to have a command that simulated activity (−heartbeat−cmd) but it doesn't seem to be available anymore (at least not in the Arch version). Also, if you used xscreensaver, MPlayer's '-stop-xscreensaver' command is available.
Of course other alternatives could include simply killing gnome-screensaver and then restarting it via a script, though that may not be as elegant as using built-in commands or DBUS signals.
Edit:
Tested with gnome + openbox here. I only have XFCE-WM4 installed (not the full XFCE desktop) and I didn't test that yet.
Last edited by MrWeatherbee (2008-01-24 15:06:25)

Mplayer doesn't stop gnome screensaver

Hi !
I'm using the option stop-xscreensave="yes" in mplayer config but after about 5 minutes of playing the movie the screen fades away and i have to login in order to get to mplayer again
How can i stop this from happening ?
Thanks a lot !

Here's my tv watching script..
#!/bin/sh
# inhibit the screensaver and output to the tv (display 0.2)
# gnome-screensaver-command -i -r "Watching Videos" &
xscreensaver-command -exit
DISPLAY=:0.2 mplayer -fs "$@"
# killall gnome-screensaver-command
xscreensaver -no-splash &
You'ld probably want something more like
#!/bin/sh
# inhibit the screensaver and output to the tv
gnome-screensaver-command -i -r "Watching Videos" &
mplayer -fs "$@"
killall gnome-screensaver-command
Not sure if it is the most efficient way, but I believe it worked.
You would just copy that to a file named tv.sh (or tv or watch or foo), make the file executable (chmod 755 tv.sh), put it in your path somewhere (/usr/local/bin if that's in your path), and then type tv.sh filename to start watching (but I imagine you already knew all that).
If you use a graphical player. I dunno. The player might have an option? Or else just run the `gnome-screensaver-command -i -r "Watching Videos"` part in a term and kill it when your done. Or run it from an Alt-F2 dialog with & and kill it when your done might work. Something to tinker with..

[SOLVED]Gnome-screensaver not kicking in

Hi, since the recent update gnome-screensaver hasn't been kicking in.
I can lock my screen with gnome-screensaver-command -l manually and I see that the gnome-screensaver process is running but it just won't activate itself after 5 minutes. I can leave my computer on for an hour and the screensaver doesn't kick in.
Does anyone else experience this ?
Last edited by moljac024 (2009-01-28 13:41:20)

I have ocassional locks when trying to unlock the screensaver. The solution for me is to kill this application.
It seems that the application has problems with libgnomekdbui. Having a look at /var/log/everything.log shows me lines like this:
Dec 3 17:32:01 t23 gnome-screensav[16328]: segfault at 11 ip b7d679c6 sp bfc329f0 error 4 in libgnomekbdui.so.3.0.0[b7d61000+f000]
Dec 3 17:32:02 t23 gnome-screensav[16329]: segfault at 19 ip b7d4a9c6 sp bf814dd0 error 4 in libgnomekbdui.so.3.0.0[b7d44000+f000]
Dec 3 17:32:04 t23 gnome-screensav[16330]: segfault at 19 ip b7d3a9c6 sp bfe053c0 error 4 in libgnomekbdui.so.3.0.0[b7d34000+f000]
Dec 3 17:32:04 t23 gnome-screensav[16333]: segfault at 19 ip b7ea29c6 sp bf86f630 error 4 in libgnomekbdui.so.3.0.0[b7e9c000+f000]
Dec 3 17:32:05 t23 gnome-screensav[16334]: segfault at 19 ip b7e4e9c6 sp bfe1bbe0 error 4 in libgnomekbdui.so.3.0.0[b7e48000+f000]
Dec 3 17:32:06 t23 gnome-screensav[16335]: segfault at 11 ip b7e529c6 sp bfe1fbe0 error 4 in libgnomekbdui.so.3.0.0[b7e4c000+f000]
Dec 3 17:32:06 t23 gnome-screensav[16336]: segfault at 19 ip b7e979c6 sp bfb64120 error 4 in libgnomekbdui.so.3.0.0[b7e91000+f000]
Dec 3 17:32:07 t23 gnome-screensav[16337]: segfault at 19 ip b7f2d9c6 sp bfcf8ac0 error 4 in libgnomekbdui.so.3.0.0[b7f27000+f000]
Dec 3 17:32:07 t23 gnome-screensav[16338]: segfault at 19 ip b7d399c6 sp bf8045c0 error 4 in libgnomekbdui.so.3.0.0[b7d33000+f000]
Dec 3 17:32:08 t23 gnome-screensav[16339]: segfault at 19 ip b7f009c6 sp bfccda90 error 4 in libgnomekbdui.so.3.0.0[b7efa000+f000]
Do you maybe have something similar?
Last edited by ss2 (2008-12-03 17:21:07)

Gnome screensaver keeps starting in openbox

I don't know what config is starting it, but it is driving me crazy (It tries to run when I'm playing games). I couldn't find it in ~/.config/openbox/* or in any of the ~./X* files. I use kdm for logging on (my gf would panic if she ever saw a terminal login)
pstree:
init─┬─6*[agetty]
├─console-kit-dae───63*[{console-kit-dae}]
├─crond
├─cupsd
├─3*[dbus-daemon]
├─2*[dbus-launch]
├─dcopserver
├─ddclient
├─gconfd-2
├─gnome-screensav
├─gnome-settings-───{gnome-settings-}
├─gvfs-fuse-daemo───3*[{gvfs-fuse-daemo}]
├─gvfsd
├─hald───hald-runner─┬─hald-addon-acpi
│ ├─hald-addon-inpu
│ └─2*[hald-addon-stor]
├─kded
├─kded4
├─kdeinit───klauncher
├─kdeinit4─┬─kio_file
│ └─klauncher
├─kdm─┬─X
│ └─kdm───openbox─┬─firefox───5*[{firefox}]
│ ├─xterm───dash
│ └─xterm───pstree.x11
├─mpd───3*[{mpd}]
├─ntpd
├─portmap
├─privoxy
├─rpc.mountd
├─rpc.statd
├─sshd
├─start_kdeinit
├─syslog-ng
└─udevd

As I understand it, if you want to use gnome-screensaver, you need to load gnome-settings-daemon and perhaps gnome-settings-daemon-helper
I don't have an Arch box around to test, but I believe this will go ahead and load Nautilus on you as well, which will draw the desktop and handle your background, fonts, gtk, etc. I've read you're able to turn this behaviour off with gconftool-2 -s -t bool /apps/nautilus/preferences/show_desktop false
The screensaver config dialog is started with the command gnome-screensaver-preferences

Getting a "pop" when fading titles

never particularly noticed this before ... when fading (using cross dissolve) titles in & out, i'm observing a pop at the point where the transition begins. the fade is not smooth. there's a visible of a degradation in quality at the the first frame of the transition. i can even step frame or jog through and observe it. thought maybe it was a render issue but it's not that. i'm using the boris title 3D. it does not happen when i use fcp's text & lower third titler but i need more firepower so perhaps it's a boris thing. thought i could work around it by key framing the opacity to fade the titles in & out but that produces the same pop. very bizarre. any ideas? thanks.

even in safe mode there's no indication that it needed to be rendered but rendering those titles fixed the problem. interstingly there's some titles that play fine with no rendering using the same exact everything, no rhyme or reason ...

Gnome-screensaver doesn't autolock the screen in gnome 2.26 in testing

Under gnome 2.26 in testing, gnome screensaver no longer auto locks the screen after the specified time. The screensaver doesn't even come up either. I have to manually switch off the monitor.
Anyone else seeing this bug? How can I find out what's going wrong?
Last edited by hussam (2009-03-31 04:46:48)

Just start gnome-screensaver on a terminal (it starts up in daemon mode by default).
That's it.For a test you can set screensaver time to 1 min.
A random discovery I am happy for
Last edited by nema.arpit (2010-01-11 17:28:09)

Gnome-screensaver ignores input when fading to black

Similar Messages

Maybe you are looking for