[Bug 495723] Re: the copy action doesn't work in the second after a directory load
Hmmm, I ran it, but CTRL+A, CTRL+C, CTRL+V don't seem to do anything, nor does right click :S -- the copy action doesn't work in the second after a directory load https://bugs.launchpad.net/bugs/495723 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 495723] Re: the copy action doesn't work in the second after a directory load
Hey mate thanks, sorry but how would I go about installing that? :P -- the copy action doesn't work in the second after a directory load https://bugs.launchpad.net/bugs/495723 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 495723] Re: Nautilus File Copy Lag
Pardon me, I thought it was more clear than that. If you consider the Ctrl+C keyboard shortcut as a trigger to the operation of placing the file(s)/directory(s) into the clipboard for copying, and I am saying is that the trigger does not initiate the operation until about 2 seconds after the directory in opened - from which the trigger is initiated. Hopefully that makes more sense. -- Nautilus File Copy Lag https://bugs.launchpad.net/bugs/495723 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 495723] Re: the copy action doesn't work in the second after a directory load
Happens to me literally all the time. No need to visually parse the directory if you cache the required query :P -- the copy action doesn't work in the second after a directory load https://bugs.launchpad.net/bugs/495723 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 161787] Re: Gnome Sound Preferences help refers to a system bell, but it's called system beep.
I would like the developers to elevate the importance of this bug. This issue is present in jaunty, in the beta, with all the packages up to date. I have found it impossible to disable the system beep in any way. None of the configuration options noted above work for me. I also cannot simply blacklist the pcspkr or snd-sprk module, because my laptop has the speaker built into the sound card - which means the only way to disable it, is to blacklist the module for the entire sound card - which means no sound of any kind whatsoever. And the beep is really bloody annoying. I know ubuntu developers put it there willingly several versions back, so it's not like you have to search around trying to find it - how hard can it be to put an option on it, whether to enable it or not at shutdown? Thanks. -- Gnome Sound Preferences help refers to a system bell, but it's called system beep. https://bugs.launchpad.net/bugs/161787 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 161787] Re: Gnome Sound Preferences help refers to a system bell, but it's called system beep.
Also, the pcspkr creates static for me on reboot, which is an extra annoyance. -- Gnome Sound Preferences help refers to a system bell, but it's called system beep. https://bugs.launchpad.net/bugs/161787 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
