Update: Not sure what changed -- I deleted the .config/nautilus
directory to no effect, then turned off the overlay scrollbars to no
effect, restarted with overlay scrollbars off, and it touchpad scrolling
seems to be working again.
--
You received this bug notification because you are a member
Public bug reported:
After a recent update, touchpad scrolling within Nautilus stopped
working. Scrolling does work when the scrollbars are grabbed and moved,
but edge scrolling and two-finger scrolling ceased working.
This behavior began concurrently with Bug #1010033 (gnome-search-tool
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1010120
Title:
Touchpad scrolling no longer works
To manage notifications about this bug go to:
Actually, you can add compiz --replace to your Startup Applications and
not have to think about this bug until it gets fixed. That's a trick I
had to use in past releases, and it still works today. I can drag and
drop in Ubuntu 11.04 Classic Desktop without a second thought -- and it
was one of
(I should have noted that the compiz --replace startup fix is if you're
using the classic Gnome desktop, and not Unity.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libwnck in Ubuntu.
https://bugs.launchpad.net/bugs/697358
Public bug reported:
Binary package hint: gnome-control-center
Whenever Appearances is opened from System Preferences, gnome-
appearance-properties spikes to around 100%. After closing Appearances,
gnome-appearance-properties will not end, and continues to hammer the
cpu. If you open
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
https://bugs.launchpad.net/bugs/688182
Title:
gnome-appearance-properties: high cpu, won't end
--
desktop-bugs mailing list
Public bug reported:
Binary package hint: gnome-control-center
On boot, gnome-appearance-properties spikes to around 70%-80%, and
doesn't go down. This happens on two separate installations of Ubuntu
10.10, one clean install on a Lenovo IdeaPad Y510 (laptop) and one
upgrade on a Dell Inspiron
--
gnome-appearance-properties spikes the CPU
https://bugs.launchpad.net/bugs/680734
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I'm using Maverick, and this bug has been persistent at least since
Karmic. If Paddy Launch was able to do something to make it work, care
to share?
--
nautilus unable to delete directories correctly over WebDAV
https://bugs.launchpad.net/bugs/402279
You received this bug notification because
I never had an issue with this until I installed Maverick. Now gnome-
power-manager is regularly ramping my CPU up between 50% and 70% when
plugged in to AC power. Unplugging it doesn't seem to help.
Running Ubuntu 10.10 (64bit) on a Lenovo IdeaPad Y510, clean install.
I did piped the same
Public bug reported:
Binary package hint: nautilus
Almost every time I remove my Sansa Sandisk Clip+ mp3 device, the device
is unmounted, and then Nautilus throws the error the folder contents
could not be displayed.
There doesn't seem to be anything wrong -- the device is unmounted
without
Hi, thanks for checking back in.
I did upgrade to Maverick and hadn't noticed that same behavior until
yesterday. So it seems to be much more erratic, and I've only noticed it
once, but it was still there.
--
Keyboard, mouse clicks unresponsive after display resumes from sleep until
Just curious how this was fixed. I'm having this same problem on a clean
install of Maverick.
--
safe remove drive - Could not display computer:///
https://bugs.launchpad.net/bugs/599740
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Binary package hint: gnome-power-manager
What's expected: After resuming from a blank screen, expect to be able
to use whatever as normal.
What actually happens: After resuming from a blank screen, keyboard and
mouse input is unresponsive until the application is minimized
15 matches
Mail list logo