[Desktop-packages] [Bug 1184159]
2 Patches are now on xorg-devel, http://lists.x.org/archives/xorg-devel/2013-November/039220.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1184159 Title: [saucy] scrolling with a touchpad is jerky with bindings set in compiz for Desktop-based Viewport Switching Status in Compiz: Invalid Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “gtk+3.0” package in Ubuntu: Triaged Status in “xorg-server” package in Ubuntu: Triaged Bug description: Hello, Scrolling with a touchpad is now a bit jerky. It's exactly the same bug than bug #1171156 introduced in Raring by an upstream's patch in order to fix bug #1046988 (which was tracked by upstream there: https://bugzilla.gnome.org/show_bug.cgi?id=690275 ) * Impact: Up & down scrolling with a touchpad is now a bit jerky, seen best with gedit in large files though also seems to affect nautilus & in general. * Testcase: Set any bindings in Viewport Switcher > Desktop-based Viewport switching try scrolling in long documents in gedit using a touchpad, is scrolling "jerky"? * Videos: Before: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650661/+files/gtk_scroll_1171156_without_patch.ogv After: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650662/+files/gtk_scroll_1171156_with_patch.ogv * Note: It seems this bug doesn't affect Gnome-Shell session: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/comments/10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 17:44:01 2013 InstallationDate: Installed on 2011-08-10 (653 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1184159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1666676] Re: Install tracker by default
On Sat, Apr 29, 2017 at 5:58 PM, Khurshid Alam wrote: > @Carlos Garnacho > > I have tested this on a low-end laptops first with no tracker and then > with tracker installed with default configuration (and there our problem > lies.) The default configuration is just unacceptable. https://developer.gnome.org/gio/unstable/GSettings.html#id-1.4.19.2.9.25 > > 1. Why does tracker index bzr, vendor, pycache folders by default? I put Because nobody provided patches. I will welcome yours at https://bugzilla.gnome.org/enter_bug.cgi?product=tracker What are 'vendor' folders at all? > my git projects inside documents. You can literally see that with > tracker daemon -f. Also, It should ignore any directory starting with > "." by default It does ignore hidden files/folders, both unix and msdos style on vfat mounts > > 2. There are many other configuration available in Gsettings which > aren't exposed in GUI. As far as Tracker is concerned, UI is part of the integrator. The tracker-preferences executable is a relic and will be eventually discontinued. > > 3. I configure following things: > -- enable-writeback false > -- index-optical-discs false > -- index-on-battery false > -- index-removable-devices false > -- ignored-directories ['core-dumps', 'CVS', 'lost+found', 'po', > 'vendor', '.git'] > -- ignore-stop-words true > -- ignore-numbers true > -- max-words-to-index 1000 > -- removable-days-threshold 3 ? (I don't not understand this) - You seem to reset a bunch of those settings to their default: index-optical-discs, index-removable-devices, ignore-stop-words, ignore-numbers and removable-days-threshold - You added 'vendor' to ignored-directories, good. Adding '.git' is both useless and needless though, the hidden directory will be ignored by default anyway, what you want (and the default) is having '.git' on ignored-directories-with-content, so the parent directory is ignored (and thus the whole cloned repo). - The remaining settings (enable-writeback, index-on-battery, max-words-to-index), how did you measure the impact of these modifications? Did you reindex from scratch after every modification? What were you aiming to measure, system responsivity, indexing responsitivity, cpu usage, ... ? > > After this the system is somewhat working well. There are no aggressive > indexing. All files can still be searched from shell. Documents, Bijiben > etc works without any problems. Perhaps you've just left initial indexing to happen? Tracker is obviously smart enough to avoid reindexing stuff for the sake of it, after initial indexing happened it will sit idle most of the time unless there's file monitor events to attend to. Also, checking an unmodified, up-to-date directory tree (as it usually happens on miner startup) is orders of magnitude faster than indexing it from scratch. > > There are many options which can be disabled during compilation. For > example extractor metadata for ps.gz, gif, iso, xps, abw seems pretty > useless to me (who use it and why?). These can be disabled during > compilation. I have the feeling here and other places above that you are extrapolating personal usecases to entire user bases. Not indexing .iso files will eg. limit functionality of gnome-boxes. As for the other document/image formats, how can you tell at all they are useless? Would you think it's fair not to index the content of these documents for users that actually possess those? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Install tracker by default Status in nautilus package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666676] Re: Enable tracker by default for Unity too
With my obvious tracker maintainer bias, I support the move. Tracker has been slowly but steadily improving in stability throughout the 1.x series, the common complains about CPU and logging have decreased as well from where I stand. Although I also suggest you have a look at the settings and see if vendor overrides might make sense for your users. Tracker is heading now to 1.12.x which according to the current plan will be the last 1.x release series (in preparation for 2.x), it will remain feature frozen but still open to stability and performance improvements. Khurshid: zeitgeist and tracker have little in common. Zeitgeist is about activity tracking, Tracker for these purposes is a filesystem indexer. The usecase being discussed here is nautilus indeed, but having tracker by default could make other gnome apps that strongly rely on Tracker work on Unity, like gnome-music or gnome-documents. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too Status in nautilus package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666676] Re: Enable tracker by default for Unity too
Hey Jorge, some answers, for the same definition of "some" :P - What does an upgrade look like? Let's say I have a home directory with gigs of data, when I accomplish an upgrade to 17.10 when/how does indexing take place? Indexing would take place when the services have been started on the user session, presumably started by the install scripts, or on session restart. tracker-miner-fs has a configurable timeout (defaults to 15s) to avoid I/O during session startup, as it's already pretty high at that time. - Is this something that happens in the background or during a package installation? All indexing happens in the background, on startup tracker-miner-fs performs an initial crawling where it 1) sets up directory monitors and 2) ensures its idea of the FS is up-to-date (eg. there's not been changes between reboots). After that, tracker-miner-fs just listens to directory monitor events and updates its DB, subdirectories newly added to recursively indexed folders would be crawled in a similar way when discovered. And same for local mounted volumes, although we don't index those by default. Indexing is also influenced by AC adapter/battery state and configuration, it reduces to a crawl or pauses altogether given the right conditions. - Is indexing a long process? It depends, Tracker only indexes XDG folders (and $HOME non-recursively) by default, so indexing depends on the amount of files/directories and I/O throughtput. There's of course worst cases like multi-TB 2500rpm HDDs with millions of files, but on more average setups tracker-miner-fs should take the order of seconds. A somewhat favorable example, reindexing from scratch ~8K items take tracker-miner-fs ~2s on this ssd- powered laptop. But tracker-miner-fs only manages FS-level information, the isolated tracker-extract process performs the actual content sniffing, and the time spent there is variable too per mimetype, eg. heavy PDF documents might take poppler several seconds each, while plain text files could be handled in the ballpark of hundreds per second. Oh, and there's also file/dir name pattern matching to cut down uninteresting portions of the filesystem, tracker-miner-fs eg. tries to avoid git repos, uncompressed tarballs and whatnot. - Is it something we need to display to the user? It's your call really... gnome doesn't bother for example. Some apps like gnome-music do track activity and show a "Loading..." in-app banner, but little else. - Is it one of those things where we'll need to inform users in the release notes that an expensive io operation will take place as part of the upgrade? It's maybe wise to do that, it will churn a few extra cycles globally. - In the past I recall having to modify inotify handles for performance, at some point the default handles we set in ubuntu would run out and search wouldn't work well at all. Since that was years ago I'm assuming these sorts of issues have been sorted out? I assume so, tracker is admittedly greedy with inotify handles, but there's been for quite some time now the runtime checks for the user limit, leaving also some room for other apps wanting file monitors. If with the big slice of handles that Tracker takes for itself there's really not enough to cover the indexed portions of the filesystem, Tracker takes this as a soft failure, the non-monitored directories would just be checked for changes on the startup phase. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too Status in nautilus package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666676] Re: Enable tracker by default for Unity too
Hi Martin, You're right. Tracker is not a replacement for type-ahead search, reducing tracker to this would be far too simplistic. Using Tracker is however a technical decision adopted by the nautilus team, they use it in a way that doesn't even attempt to be functionally equivalent to type-ahead search. As I see it, Ubuntu has two choices: 1) Investing time/resources in updating a patch that will get bigger and trickier to rebase over time, with the downside of possible stability issues ending up in the wrong bug reporting system, being ignored or not addressed properly, and generally frustrating users. 2) Getting closer to upstream, which means accepting additional processes to get your files indexed in the background and best-effort latency upon filesystem changes, and getting a more versatile search in return. Whatever the decision is, and as far as I'm personally concerned, by all means be my guest :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too Status in nautilus package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666676] Re: Enable tracker by default for Unity too
Hey Jeremy, - Initial indexing (How long does it take? Does it make the computer noticeably less responsive?) I already tried to reply this to Jorge, it does depend. Depends on the amount of files and disk throughput. - Search (Is search in Nautilus more or less responsive with tracker? How noticeable is the difference?) Full-text search in Tracker is fairly optimized, plain FTS queries usually take ~30-50ms across multiple thousands of indexed documents. This is fast enough for search-as-you-type as nautilus uses it, and definitely faster than the recursive filename matching paths. Hi Martin, - Is it acceptable to have approximate search results if the indexing isn't (yet) up to date? If tracker-miner-fs is not paused/throttled down, it will pick up changes in monitored folders just as fast as any other app, there is very little extra overhead above the gio/inotify delays. - Does it significantly affect battery life? Given Tracker is pretty conservative while on battery, that's a bold "no". However "acceptable" or "significant" something is is entirely in the eye of the beholder. It's not news that there's a trade off between instantness and cpu/battery, Tracker can't get the best of both worlds at the same time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too Status in nautilus package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666676] Re: Enable tracker by default for Unity too
- Initial indexing (How long does it take? Does it make the computer noticeably less responsive?) I realize I might have not replied to the "responsiveness" bit. Given Tracker miners set up themselves with low scheduler/io priority and high niceness, I expect it to have little impact in perceived responsiveness. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too Status in nautilus package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
