The following dbus calls seem to no longer work (e.g. screensaver is not
deactivated or timeout reset):
$ dbus-send --session --type=method_call --dest=org.gnome.ScreenSaver /
org.gnome.ScreenSaver.SimulateUserActivity
$ dbus-send --session --type=method_call --dest=org.gnome.ScreenSaver
/org/
** No longer affects: indicator-session (Ubuntu)
** No longer affects: indicator-session (Ubuntu Quantal)
** No longer affects: indicator-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067515
This bug was fixed in the package gnome-screensaver - 3.6.0-0ubuntu2
---
gnome-screensaver (3.6.0-0ubuntu2) quantal-proposed; urgency=low
* debian/patches/28_blocking_return.patch:
- Correctly reply so the client doesn't block waiting (lp: #1067515)
-- Sebastien BacherThu,
This bug was fixed in the package gnome-screensaver - 3.6.0-0ubuntu2
---
gnome-screensaver (3.6.0-0ubuntu2) quantal-proposed; urgency=low
* debian/patches/28_blocking_return.patch:
- Correctly reply so the client doesn't block waiting (lp: #1067515)
-- Sebastien BacherThu,
Tested with package from -proposed, this issue is now resolved!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067515
Title:
Lo
Hello Tim, or anyone else affected,
Accepted gnome-screensaver into quantal-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/gnome-
screensaver/3.6.0-0ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
** Changed in: gnome-screensaver
Status: Unknown => Fix Released
** Changed in: gnome-screensaver
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067515
Title:
Ok, after IRC discussion that seems right, I've forward to
https://bugzilla.gnome.org/show_bug.cgi?id=686400 and will upload
** Bug watch added: GNOME Bug Tracker #686400
https://bugzilla.gnome.org/show_bug.cgi?id=686400
** Also affects: gnome-screensaver via
https://bugzilla.gnome.org/show
** Description changed:
- Steps to reproduce
+ Impact:
+ Locking and other actions are delayed when used for a second time
+
+ Test Case:
1. Login
2. Lock screen from system menu, then unlock
3. Lock screen again from system menu
This time the lock dialog takes around 30secs to be disp
** Changed in: indicator-session
Status: New => Invalid
** Changed in: indicator-session (Ubuntu Quantal)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067515
Ok, looking a bit to it, doing:
dbus-send --session --print-reply --dest=org.gnome.ScreenSaver
/org/gnome/ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity
blocks on the current code
The patch there "fixes" the issue, I'm not sure it's right though, I
would appreciate comments of people kno
** Summary changed:
- Locking from user menu fails second time (g-s SimulateUserActivity doesn't
return)
+ Locking from user menu fails second time (gnome-screensaver
SimulateUserActivity() doesn't return)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
interesting, calling SimulateUserActivity() in d-feet leads to block the
ui as well, really looking like a gnome-screensaver issue...
** Summary changed:
- Locking from user menu fails second time
+ Locking from user menu fails second time (g-s SimulateUserActivity doesn't
return)
--
You rece
Thanks for the debugging Jason, I wonder if that makes it a gnome-
screensaver bug then, it seems like SimulateUserActivity should give a
reply...
** Also affects: indicator-session
Importance: Undecided
Status: New
** Changed in: indicator-session (Ubuntu)
Importance: Undecided => L
The attachment "indicator-session_reply_timeout_workaround.debdiff" of
this bug report has been identified as being a patch in the form of a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. In the event
that this is
Seems to fix it here, attaching a debdiff with the workaround. Curious
if this is due to some change in dbus, I know quantal included at least
the eavesdropping changes (though I would think we should be able to get
the reply to our own method call).
** Patch added: "indicator-session_reply_timeou
Don't think this is a bug in indicator-session. Basically indicator-
session is just calling two dbus methods on org.gnome.ScreenSaver; Lock
and SimulateUserActivity. It seems that the SimulateUserActivity call is
not returning immediately. I can illustrate this with a simple script:
#!/bin/bash
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-session (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/1067515
T
Actually appears something is hanging around after unlocking, that
blocks indicator session for a bit. If you wait a few minutes between
unlock and locking again (or log-out etc), the lock screen appears
without delay.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
19 matches
Mail list logo
