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
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
- 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
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
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
Desktop Bugs, which is a bug assignee.
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
Desktop Bugs, which
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
Desktop Bugs, which is a
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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
12 matches
Mail list logo
