Re-opening. This shouldn't be marked Fix Released as the fix is not
present in Lucid.
** Also affects: hamster-applet (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: hamster-applet (Ubuntu Karmic)
Status: New => Fix Released
** Changed in: hamster-applet (Ubuntu
** Branch linked: lp:ubuntu/karmic-security/hamster-applet
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
This bug was fixed in the package hamster-applet - 2.28.0-0ubuntu1.1
---
hamster-applet (2.28.0-0ubuntu1.1) karmic-security; urgency=low
* SECURITY UPDATE: broken screen-locking idle timeout (LP: #448438)
- debian/patches/01-fix_inhibit_cookie: fix screensaver inhibit issue.
--
Andreas:
Those are different issues. Could you please open two new bugs for them,
and we'll get them investigated.
Thanks.
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of
The updated hamster-applet from comment #21 does not seem to fix
anything for me:
Still, the Screenblanker sometimes "forgets" to kick in. In these cases,
the moment I move the mouse again, the screen fades out as if the
Screenblanker is about to activate, but then switches back on (probably
becau
> I've built an updated hamster-applet package in the following PPA:
>
> https://launchpad.net/~mdeslaur/+archive/screen-locking
>
> Please try it, along with the gnome-screensaver security update for
> karmic that came out a couple of days ago, and give feedback here.
I gave it a shot, tested
Tom:
Sorry, I didn't meant the fix was ugly, I just meant releasing an update
with it is less ideal than the type of solution Chris was proposing. A
bad choice of words on my part.
This is the commit I put in the test package:
http://git.gnome.org/cgit/hamster-
applet/commit/?h=gnome-2-28&id=a3b
Chris - if you are up to the task, I can well suggest looking in two places.
First the DBUS should be able to survive invalid listeners.
Second, it might be useful that screensaver / gnome session DBUS API
differentiate between a user-requested screen lock and idle timeout, because
that is what
Marc - Ok, I'm happy with going with the current solution in Karmic for
now then, as long as it solves the issue. It also has minimal regression
potential for hamster-applet.
I'll have a think about a longer term solution over the next few days
though, and propose that to upstream.
Thanks
--
id
I'm looking forward too.
Marc - where can i see the ugly fix you are referring to?
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I agree that hamster-applet shouldn't be doing that, and will be looking
forward to your better way of handling it.
Meanwhile, the ugly fix will help with screen-locking issues, and I'd
rather get something out that at least takes care of the issue sooner
rather than later.
--
idle/screensaver i
Marc - I had a look at the patch from upstream, and I still think it's
wrong. I was going to propose a different way to handle this upstream,
but haven't had a chance to look at it properly yet. hamster-applet
really shouldn't be intercepting and handling messages on the
org.gnome.ScreeSaver interf
I've built an updated hamster-applet package in the following PPA:
https://launchpad.net/~mdeslaur/+archive/screen-locking
Please try it, along with the gnome-screensaver security update for
karmic that came out a couple of days ago, and give feedback here.
If this solves the problem, I'll push
Just checking the pulse here, from what I understand this has been fixed
upstream by hamster. Will the fix be backported to the karmic package?
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because
I often have the case that the screenblanker does not kick in if I don't
use the computer, but if I touch the mouse again, it suddenly activates.
Is this a separate bug to this?
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You recei
There's likely only one issue affecting totem and eog here. Closing the
eog task for now
** Changed in: eog
Status: Confirmed => Invalid
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because
Is anyone here using the hamster-applet?
** Changed in: gnome-screensaver (Ubuntu)
Status: Triaged => Incomplete
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubu
After further testing, I was able to determine that this is not
architecture/package-specific either. Creating a blank account account
on this computer, I can see that only my main account is affected, so it
must be the usual "broken/corrupt configuration" problem.
The problem is that I have no id
In the hope that it can help as per previous comment, here are some
steps for reproducing:
- in gnome-power-preferences, set the screen to blank after 1 minute of
inactivity
- (optional?): in gnome-screensaver-preferences, set the session to go
idle/screensaver to activate at 1 minute
Now, logout
Responding to your list comment, the issue is not a blocker because
there is only one user running into it so far you, and the bug without
steps describing how to trigger the issue is not easy to work on, would
still be nice to get fixed though
--
idle/screensaver inhibition feature doesn't work
** Changed in: eog
Status: New => Confirmed
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: gnome-screensaver via
https://bugzilla.gnome.org/show_bug.cgi?id=599196
Importance: Unknown
Status: Unknown
** Package changed: totem (Ubuntu) => gnome-screensaver (Ubuntu)
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad
Well, now I filed a third bug,
https://bugzilla.gnome.org/show_bug.cgi?id=599196 hoping that it gets
anywhere...
** Bug watch added: GNOME Bug Tracker #599196
https://bugzilla.gnome.org/show_bug.cgi?id=599196
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.
the fact that you get the same issue on different softwares suggests it
would rather be a gnome-screensaver bug
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubuntu
Bugs,
I just filed https://bugzilla.gnome.org/show_bug.cgi?id=599139 upstream,
but I don't know how to retroactively link to a second upstream bug from
launchpad...
** Bug watch added: GNOME Bug Tracker #599139
https://bugzilla.gnome.org/show_bug.cgi?id=599139
--
idle/screensaver inhibition feature
Yes, along with gnome-session and gnome-power-manager.
I did some further testing, and indeed, eog causes the same kinds of
problems as totem did: if you use fullscreen once, you won't have
working session idling (ie: eog doesn't uninhibit, it seems) until you
logout.
--
idle/screensaver inhibit
do you have gnome-screensaver running?
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
It also affects EoG when you use fullscreen/slideshow:
j...@kusanagi:~$ eog Capture.png
(eog:2262): GLib-WARNING **: GError set over the top of a previous GError or
uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before
it's set.
The overwriting er
Upstream replied that they fixed the warnings in totem, and that they "couldn't
reproduce the problem, but I can see how the original warning might happen.
Most likely, gnome-screensaver crashed, or was killed, and the gnome-session
inhibition didn't notice. gnome-screensaver is supposed to prox
I can reproduce this bug on opensuse 11.2 too. This is a upstream bug.
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Thank you for sending the bug to GNOME
** Changed in: totem (Ubuntu)
Status: New => Triaged
--
idle/screensaver inhibition feature doesn't work reliably in karmic
https://bugs.launchpad.net/bugs/448438
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Bug watch added: GNOME Bug Tracker #598173
https://bugzilla.gnome.org/show_bug.cgi?id=598173
** Also affects: totem via
https://bugzilla.gnome.org/show_bug.cgi?id=598173
Importance: Unknown
Status: Unknown
--
idle/screensaver inhibition feature doesn't work reliably in karmic
Thank you for your bug report. The issue is an upstream one and it would
be nice if somebody having it could send the bug the to the people
writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
** Changed in: totem (Ubuntu)
Importance: Undecided => Low
** Changed in: totem (Ubunt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33431040/Dependencies.txt
** Attachment added: "GstreamerVersions.txt"
http://launchpadlibrarian.net/33431044/GstreamerVersions.txt
** Attachment added: "LogAlsaMixer.txt"
http://launchpadlibrarian.net/33431046/LogAls
34 matches
Mail list logo
