have not seen this one jet in newer version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346912
Title:
Tracker index corruption (was Tracker does not stop indexing)
To manage notifications about
is this still a problem in focal or later?
** Changed in: tracker (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346912
Title:
Tracker index corruption
Jaunty is well past its EOL. Closing as Won't Fix.
** Changed in: tracker (Ubuntu Jaunty)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346912
Title:
Tracker
** Changed in: tracker
Status: Invalid = Expired
** Changed in: tracker
Importance: Unknown = Critical
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: tracker
Status: New = Invalid
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I still have the same Problem with the tracker. I disabled it 2 months
ago because it took so much CPU and a lot of my harddisk-resource. I
enabled it yesterday an got the told error.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You
I had the problem on several occasions in Jaunty, then about 6 months of peace,
and now the problem is back in Karmic...
tracker-processes -r and re-indexing the drive is a bit of a pain though
--
Tracker index corruption (was Tracker does not stop indexing)
I've been having exactly the same issues as many of the above posters have had.
I'm hoping to have a go at the Milan solution a bit later (deleting a few
hidden files). One other piece of info though.
A piece of extra info not necessarily mentioned above:
there is no problem until I put a
After updates tracker indexing works without problems on my machine. No further
occurrences of index corruption errors.
OS Ubuntu 9.04 64-bit on Ext4 (root) and a few partitions mounted (Ext3, Ext4,
NTFS) with indexing activated for some of their folders. (Note: the setting
index mounted media
I also had this bug after upgrading to 9.04, and
sudo apt-get install tracker-utils
tracker-processes -r # --hard-reset
solved the problem. However, it occured again after I accidentally pulled the
plug of my computer. I now uninstalled tracker. As savebart, I also have a ntfs
drive, but
This bug affected me today. I killed the tracker processes and deleted the
files in those folders
~/.cache/tracker and ~./.local/share/tracker/data and then restarted the
program ( no need to reboot) and works fine now. I have not made any changes to
my torrent program in weeks and this hit me
Hello to all of you!
Decided to Disable the Tracker Index...so now all work well...my
Computer Guru son say me that it's totally NOT necessary!.
Thanks so much for your polite advices!
Truly,
Alex!
On Fri, May 22, 2009 at 11:20 AM, Alex Cozac alex.co...@gmail.com
wrote:
Hi Mike.
Thanks so
Hello!
I confirm the problem on a fresh ubuntu 9.04 64-bit installation, after having
added a ntfs driver in the monitored folders list. The driver was
automatically mounted by modifying the fstab file with the following line:
/dev/sdb1 /media/Dati ntfs-3g defaults,locale=it_IT.UTF-8 0 0
I'd like to add that, for me:
tracker-processes -r
[unsure if required - removed 2 remaining files in ~/.cache/tracker]
/usr/lib/tracker/trackerd
tracker-applet
Seems to have tracker back and working again. I could have logged out
and back in I guess after the first 2 lines, but the
Hi Mike.
Thanks so much...next week my Computer Guru programmer Son will visit
us...so he will repair this bug I hope!.
Thanks again i will inform you...the finally results!.
Cheers,
Alex!
On Fri, May 22, 2009 at 10:00 AM, Mr. Mike m...@himikeb.com wrote:
I'd like to add that, for me:
I should like to add my humble opinion. My system (quad core 2.4GHz
Intel Core2) which worked just fine until upgrading to Ubuntu 9.04 -
the Jaunty Jackalope, is now as slow as Windows Vista (sorry for the
insult). Launching the about Ubuntu dialog takes nearly a minute. At no
time was
jrrk: I don't think you're suffering from the same bug. Yours is
actually much more of a problem! Please open a new report, there must be
a very precise problem to tackle - which may be easier to solve than the
present bug, in the end. Attaching logs from ~/.local/share/tracker/
will help.
--
@gabriela Tracker *was* installed and enabled by default in Intrepid. By
upgrading from Intrepid on your two laptops you inherited its
configuration.
To test if tracker is enabled (or even installed) by default in Jaunty
you need to do a fresh install (in a virtual machine for example). Or
just
Dan - that's wrong. Tracker was installed by default but disabled on
Intrepid. It was only ever enabled by default for a very short period
after being installed by default for the first time in the Hardy
development cycle.
Likewise, it is definately disabled by default on Jaunty (I should know
-
...So? Is there going to be a hot fix that kill trackerd, rm -rf all of
the user files, and then reindexes?
My boss is pretty darn angry with this issue, and he think every other
program is at fault as well. Suddenly his machine is extremely slow.
Why don't you push out a work around through the
Odin - see bug 361205. Perhaps you could try out the package in jaunty-
proposed there and provide some information requested in that bug
report.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you
It seems to work on 2 computers I saw with this trouble using the
package in jaunty-proposed.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I would humbly submit that this bug priority should be raised to High,
if not Critical.
a) One of the bugs that was merged into this one had a priority of high.
b) Medium status is not preferred, see https://dev.launchpad.net/BugTriage
c) Most importantly, this bug keeps a large number of users
Medium is the correct priority for this (definately not critical - for
that, the bug would need to make a large proportion of users machines
unusable with no workaround. There is clearly a workaround here).
Tracker is not enabled by default and you can easily disable it again if
you're
Thomas - the issue about the repeated notifications, and inability to
recover from the index corruption via reindexing is covered by a
separate bug report (bug 361205), which is already high priority and I'm
working on fixing that.
The actual corruption (this bug here) is most likely going to be
I upgraded from Intrepid and had this issue. I did what Bryan McLellan
suggested in a
href=https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/361560/comments/30;bug
361560/a:
sudo apt-get install tracker-utils
tracker-processes -r # --hard-reset
and ran
/usr/lib/tracker/trackerd
Ah, thanks for the correction, and for your work on this. Sorry if I added
to any confusion.
On Fri, May 8, 2009 at 4:24 PM, Chris Coulson
chrisccoul...@googlemail.comwrote:
Thomas - the issue about the repeated notifications, and inability to
recover from the index corruption via reindexing
Someone wrote Tracker is not enabled by default. Please allow me to
doubt that.
I didn't even know what tracker is, until these dialog boxes kept
appearing on and on again on my main machine, with no way to get rid of
them. Tracker was enabled on two of my notebooks, which were upgraded
from
To turn off the track, in a way that it won't start up again:
(1) Right click on it's magnifying glass icon by the clock, and click quit.
(2) Click on the System menu, and goto PreferencesStartUp Applications
(3) Uncheck Tracker and Tracker Applet
I did that for a while hoping I'd see an update
I also have the indexing problem. It is very hard to rid the desktop of
the error message no matter what option I choose.
Next, my Tracker has been un-checked as suggested above by Milan,
however, should we also un-check the Tracker Applet next to the Tracker?
My system is an Intel Core 2 Quad
I also have the indexing problem. It is very hard to rid the desktop of
the error message no matter what option I choose.
Next, my Tracker has been un-checked as suggested above by Milan,
however, should we also un-check the Tracker Applet next to the Tracker?
My system is an Intel Core 2 Quad
@Milan But note that it has always been *disabled* by default. - That
I don't understand.
Yesterday I updated my Dell Latitude to Jaunty (came orig. with 7.10)
and got the tracker error described above. I surely never intentionally
activated indexing - I just don't know what it does. But it is
I started a discussion about this bug here:
http://ubuntuforums.org/showthread.php?p=7149477#post7149477
I hope that is helpful. I am a fairly simple end user, and I am not
very familiar with the proper way to resolve bugs. I had lots of stupid
questions with which I did not want to junk up
@Matteo: I was not criticizing tracker -- that I am trying to wort
around this bug by purging the files and disabling the feature. And I
made an explicit point of saying to Jamie -- you know, the author --
that my turning off the feature was *not* a criticism of his code. I
just don't use or
A few informations to stop these scared comments: :-)
- unchecking 'Enable indexing' in System-Preferences-Search indexing should
be sufficient to stop trackerd, at least after restarting your session if it's
hanging
- you can prevent trackerd from starting by going to
Tracker bugged out for me too. Kept saying the index was corrupted and
the pop-up box came up over and over, regardless of the option selected.
Have tried the manual remove as above:
- remove the contents of ~/.cache/tracker and of
~./.local/share/tracker/data
Perhaps this should be an option on
I upgraded to Jaunty (final) and after a couple hours began seeing
persistent dialogs saying There was an error while performing indexing:
Index corrupted. (Same as many other reporters. No such problem on the
fresh install on my desktop.)
I tried killing tracker, removing ~/.cache/tracker, and
I had the same problem on both of my systems, I upgraded both from Intrepid to
Jaunty Final.
The solution:
- remove the contents of ~/.cache/tracker and of ~./.local/share/tracker/data
- tracker-processes -r
- restart trackerd (in a shell with -v 2 to check)
- let the system index over night
A good number people, including me, have encountered this problem after
upgrading to Jaunty. It makes the system quite unusable and its priority
should be high.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug
I'm sorry for a bad english. I upgraded to Jaunty and have a same
problem with index tracker.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
My solution: purge the tracker data (if you don't know how, see above)
and disable tracker (System-Preferences-Search and Indexing, clear
Enable Indexing). Personally, I consider the capability a waste of time
and space. Sorry, Jamie -- that is not a dig at your tracker; on every
OS that has
@Noel: you can disable tracker for new accounts deleting the corresponding
files in /etc/xdg/autostart.
However, this isn't related to this bug, so please help fixing it or at least
avoid criticizing tracker; there are better places to do that.
--
Tracker index corruption (was Tracker does not
No need to even do that. Tracker is disabled by default in Ubuntu, so
you have to explicitly enable it in the preferences. This is true even
for new users.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification
I can't restart tracker. If I disable and re-enable indexing in
System-Preferences-Search and Indexing that doesn't do anything. And I
don't have any trackerd executable on my system.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You
I can confirm that bug on the final 9.04 release updating from 8.10
provided solution:
- remove the contents of ~/.cache/tracker and of ~./.local/share/tracker/data
- reindex
didn't work.
aptitude install tracker-utils
tracker-processes -r
seems to work, but system is slower than before.
--
The importance of this bug should be very high - it will impact many
users that have above a few GBs of indexable data. It might even have
blocker potential. Currently I'm learning to live without indexing
until this bug is fixed.
A possible workaround [needs the tracker-utils package - sudo
Tracker is just unusable with Jaunty/ext4 from an upgrade.
I removed it, and installed beagle : indexing is fine, longer but system
doesn't slow down like tracker... and it doesn't hang.
I agree with the last post, this bug have to be fixed before the final
release.
On Wed, Apr 22, 2009 at 2:54
This bug will not be fixed before final release. Fixing it requires
significant changes in Tracker, which are currently happening upstream.
You can't delay an entire release for that.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You
Jaunty does not install tracker by default, thus fixing this in an SRU
is perfectly acceptable.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Have you all tried my solution:
- remove the contents of ~/.cache/tracker and of ~./.local/share/tracker/data
- reindex
Chris: as far as I understand the situation, this bug only affects
people who upgraded to Jaunty somewhere are the beta. Is that true?
--
Tracker index corruption (was Tracker
Milan, I can confirm that solution works. I am running the Jaunty beta,
but I did not upgrade to it (completely fresh install on a brand new
hard drive).
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification
I can confirm its still an issue.
My ~/.local/share/tracker/tracker-indexer.log is growing at a rate of
~300 KB/s with the message repeated over:
22 Apr 2009, 14:14:04: Tracker-Warning **: Could not store word 'css':
with fatal error
All other logs are empty. Will try solutions suggested by
Experiencing this both on i386 and PPC, with systems updated to today.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confirming still an issue with my Jaunty RC. I get pop ups saying my
index is corrupted, but whatever I click the message keeps popping up.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a
fyi: problem so far occured here on all upgrades to current release
candidate (from 8.10 or 9.04 alpha/betas), but not on clean/new
installs. Rgds, Dani
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification
I can confirm this problem on a completely clean, brand new install of
the 9.04 beta.
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm the bug cannot be solved by reindexing, only by removing
the contents of ~/.cache/tracker, and of ~./.local/share/tracker/data.
After reindexing then, everything is fine (I'm using version
0.6.93-0ubuntu1).
Maybe a more radical solution should be used by Tracker when the DB is
Martin: In case you're not aware, I think the notification dialog issue
has been addressed here:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/361205
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
You received this bug
Jane Silber (dupe in bug 361021) just confirmed that she is still
suffering from the neverending 100% CPU issue with the latest tracker
(0.6.93-0ubuntu1), so it seems that contrary to comment 21 this is not
fixed yet?
** Also affects: tracker (Ubuntu Jaunty)
Importance: Medium
Status:
As discussed in #ubuntu-desktop, could we drop the broken quasi-
notification-dialog and just do the reindexing if index corruption is
detected? there's no other sane answer anyway, is there?
--
Tracker index corruption (was Tracker does not stop indexing)
https://bugs.launchpad.net/bugs/346912
I have also seen the looping problem Noel Bergman reports above.
dpkg -l | grep tracker
ii libdeskbar-tracker 0.6.93-0ubuntu1
metadata database, indexer and search tool - deskbar-ap
ii libtracker-gtk00.6.93-0ubuntu1
The new version in Jaunty detects corruption and gives you the option of
re-indexing. This should stop the problem where tracker uses 100% CPU
(so I've adjusted the title now) but obviously doesn't stop the
corruption, so I'll keep this report open.
** Summary changed:
- Tracker does not stop
Chris,
Now I am getting a loop of:
Tracker
There was an error while performing indexing:
Index corrupted
dialogs. Cancel it, and it comes back. Click to index all contents, and
it comes back. Click OK, and ...
So choosing to re-index did not appear to help.
I've run tracker-processes
Could someone please clarify the ext4 issue?
- Does tracker 0.6.9x generally have to get corrupted DBs due to a
QDBM-ext4-issue?
- Is there a different solution other than reformatting to ext3 or xyz-fs or
waiting for tracker 0.7.x?
- Specifically: Would it be viable to come up with some
64 matches
Mail list logo
