There seems to be an option in gnome-power-manager gconf now for "use
screensaver setting" - maybe it's as simple as changing to that by
default. I definitely expected the screensaver setting to completely
remove all screen locking, and when it didn't that was surprising.
--
You received this bug
basically you need to figure out who is sending a _NET_ACTIVE_WINDOW
request (e.g. done by gtk_window_present, gtk_window_present_with_time,
wnck_window_activate) with a timestamp of 0 (also known as CurrentTime,
or GDK_CURRENT_TIME). Then that app needs to be fixed.
Though it sounds like more may
Public bug reported:
In Lucid beta the mute button now toggles instead of forcing sound off. I think
it was a deliberate design choice that it always forced sound off; on
Thinkpads, it always forces sound off in Windows too, I believe, and even
before the OS boots e.g. the power-on beep. It mak
I'm on 32-bit, with NetworkManager
After a kernel upgrade to 2.6.32-17-generic it seems to work fine (so far) but
the logs are getting continuous spam
[ 359.852950] iwlagn :03:00.0: free more than tfds_in_queue (1:2)
[ 359.877899] iwlagn :03:00.0: free more than tfds_in_queue (1:2)
[ 3
With Lucid 2.6.32-16-generic and Intel 5300 wifi is broken for me.
Sometimes it downloads a few K before it stops working, sometimes
doesn't seem to work at all. I don't have the log errors though. It
worked OK for me in Karmic and before.
--
Intel Wireless 5300 AGN: iwlagn: No space for Tx
https
Firefox is considerably easier to fix than flash ;-) just yank the
misguided couple lines that unfullscreen on focus out.
--
Pressing volume/brightness key changes window focus (e.g. makes Flash exit full
screen)
https://bugs.launchpad.net/bugs/224475
You received this bug notification because y
I think we're confusing Adobe - both here, and due to people piling on
to the Adobe bug with "me too!" comments that conceal the content-
containing comments over on the Adobe site.
This is a Flash bug. There may _also_ be a GNOME bug or bugs.
The way X works is that if client xyz is going to get
The Adobe bug was wrongly closed, this is caused by Adobe. They need to
reopen their bug. I added a comment to it explaining.
Exiting fullscreen on alt+tab is fine if that's the policy (I don't know
if it is or not), but exiting on volume keys is not fine. They are
implementing the fullscreen-exit
