Hi Ian,
It may well be a rogue file being indexed.
We've just fixed a bug which was allocating way too much memory here:
https://bugzilla.gnome.org/show_bug.cgi?id=748608
This started off as a Tracker bug in tracker-extract too. Turned out to
be a library we depend on.
The bug also mentions a
Public bug reported:
Simple apt-get update failure.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.113-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
So, there are a few things mentioned here, let me answer them:
1. Any case where you see SIGABRT is usually Tracker killing itself due
to seriously high memory use. This has been removed for 1.3.x onwards.
What this means is, instead of getting a SIGABRT and the process
closing, your machine will
Please can we push this, the crashes that are fixed are being witnessed
for me every time I start my desktop daily. This release fixes that
crash!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391102
Really, you're using Tracker 0.10?
You have / had databases in the cache dir which haven't been used by
Tracker in about half a decade, probably longer.
I would suggest you upgrade and update your config (at least to the
default) to avoid these sort of problems as best as possble.
--
You
Hi all,
I am one of the upstream maintainers. I think I've seen this bug recently but
need a way to reliably reproduce it to fix it.
Does anyone have a way to do that?
Normally, if you know the file in question being extracted, you should
be able to run this on the command line to reproduce the
Just to add, my initial suspicion is either:
a) a rogue extractor
b) the kernel could be killing us due to too much memory use, based on our call
to setrlimit() which we mainly only use in tracker-extract. The limit = CLAMP
(total_halfed, MEM_LIMIT_MIN, G_MAXLONG); where MEM_LIMIT_MIN = 256 Mb.
Hi there Mike, I am the upstream maintainer. Are you able to find out
what SPARQL query is being used here? If you need help with how to do
that, let me know what process you're using and I can assist! :)
Thanks for reporting the bug!
--
You received this bug notification because you are a
Is anyone able to reproduce this reliably?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/641225
Title:
tracker-miner-fs crashed with SIGSEGV in g_slice_alloc()
To manage notifications about this
@Laurent Bonnaud, are you able to reproduce this consistently using:
/usr/libexec/tracker-extract -v 3 -f $FILENAME
?
It certainly looks like a Gstreamer bug yes. Are you able to test with
0.15.x? (or master?) - they use the new GStreamer 1.x APIs and this
might show the bug is fixed.
--
I have a Brother MFC-7320 and I was getting this this afternoon:
$ scanimage -t
scanimage: open of device brother3:bus3;dev1 failed: Invalid argument
Using strace, I also saw the USBDEVFS_CONTROL error being reported up
the stack from the ioctl call.
What fixed this for me was adding my
I am also using Ubuntu Pangolin (beta2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/478761
Title:
failed to start scanner: Invalid argument
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 952544 ***
https://bugs.launchpad.net/bugs/952544
Public bug reported:
Tried installing latest version of skype from skype.com as of today.
Dependencies failed to install.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libsane 1.0.22-7ubuntu1
*** This bug is a duplicate of bug 952544 ***
https://bugs.launchpad.net/bugs/952544
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985573
Title:
package libsane 1.0.22-7ubuntu1 [modified:
Public bug reported:
Occurred while getting gdb information for nautilus crash reported in
bug #899641
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gdb 7.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899642
Title:
gdb crashed with SIGABRT in raise()
To manage notifications about this bug go to:
This has been reported in an upstream but too:
https://bugzilla.gnome.org/show_bug.cgi?id=654824
You can blame the camel API for changing yet again here. We're trying to
get this fixed before we start 0.12.x releases in the next few weeks.
** Bug watch added: GNOME Bug Tracker #654824
Yes, that looks like a bug to me. Can you set Verbosity=3 and re-run
tracker-control -ts to make sure we capture what is happening on
startup. To find out how to do this see:
http://live.gnome.org/Tracker/Documentation/Debugging
The logs should indicate which directories we are trying to
I need to know where in that function it crashes (a line number or
something would help) - but just looking at _utils_get_data() I can't
see what the problem is.
--
tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data()
https://bugs.launchpad.net/bugs/355499
You
We committed some code yesterday which now notifies the user if the
index becomes corrupt. It will also present a notification (if running
the applet) allowing the user to attempt a reindex.
We are working on shutting down nicely when going into suspend mode
which we believe is partially to blame
Michael, Chris, yes, it should be added to tracker-utils. It also allows
the user to kill/terminate all tracker processes and which is most
useful, reset all tracker databases after killing processes. The
tracker-processes -r command is now what we suggest to use when people
have corruption in
Tracker will stop indexing if the file system becomes too full. You can
set the percentage in the config (and tracker-preferences). Usually 1%
left is where it stops.
It certainly shouldn't crash.
--
tracker-indexer crashed with SIGSEGV in g_closure_invoke()
Actually, Tracker will index removable media by default, you have to
disable it if you don't want that.
This crash is possibly related to Tracker and the pre-umount signal from
GVFS. This was not implemented in GVFS until recently (last few weeks)
and we implemented it and the Tracker solution to
After some investigation and discussion with Carlos (who wrote the
code), he is confident his commit shortly AFTER 0.6.92 was released
fixed this issue:
mar...@petunia:~/Source/tracker$ svn log -r3159 ChangeLog
r3159 |
Thanks for spotting, just fixed this in TRUNK, it will be available in
release 0.6.93 later this week.
--
trackerd crashed with SIGSEGV in fclose()
https://bugs.launchpad.net/bugs/355982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not having tracker-processes is a packaging bug, it is available from
0.6.92 onwards, but it wasn't included. There is a bug about it here
somewhere :)
Those two warnings above are fine to ignore.
The logs you show above is with QDBM failing to index a word. We are not
entirely sure why this
Actually, we should probably detect such a case and pause indexing for
the shutdown as soon as we know the process has started.
--
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
This is fixed upstream, we now listen to GVFS pre-unmount signal, which
was broken and recently patched upstream too.
--
tracker-extract crashed with signal 5 in g_malloc()
https://bugs.launchpad.net/bugs/334386
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi pt123, the first error shouldn't happen, the second and third are
expected - we don't use that .sql file anyway so it is just a warning
about something unused at this point. I will be fixed when SQLite FTS is
used.
--
tracker stops indexing, 100% cpu load
Marco, I can't say I have seen it, I know 1 or 2 people have reported
such an issue, but I have failed to see how to reproduce it with
TRUNK/0.6.92 and above. We have changed a lot of things in this area in
the past month or so. Namely:
- We now calculate stats based on DB functions with COUNT
I think this is fixed now, the signal signature was incorrect and we
fixed it recently.
--
trackerd crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/352252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
If you are using imagemagick, you must be using an old version of
Tracker which is no longer supported. Loading the CPU to 50% really
isn't a bad thing especially if you are doing nothing else. Also, it
depends on your system of course.
--
Tracker, wrong parameters for dcraw
We have fixed many memory leaks / corruptions in the tracker-extract app
this week. We are considering releasing again ASAP.
--
tracker-extract crashed with SIGSEGV
https://bugs.launchpad.net/bugs/353267
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have seen the G_IS_FILE() issue to, really hard to replicate that
condition so I haven't been able to fix it.
Andreas, gnome-search-tool is not part of Tracker. This error, however,
is from Tracker.
--
Places - Search files... doesn't start
https://bugs.launchpad.net/bugs/350629
You received
I should also add, this error is not a crasher and it doesn't stop you
from starting Tracker or any other application.
--
Places - Search files... doesn't start
https://bugs.launchpad.net/bugs/350629
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can you change the config verbosity ($HOME/.config/tracker/tracker.cfg
to 3 and re-run. The indexer logs should say what is going on and which
file is causing the problems, it is in:
$HOME/.local/share/tracker/tracker-indexer.log
Any further information you can give us here would really help!
This was problematic with a broken API in older versions of
libtrackerclient and the file chooser dialog complaining about missing
symbols IIRC. This should have been fixed for a while now.
--
gtk file dialog blocks on trackerd (via dbus) for 25s for users with NFS
homedirs
*** This bug is a duplicate of bug 346388 ***
https://bugs.launchpad.net/bugs/346388
This should be fixed by now. I think there is a patch which plays with
setrlimit. I think a lot of crashes in the extractor are due to this -
currently we set memory limits of 128Mb (512Mb for AMD64
Hi Chris, this should be fixed. I will double check.
--
Tracker's Evolution module misplaced
https://bugs.launchpad.net/bugs/354601
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK, I will look into fixing it Monday. I am likely to do a release next
week sometime with all the crashers and leaks we managed to fix in the
last week already.
--
Tracker's Evolution module misplaced
https://bugs.launchpad.net/bugs/354601
You received this bug notification because you are a
We think this is now fixed upstream. Possibly in release 0.6.92.
Basically, the sooner QDBM is terminated from Tracker, the sooner we
stop getting these silly issues and warnings.
--
tracker stops indexing, 100% cpu load
https://bugs.launchpad.net/bugs/348885
You received this bug notification
This is fixed in 0.6.92 release last week.
--
tracker-extract crashed with SIGSEGV in g_utf8_validate()
https://bugs.launchpad.net/bugs/352822
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
tracker-preferences allows you to change WHERE gets indexed, $HOME is
the default and why shouldn't it be, from a fresh install, nothing
exists to be indexed really. If it says it is always indexing then it
can be one of two things.
1. The bug we fixed where the status was always indexing.
2. You
OK, so I did test the same steps as in the screen cast and I couldn't
reproduce it with TRUNK at the time. We just release (last Friday)
tracker 0.6.92. I believe this is fixed and from what I have heard the
packages should be integrated this week some time.
--
Tracker's Evolution mail
Also, I should add that we disabled Evolution support by default using
the old plugin mechanism which reads their mail :) so to speak by
peaking at the SQLite DBs. Now we use a push plugin so Evolution
passes us the information we need. I believe this has to be enabled on
the Evolution side and
Well, we already have the dialog to fetch the statistics and we already
tell the user how many files we have indexed so far out of how many we
know about. Plus we give a time estimation. I did (for 0.6.92) add more
states (watching, crawling, optimising and shutting down) to keep the
user out of
OK, this is for an old version of Tracker AFAICS and no longer
supported. Can you try 0.6.92, it is vastly superior.
--
file index is too big - discontinuing index
https://bugs.launchpad.net/bugs/352441
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also, if trackerd -r didn't work, it is because you still had tracker
processes running which were using the database or writing to it.
--
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
This should be fixed in TRUNK. A reindex is needed when it happens, you
can use tracker-processes -r to do that, note it will kill all processes
and databases. If you don't have that command, you need a newer version
:)
--
Tracker does not stop indexing
https://bugs.launchpad.net/bugs/346912
You
Hi, I would need to know which file you were trying to extract which
caused this crash. We put the extraction in a separate binary because it
is likely to crash with so many variable formats we have to work with.
If you can provide that file, I can test it here and come up with a fix.
Note,
I think I know the issue you are talking about. I think 0.6.92 resolves
this issue.
--
tracker shows wrong results
https://bugs.launchpad.net/bugs/303129
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We have recently fixed some memory corruption and leakage in the
GStreamer extractor. I think this is fixed in trunk but possibly NOT
0.6.92.
--
tracker-extract crashed with signal 5 in g_malloc()
https://bugs.launchpad.net/bugs/340055
You received this bug notification because you are a member
Michael Biebl wrote:
Hi,
Hi :)
maybe you want to enable the new-style evolution plugin.
For that you have to build-depend on
evolution-dev (= 2.25.5)
and
evolution-data-server-dev (= 2.25.5)
These are the requirements in configure right now.
I couldn't test this on Debian though, as the
The crash here doesn't look like it is in Tracker. The data here doesn't
help identify the problem area either :(
--
tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()
https://bugs.launchpad.net/bugs/346413
You received this bug notification because you are a member of Ubuntu
Tiefflieger, what version are you using?
--
Tracker's Evolution mail indexation hangs Evolution
https://bugs.launchpad.net/bugs/335911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hmm, we did improve the preferences dialog (I am sure for 0.6.91) I am
surprised to hear disabling mail doesn't work. Can you give me the exact
steps you use so I can try to reproduce it?
--
Tracker's Evolution mail indexation hangs Evolution
https://bugs.launchpad.net/bugs/335911
You received
This bug is related to an obsolete version and is no longer valid. It
was fixed upstream.
We have disabled support for the Evolution SQLite DB inspection code
since it was causing problems with Evolution running and not responding.
We have a new method which involves Evolution pushing data to
*** This bug is a duplicate of bug 346575 ***
https://bugs.launchpad.net/bugs/346575
This has been fixed upstream, TRUNK now NULL checks before calling
g_utf8_validate().
0.6.92 will be released this week with the fix.
--
tracker-extract crashed with SIGSEGV in IA__g_utf8_validate()
This is a QDBM problem. We are replacing this database in the coming
months. For now, we are not sure why it does this but it usually happens
when your index is corrupt.
--
Tracker does not stop indexing
https://bugs.launchpad.net/bugs/346912
You received this bug notification because you are a
We have seen several reports of this. It seems that our peeking at
Evolution's SQLite database is causing Evolution problems and not doing
us any favours either.
We have disabled support for the Evolution SQLite DB inspection code
since it was causing problems with Evolution running and not
Jack, there is no support for Thunderbird, as in, no code ever written
to handle it. For logging, you can edit
$HOME/.config/tracker/tracker.cfg and change Verbosity to 3 (max) and
you will find logs for trackerd, tracker-indexer and tracker-extract all
in $HOME/.local/share/tracker/.
You might
Thanks for reporting this bug. I have never seen such a crash, but I
just fixed it anyway. I know where this happens. We now use g_strcmp0()
instead in all of the places we use this function
(g_list_find_custom()).
This will be fixed in the release I am doing this week (0.6.92).
--
trackerd
if you use the applet to reindex, that should fix it. The equivalent
command is $prefix/libexec/trackerd -r
--
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.
--
hirak99, by then it is too late, if you click the next button and it
shows you nothing and all that changes is the statistics on the left
hand side then the user is confused and thinks the button doesn't work.
I agree, we should have something better though to let the user know
what is going on.
Thunderbird and KMail were never supported.
We spent the last 12 months refactoring the code because it was needed
There have been some serious speed improvements and system performance is much
better while it is in use.
We accept patches. If you want to help out great :), if not, you're really
Hi, I just fixed a nasty crasher in the applet today. So this is
probably fixed in TRUNK.
--
tracker-extract crashed with SIGSEGV in FcDirCacheLoad()
https://bugs.launchpad.net/bugs/343752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The tracker-applet has seriously been improved since v0.6.6. The trace
doesn't look any good to me either.
--
tracker-applet crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/282308
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, I have fixed the config here a bit. It wasn't loading the defaults
in properly if *some* didn't exist in the .cfg. But the default here
works as I would expect anyway, so with no config here, the default is:
BatteryIndex=true
BatteryIndexInitial=false
Note, this means it will NOT index
So much has changed since 0.6.6 not only to the indexer and the trackerd
but also the applications. I can't see what is going on from this stack
trace. I personally would close the bug as NEEDINFO/WONTFIX or OBSOLETE.
--
tracker-applet crashed with SIGSEGV in g_closure_invoke()
Hi,
Can you find out which file caused this crash? We are constantly fixing
the extractors and this might have already been fixed. It looks like it
was a media file of some sorts since GStreamer is in the back trace. Any
chance you could send us the file so we can test with it? It may already
be
Hi,
Wow, this code has been in use for a while and we have not seen this. I
just checked and double checked your logic and you are right. Superb
catch! Now committing a fix to TRUNK. This will be available in this
weeks release 0.6.91.
Do you have the file here which is causing this problem so
Thanks for the additional information here. Looking at the code, it all
seems fine. Unless this is some internal GStreamer bug, I don't see what
is going wrong here.
Are you able to send us the file which causes this situation? You can
probably test it in a stand alone manner using
I am now testing this and will try to fix it for this weeks release
(0.6.91).
Asa, Jamin, just to confirm, what are your config values set to? There
are 2:
BatteryIndex
BatteryIndexInitial
Of course, if you have BatteryIndex=false, but you have
BatteryIndexInitial=true, then it will index
I just tested this with TRUNK for the last hour or so and it works for
me. Can you tell me exactly what you are doing to make this fail so I
can try to reproduce it?
--
trackerd indexes when on battery
https://bugs.launchpad.net/bugs/210967
You received this bug notification because you are a
Asa, ah I see, I will try to reproduce it tomorrow and come up with a
fix. It should write any changes in the config to the .cfg file. Looks
like you might have stumbled onto another bug as part of this :) I will
let you know how I get on tomorrow!
Thanks again for the extra information.
--
Note: If you are using tracker-search-tool and it says you have 10 files
but no results are shown, this is normal behaviour. The hit score you
get back is an indication. This is exactly the same way that Google
works. This is reproducible by indexing the kernel source, then removing
the top level
mlissner, I know this is going to sound silly, but if you move a
directory with 200 files in it to some place Tracker doesn't monitor, it
is considered a DELETE event. In that case, you then can have a lot of
hits which are grossly misreported by the search tool. If you do the
same thing with the
I just updated on Feisty to kernel 2.6.20-14 and when I try to reboot (with
-quiet removed from the grub config) I get the following:
--
Loading essential drivers ... OK
Running /scripts/init-premount... OK
Mounting root file system ...
Running /scripts/local-top ... OK
Waiting for root file
Public bug reported:
I just updated on Feisty to kernel 2.6.20-14 from -13 and when I rebooted it
stalled at almost 0%.
I changed grub and removed the -quiet switch and I get the following:
--
Loading essential drivers ... OK
Running /scripts/init-premount... OK
Mounting root file system ...
** Attachment added: Output of lspci
http://librarian.launchpad.net/7320982/pci.txt
--
Boot hangs with Waiting for root file system since kernel 2.6.20-14
https://bugs.launchpad.net/bugs/106260
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
80 matches
Mail list logo
