[Bug 995636] [NEW] Space, arrows and j/k stop working randomly
Public bug reported: Sometimes all the other key commands to scroll a document apart from pg. up/down stop working. Mouse wheel still works. This is unrelated to the fullscreen bug, as entering fullscreen is not needed to trigger this, and entering/exiting fs doesn't return the functionality. Nor does opening any menus etc. Hints appreciated how to debug this better, since there are no obvious steps to reproduce this. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/995636 Title: Space, arrows and j/k stop working randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/995636/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 576744] Re: Unable to modify brightness when the screen is locked
I'm not what is required to raise the importance of the bug, but this is much more major usability problem than just low. Given a non technical user, the screen is just black without any hints on what the user can do. This is equivalent to the system just plain crashing or freezing. A more clever user might attempt to write the password blindly, and even try pressing the caps lock if the first attempt doesn't work, but this is just unacceptable. It's even worse in natty, where the brightness goes to zero when removing the power cable, even if all relevant settings are disabled in power management GUI. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/576744 Title: Unable to modify brightness when the screen is locked -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 735299] [NEW] Failed to load terminal capabilities from '/etc/termcap'
Public bug reported: Binary package hint: gnome-terminal After upgrading from maverick to natty, termcap isn't found anymore on Terminal. This results to for example enter not working (instead have to use ctrl-j). Xterm for example works fine. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. https://bugs.launchpad.net/bugs/735299 Title: Failed to load terminal capabilities from '/etc/termcap' -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 430494] Re: gdm upstart script fails to start gdm
Seems like it is fixed in Lucid. -- gdm upstart script fails to start gdm https://bugs.launchpad.net/bugs/430494 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 585278] [NEW] g-p-m runs for every user and gdm, eating memory
Public bug reported: Binary package hint: gnome-power-manager While running multiple times wouldn't be a problem normally, each instance eats roughly 250 megabytes of memory. For a small family of users, this means that even a new machine with 4GB ram will eventually start struggling on tasks it shouldn't. Either one instance of g-p-m should be enough, or the memory footprint should be a lot smaller. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- g-p-m runs for every user and gdm, eating memory https://bugs.launchpad.net/bugs/585278 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 430494] Re: gdm upstart script fails to start gdm
Doesn't seem like it. Exact same symptoms: 'start gdm' reports a pid, but gdm does not come up. syslog shows that it tried to spawn too many times. sudo gdm does work just fine. It seems like this is still related to booting into recovery mode and then continuing the boot. -- gdm upstart script fails to start gdm https://bugs.launchpad.net/bugs/430494 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
