Does https://www.jwz.org/xscreensaver/man1.html#8 help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/528094
Title:
lock screen fails with xscreensaver
To manage notifications about this bug go to:
Here is a workaround. Works with Ubuntu 12.04 LTS, 32 bits.
Using Ubuntu Software Center or Terminal, install xscreensaver-gl-extra
and xscreensaver-data-extra
Click OK to both prompts asking to turn-off Gnome Daemon and to start
xscreensaver-daemon respectively.
If you want to manually lock the
Confirming this bug is still present in Ubuntu 12.04 LTS, 32bits, Unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/528094
Title:
lock screen fails with xscreensaver
To manage notifications about
I am using Ubuntu 11.10. Pressing the menu command for lock screen does
nothing. Using the keyboard shortcut CTRL+ALT+L give the following error
popup:
Couldn't execute command: gnome-screensaver-command --lock
Verify that this is a valid command.
--
You received this bug notification because yo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xscreensaver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/528094
Title:
It looks like this should be part of the xscreensaver package, so that
the lock screen menu item will work. Either that, or the Session Menu
should look for xscreensaver vs gnome-screensaver, and enable the
appropriate method. I am assuming the DBUS object is created by gnome-
screensaver, so the e
Since you have disabled the gnome-screensaver, the dbus object
org.gnome.ScreenSaver is not created while the Gnome starts.
We need to create the dbus object org.gnome.ScreenSaver and implement
the Lock method.
I use the below python script to create the org.gnome.ScreenSaver.
--- mys
I expected something like that to happen--it seems like with the
.service file you listed, the destination object now calls 'xscreensaver
-lock' as the executable, which does what is expected, but the "message
name" = "org.gnome.ScreenSaver.Lock" is not recognized and no reply is
made via DBUS. So
One further detail about this that I didn't notice until now: When
running the dbus-send command, I get a DBus error as follows:
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy
Excellent Carlos!
I made a file called:
/usr/share/dbus-1/services/org.gnome.ScreenSaver.service
with the following contents:
[D-BUS Service]
Name=org.gnome.ScreenSaver
Exec=/usr/bin/xscreensaver-command -lock
And now the session menu works. It looks like this needs to be added to
the xscreensave
** Changed in: xscreensaver (Ubuntu)
Status: Invalid => New
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
In addition to Brian's comment dated 2010-06-17: I got the session menu
to lock the screen with xscreensaver. In the file
/usr/share/dbus-1/services/org.gnome.ScreenSaver.service I modified the
Exec line to the following:
Exec=/usr/bin/xscreensaver-command -lock
and the dbus-send command worked.
Thanks Nadim.
I have upgraded now to Lucid on a new machine, and the bug is still
present. I did notice that Ctrl-Alt-L locks the screen with xscreensaver
now :)
I tried to fix the DBus issue, but I am in the same boat as far as knowledge
about what's happening there. In
https://bugs.launchpad.n
Just looked at the code a little, though I'm not really familiar with
the internal Gnome architecture at all. It looks like indicator-session
is where things go down. session_service.c is where the Lock Screen
item is actually provided for the menu, and lock-helper.c (function
lock_screen()) is w
To answer your question, Brian, yes, it appears this bug is still
present in Lucid. I stumbled on this bug report after noticing the
problem (I also refuse to use the broken gnome-screensaver). It looks
like ctrl-alt-l works correctly in Lucid, but the "Lock Screen" session
menu command does not.
[1] indicates that indicator-session calls gnome screen saver directly.
It should do whatever ctrl+alt+l does so that it would work with
xscreensaver.
Why I'm interested? Switch user does not lock current session so I can
switch between users without entering a password as long as xscreensaver
tim
vamped wrote in post #21:
believe that is Ubuntu's default lock-screen key-combination.
It works for me (activates xscreensaver lock) and I have not added it as a
custom command. Moreover, I'm using the default visual-effects.
Yes, that is the default lock-screen combo. It didn't work in Jaunty
Brian wrote in post #14: Also, if I run xscreensaver-command -lock it
works correctly. Pressing --L works but only because I added
it in Compiz as a command, which runs xscreensaver-command -lock.
Otherwise it did not work.
I believe that is Ubuntu's default lock-screen key-
combination. It works
** Changed in: indicator-session
Importance: Undecided => Wishlist
** Changed in: indicator-session
Status: New => Confirmed
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I think you may misunderstand the bug.
xscreensaver has no problem, it is the session menu that has a bug. I
cannot get the screen to lock from the session menu when I have replaced
gnome-screensaver with xscreensaver. The session menu only functions
properly if gnome-screensaver is used. Since gn
I have also verified that the timer works on xscreensaver.
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I have attempted to duplicate your issue on Lucid however the issue did
not occur. I may have done something different then you though.
In attempt to recreate the bug but failed I did the following steps.
sudo apt-get install xscreensaver.
sudo apt-get remove gnome-screensaver.
Launched screen-s
** Bug watch removed: GNOME Bug Tracker #316654
https://bugzilla.gnome.org/show_bug.cgi?id=316654
** Changed in: indicator-session
Status: Incomplete => Invalid
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you
Oh also the launchpad bug report for gnome-screensaver:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/22007
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Upstream gnome-screensaver bug marked WONTFIX:
https://bugzilla.gnome.org/show_bug.cgi?id=316654
That's why I use xscreensaver. If they fix that bug (or Ubuntu forks and
fixes it) I'll use gnome-screensaver. I actually would love to use
gnome-screensaver, but only if it works. It's been almost hal
"(the bug that upstream marked WONTFIX)"
Do you have that upstream link.
"# How many monitors do you use?
1 or 2"
When does it happen with duel monitors or without duel monitors or does
not matter.
"# If it is a laptop, do you use an external screen?
Sometimes"
Does it happen in one case but no
# What desktop environment does this problem occur in? (GNOME, XFCE, KDE, etc.)
GNOME
# Do you use visual effects? (System/Preferences/Appearance/Visual Effects)
Yes--Compiz with custom effects
# Does the problem still occur if you disable visual effects?
Yes
# Does the problem still occur if yo
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it without more information.
Please include the information requested at
https://wiki.ubuntu.com/DebuggingScreenLocking as separate attachments.
** Changed in: indicator-session
St
I still cannot lock screen from the session menu when running with no
xorg.conf.
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
This is the log after deleting (renaming) xorg.conf then doing a cold
reboot to allow autodetect.
** Attachment added: "After deleting xorg.conf and cold reboot"
http://launchpadlibrarian.net/39824115/Xorg.0.log
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/39823877/xorg.conf
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/39823865/Xorg.0.log
--
lock screen fails with xscreensaver
https://bugs.launchpad.net/bugs/528094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please attach your X server configuration file
(/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the
bug report as individual uncompressed file attachments using the
"Attachment:" box below. Could
33 matches
Mail list logo
