[Bug 1164016] Re: restore type-ahead find
OK. So I was a happy user of 16.04. With a new computer in August, I thought it would make sense to go with 18.04. One of the biggest issues is this searching stuff in Nautilus. Why? 1. It is not instant (unlike the type/find ahead of Nautilus in 16.04). I cannot type and then press enter and load the folder I want. 2. It is inconsistent with file dialogs (e.g. save or open) where find/type ahead works as expected. 3. Often I just want to see the files and folders in relation to one another. I might want to see the files starting with 'th', and being able to see the files starting with 'te' and 'tg' before the ones starting with 'th' is often quite useful. 4. There is no way that I can see to make it search only within the directory and not recursively search all subdirectories. I don't like that. 5. And searching within subdirectories doesn't even work 100% of the time! E.g. A search for a dot folder consistently doesn't turn it up. Thank you Ubuntu developers for previously hiding this stupidity. Please consider getting rid of it in 18.04 as well. -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66896] Re: gnome-search-tool should make clear than the files containing text apply to text plain formats only
Please just add the wording (plain text formats only) after Contains the text in the search program. I just got bitten by this one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/66896 Title: gnome-search-tool should make clear than the files containing text apply to text plain formats only To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-utils/+bug/66896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 980687] [NEW] evince crashed with SIGSEGV in FcFontSetSort() (viewing properties)
Public bug reported: I was viewing a PDF, went to view the properties, and then tried to close the properties. The window manger asked me if I wanted to force the close, I said wait. Later, Evince crashed. It maybe related to #260715, but I doubt it. Apport gives further info: ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: evince 2.30.3-0ubuntu1.3 ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-generic i686 Architecture: i386 Date: Fri Apr 13 10:49:53 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) KernLog: Apr 13 08:36:18 AnarchistaMachina kernel: [443837.558968] type=1505 audit(1334302578.080:20): operation=profile_replace pid=7736 name=/usr/lib/cups/backend/cups-pdf Apr 13 08:36:18 AnarchistaMachina kernel: [443837.569024] type=1505 audit(1334302578.092:21): operation=profile_replace pid=7736 name=/usr/sbin/cupsd ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.32-40-generic root=UUID=386ce6cd-bbf5-47fa-b3f6-d6f03762fae7 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x1df21f FcFontSetSort+63: add(%edx),%edi PC (0x001df21f) ok source (%edx) (0x44575f30) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: evince StacktraceTop: FcFontSetSort () from /usr/lib/libfontconfig.so.1 FcFontSort () from /usr/lib/libfontconfig.so.1 GlobalParams::getDisplayFont(GfxFont*) () FontInfo::FontInfo(GfxFont*, PDFDoc*) () FontInfoScanner::scanFonts(Dict*, GooList*) () Title: evince crashed with SIGSEGV in FcFontSetSort() UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 lucid -- 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/980687 Title: evince crashed with SIGSEGV in FcFontSetSort() (viewing properties) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/980687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 980687] Re: evince crashed with SIGSEGV in FcFontSetSort() (viewing properties)
-- 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/980687 Title: evince crashed with SIGSEGV in FcFontSetSort() (viewing properties) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/980687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 173350] Re: Caps lock LED changes state even when caps lock is mapped to ctrl
This is still an issue for me. I'm running 8.04 (up to date) on a HP DV 1700 series laptop. When I use the GUI to swap the ctrl and caps keys, the key marked caps lock is still the only one that is triggering the LED. Actually, I ran the command xmodmap -e clear lock -e add lock = Caps_Lock as suggested above, and that has fixed it for now (yet to restart). On another computer running 9.10 (no way am I putting that on my laptop, I'm sticking with what I *know* works), the problem does not occur. (And, previously, running, I think it was 7.10 on my laptop, it didn't occur either.) If the xmodmap command sticks after restarting, I'll edit this. Otherwise I'll try other suggestions in the thread and comment on them too. -- Caps lock LED changes state even when caps lock is mapped to ctrl https://bugs.launchpad.net/bugs/173350 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 173350] Re: Caps lock LED changes state even when caps lock is mapped to ctrl
It doesn't stick. But, rather than mess around with config files, I've got another work around. Put the command: xmodmap -e clear lock -e add lock = Caps_Lock into the sessions thingy (System- Preferences - Sessions - Add, the name is whatever, the command is the one above etc.). Also after switching through the GUI, but before running the xmodmap command, ctrl-alt-backspace has to use the 'real' ctrl key. ctrl-alt- arrow (to switch desktops) has to use the 'new' (formally caps) ctrl key. After running the xmodmap command, the 'new' ctrl key works for everything. -- Caps lock LED changes state even when caps lock is mapped to ctrl https://bugs.launchpad.net/bugs/173350 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
