On Sat, Apr 29, 2017 at 5:58 PM, Khurshid Alam
<khurshid.a...@linuxmail.org> 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
- 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
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
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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184159
Title:
[saucy] scrolling with a touchpad is
This is already fixed upstream:
http://git.gnome.org/cgit/tracker/commit/?id=9aa5141e85e9a7f719121bf7d6ac090ca539b7e9
Will be available in 0.6.93
--
tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data()
https://bugs.launchpad.net/bugs/355499
You received this bug
This bug was fixed last week in r3159 in upstream svn. Will be included
in next tracker release
--
tracker-indexer crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
https://bugs.launchpad.net/bugs/354362
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Reporters,
Is it trackerd or tracker-indexer taking all memory? could you attach
logs from ~/.local/share/tracker/ when this happens, would you mind to
install valgrind and do the following?:
$ killall trackerd tracker-indexer
[On one terminal]
$ G_SLICE=always_malloc valgrind
Hrm, the tracker daemons are in /usr/lib/tracker/ rather, use that path
for the valgrind commands
--
trackerd uses up all available memory
https://bugs.launchpad.net/bugs/214219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hrm, I think I should have removed that file a *long* time ago, I
thought I did, sorry about that :)
Since s-t-b 2.x, the backends no longer tries to guess the service type
(had multiple i18n issues, there still had to be matching code in the
frontend to show things properly, etc), so the
would you argue that the tools was working? you can't share anonymously using
it and you need to use the
command line to set a password to do a normal share. what do you think the
normal user reaction to this is? we
got many bugs asking why we ship something which doesn't work, because
GNOME System Tools is looking for maintainers, maybe you can use your
exceptional intelligence to do something constructive
--
network settings; utter uselessness thereof for PPPoE
https://bugs.launchpad.net/bugs/180535
You received this bug notification because you are a member of Ubuntu
Bugs,
Martin, just to clear things up, I still tend to think it's still a
PolicyKit bug :). if an application doesn't set I/O watch functions for
config changes, PolicyKit shouldn't make use of its internal caches, as
they aren't going to be updated properly, leading to serious (and
unobvious)
What's the output of runlevel? it's really strange that it isn't
detecting your current one.
--
[hardy] time-admin crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/181503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There's something fishy in your system then :)
I'll commit a change to deal better with this situation though
--
[hardy] time-admin crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/181503
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Hi!,
Lately wnck has been added some tooltips, I understand they try to be
useful, however I see some problems there:
1) Report a one time information. Once the user gets to know the shortcuts the
tooltip stops being useful.
2) Reports nonexistent/useless shortcuts. I've
g-s-t has nothing to do with that, that's an error returned from PK that
g-s-t prints now, looks like bug #181088 has revived?
--
Users-admin unlock not working
https://bugs.launchpad.net/bugs/183673
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
Binary package hint: gnome-system-tools
gnome-system-tools relies on PolicyKit to check privileges, and
PolicyKit-gnome 0.6 requires reading /proc/$pid/exe to know the
executable binary path, however this is what I get when running any
g-s-t tool (didn't see it with other
Please try Drag and Drop :)
--
Cannot change order of DNS servers
https://launchpad.net/bugs/92682
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi!,
I've added sanity checks in system-tools-backends CVS, so now it will
refuse to do *any* changes if it can't figure out the init directories.
But, however, after looking a look at the code, I find hard to believe
that s-t-b is responsible of this. As the code is right now, if it
couldn't
A couple of lines should be added in system-tools-
backends/Utils/Platform.pm to recognize ubuntu-7.04 like ubuntu-6.10,
but given that feisty is supposed to fully use upstart (being
incompatible with the sysV-like init in Edgy), upstream will not add
Feisty support until there is code to handle
The W issue is already fixed in system-tools-backends HEAD
--
[network-admin] Dial out does not work
https://launchpad.net/bugs/22119
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
24 matches
Mail list logo
