This bug was fixed in the package gnome-settings-daemon -
3.8.5-0ubuntu11.1
---
gnome-settings-daemon (3.8.5-0ubuntu11.1) saucy; urgency=low
* debian/patches/git_keyboard-Don-t-set-the-XKB-group-switching-option.patch:
- If the user has the grp xkb option enabled, pressing the
I was also affected by the bug and tried installing the proposed -
gnome-settings-daemon (3.8.5-0ubuntu11.1).
After a reboot I now have the correct behaviour.
Cheers!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I was affected by this bug (Suspend-Resume-EnterPassword resulted in HUD
displaying). I enabled proposed, upgraded this morning (package version
3.8.5-0ubuntu11.1 amd64 is now installed). Suspend and resume now
results in the desired screen with no HUD. I haven't noticed any
regressions yet.
Hello Steve, or anyone else affected,
Accepted gnome-settings-daemon into saucy-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/gnome-
settings-daemon/3.8.5-0ubuntu11.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
I built a test version of gnome-settings-daemon with the wakeup keys
changed from Alt to Shift at ppa:bregma/unity7-experimental [1]. If
folks could test this and confirm it has no unwanted side effects, we
can SRU this.
[1] https://launchpad.net/~bregma/+archive/unity7-experimental
**
@bregma
I tried your patch and it works fine here. I used Suspend via menu and
closed the laptop lid. Both methods did not open HUD upon wake. Great
job! Thanks for the fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
+ Impact: hud is opened after resume
+
+ Test case: suspend/resume your computer
+
+ Regression potential: the new code is doing a tapping on the shift
+ key, check that there is no input side effect due to that
+
+ -
+
Traveling at a conference, so I'm doing a
Seems fine to me, upstream raised concerns that shift might have similar
issue but without giving details. I'm going to sponsor that SRU, let's
see how the testing goes
** Also affects: gnome-settings-daemon (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: unity
** No longer affects: unity (Ubuntu Saucy)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after suspend/resume, the Unity HUD is always open when I
** Changed in: gnome-settings-daemon
Status: New = Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1227920
Title:
after
If Gnome will not fix this brokenness on the grounds that it isn't a
problem in Gnome Shell and may be rewritten at some vague time in the
future to support a Wayland compositor, can we just distro-patch gnome-
settings-daemon to return to sanity?
--
You received this bug notification because
** Changed in: unity
Milestone: 7.2.0 = None
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after suspend/resume, the Unity HUD is always open when I
+10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after suspend/resume, the Unity HUD is always open when I unlock the
screen
Status in Gnome
My workaround was to disable the Left Alt shortcut key for the HUD.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after suspend/resume, the Unity HUD is
I see this behaviour as well on my desktop. Ubuntu 13.10 64bit, nvidia
graphics (binary drivers).
I suspend using menu option, then resume by pressing power button. I get
a password screen, enter my password, and when it drops to the desktop,
the HUD is already open.
--
You received this bug
Just upgraded to 13.10 today and noticed this bug still persists. I've
tried suspending using the menu as well as closing the lid, and both
methods suffer from the HUD being initialized upon wake. My machine is a
Dell XPS 13 Ultrabook (128 GB SSD, 4 GB RAM, Sandy Bridge)
--
You received this bug
I see it 100% of the time when suspending using the menu. I still it
with upower 0.9.22-1. Looking at the code, the debdiff in comment #18
seems very reasonable-- can someone upload this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Bug watch added: GNOME Bug Tracker #710106
https://bugzilla.gnome.org/show_bug.cgi?id=710106
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=710106
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
** Changed in: gnome-settings-daemon
Status: Unknown = New
** Changed in: gnome-settings-daemon
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Sorry, ignore my comment #24, now I see this also using Xmir
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after suspend/resume, the Unity HUD is always
I tried it also using Xmir and in my system the HUD is not shown when
waking after suspend by closing the lid.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
The gnome-settings daemon uses the XTEST extension to inject kepresses
of the alt key when the lid is opened (or whatever action is taken to
unsuspend: it's all lid opened to g-s-d). It does this to force-
reset the X11 idle time counter. The use of the Alt key is hardcoded in
The only way Unity could avoid this problem is to change the default HUD
key. The solution rightly lies in changing the behaviour of gnome-
settings-daemon.
** Changed in: unity (Ubuntu)
Status: Triaged = Invalid
** Changed in: unity
Status: Incomplete = Invalid
--
You received
@Stephen: it's not a frequently reported issue and I can't confirm it,
do you have an idea why it's non consistent behaviour?
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Desktop
Packages, which is
Sebastien, maybe everyone else is affected by bug #1228406 now, so
doesn't notice the problem since they never resume from suspend? ;-P
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
I get this issue reported to me fairly frequently. If you have the
problem, it's consistent and reliably reproduced.
The attached patch fixes the problem for me.
** Patch added: patch to change the key injected by g-s-d on resume
I have seen this bug and it is repeatable after every suspend. I only
today discovered this report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227920
Title:
after suspend/resume, the Unity HUD is always open when I unlock the
screen
Status
I have 1 machine where this occurs 100 % of the time. It's been doing this
since at least when I filed bug on a month ago, probably a week or 2 longer
than that.
Several days ago added a new install to same machine happened to notice it no
longer occurs.
So the diff here seems to be 'upower',
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
I'm the reporter of Bug #1227920 . In my system I can reproduce it 100%
of the times, but only if the system is suspended by closing the lid, if
I suspend using the menu option that the HUD is not triggered when the
computer is woken.
--
You received this bug notification because you are a
By the way, I have
ii upower 0.9.22-1 amd64abstraction for power
manageme
so comment 20 doesn't seem to apply to my system.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
32 matches
Mail list logo