This bug was fixed in the package gnome-screensaver - 2.28.0-1ubuntu5
---
gnome-screensaver (2.28.0-1ubuntu5) lucid; urgency=low
[ Chris Coulson ]
* debian/patches/10_legacy_scrsvr_inhibit.patch:
- Re-write to not use XTest to simulate fake key-presses in order
to reset
Thanks for testing. I've reopened the karmic task on bug 428884 now,
which will have to remain open until we think of a less problematic
solution
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a
** Branch linked: lp:ubuntu/karmic-proposed/gnome-screensaver
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am able to reproduce this with Open Office Writer, Calc, and Impress
(seems to trigger Alt-F), but tried with several other apps with
triggers for Alt-F, such as a Firefox, Code::Blocks, gedit, ampng
others, and I got nothing. It also seems that if it actually triggered
the Alt-F event, it would
I can confirm this behavior with blueproximity, OO and gnome-
screensaver.
Running the following batch script in a terminal window, then giving
focus to OO Writer clearly shows that the problem is gnome-screensaver-
command, not blueproximity:
#!/bin/bash
for (( ; ; ))
do
As a workaround I use the following proximity command in blueproximity:
xdotool key Scroll_Lock xdotool key Scroll_Lock.
Hopefully gnome-screensaver-command -p isn't issued by other apps I'm
running.
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Confirmed
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided = High
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: gnome-screensaver (Ubuntu Karmic)
Importance: Undecided
Status: New
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is caused by my recent change to fix bug 428884. I'm slightly
bewildered why we haven't seen issues like this before, as the method I
chose for inhibiting the screensaver is used elsewhere already (eg,
Totem uses the same method when not running under GNOME, for example
when it runs under
** Branch linked: lp:~ubuntu-desktop/gnome-screensaver/ubuntu
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Bumping the importance of the karmic task, as we're getting some
duplicates now and this is a regression in the stable release
** Changed in: gnome-screensaver (Ubuntu Karmic)
Importance: High = Critical
--
gnome-screensaver-command -p triggers keyboard event
Urgh, my last comment got truncated at the start there.It was meant to
read Bumping the importance of the karmic task, as we're getting some
duplicates now and this is a regression in the stable release
--
gnome-screensaver-command -p triggers keyboard event
I've pushed a change to bzr which fixes this issue. Unfortunately, it
breaks screensaver inhibiting again and will reopen the original bug
428884 due to a xorg regression, so I've not uploaded it yet:
http://bugs.freedesktop.org/show_bug.cgi?id=25855.
Once that xorg bug is fixed, then screensaver
Ok, my messages aren't getting truncated, but my browser does not
display them correctly. Sorry for the noise there!
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Accepted into karmic-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: gnome-screensaver (Ubuntu
As this is a regression introduced in an SRU, the normal 7-day waiting
period is waived; can be copied to -updates as soon as it's built.
Please test to confirm that this does correct the regression.
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
With the new package (2.28.0-0ubuntu3.3) I don't get this bug anymore.
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Thanks for the quick fix!
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
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.ubuntu.com
** Tags added: verification-done
** Tags removed: verification-needed
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This bug was fixed in the package gnome-screensaver - 2.28.0-0ubuntu3.3
---
gnome-screensaver (2.28.0-0ubuntu3.3) karmic-proposed; urgency=low
* Back out debian/patches/10_legacy_scrsvr_inhibit.patch for now
as the patch causes a regression, leading to menus randomly popping
21 matches
Mail list logo
