[Bug 1364780] Re: tracker-extract crashed with SIGABRT in g_malloc0()
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 link which I've added recently to help people investigate these issues, here is the link again: https://wiki.gnome.org/Projects/Tracker/Documentation/Debugging#High_memory_use.3F Are you able to share the output of: $ tracker-extract -v 3 -f /path/to/file ? That might shed some light on this issue. Alternatively, if you could attach the file in question for testing here, that could help too. Thanks :) ** Bug watch added: GNOME Bug Tracker #748608 https://bugzilla.gnome.org/show_bug.cgi?id=748608 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364780 Title: tracker-extract crashed with SIGABRT in g_malloc0() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1364780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418708] [NEW] package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed')
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 Date: Thu Feb 5 19:56:02 2015 DuplicateSignature: package:nvidia-331:331.113-0ubuntu0.1:package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2013-07-31 (554 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to utopic on 2014-10-27 (101 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418708 Title: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: package nvidia-331 is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1418708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538673] Re: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down
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 be brought to its knees if there are broken 3rd party implementations OR files not following standards. This is usually the reason for SIGABRT, it's rarely a Tracker bug. 2. The tracker-extract process has recently had a fail-safe added to it, so if extraction attempts fail more than 'n' times, we will stop trying. This avoids the login, fail, login, fail, etc cycle. 3. If you're seeing high memory use, please file a bug upstream with the file(s) causing this and we will try to fix it. The same with slow down. Some people have crazy PDF content (for example) which can take a LOOONG time to extract and use GBs of memory. This is not Tracker's fault. Finally, I want to add that the reason we have a tracker-extract process is EXACTLY because 3rd party content or libraries are not reliable enough and often deviate from standards. The process is built with crashing expected at some point, and we do try our best NOT to let this happen - but it's not always in our control. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/538673 Title: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/538673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391102] Re: [MRE] Update to tracker 1.0.6
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 Title: [MRE] Update to tracker 1.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1391102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911981 Title: tracker-store uses 100% cpu and fills all the disk space in home partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/911981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364780] Re: tracker-extract crashed with SIGABRT in g_malloc0()
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 crash: $ /usr/libexec/tracker-extract -v 3 -f /path/to/file.mp3 Once you have that crash, a file uploaded here to test with would help hugely. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364780 Title: tracker-extract crashed with SIGABRT in g_malloc0() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1364780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364780] Re: tracker-extract crashed with SIGABRT in g_malloc0()
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. Bare in mind, the memory use in the logs above is more than 256MB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364780 Title: tracker-extract crashed with SIGABRT in g_malloc0() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1364780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273955] Re: Could not run Sparql query: 1.182: syntax error, unexpected character
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273955 Title: Could not run Sparql query: 1.182: syntax error, unexpected character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1273955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 641225] Re: tracker-miner-fs crashed with SIGSEGV in g_slice_alloc()
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/641225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052348] Re: tracker-extract crashed with SIGSEGV in type_check_is_value_type_U()
@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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052348 Title: tracker-extract crashed with SIGSEGV in type_check_is_value_type_U() To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1052348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 478761] Re: failed to start scanner: Invalid argument
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 username to the group lp. I also
Added to /lib/udev/rules.d/40-libsane.rules
MODE=0664, GROUP=lp
So the final line looks like:
ATTRS{idVendor}==04f9, MODE=0664, GROUP=lp,
ENV{libsane_matched}=yes
Note, you may have to:
a) turn off the printer
b) sudo service udev restart
c) log out and log back in (for new group permissions to take effect)
d) turn printer on
Hope this helps.
--
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:
https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/478761/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 478761] Re: failed to start scanner: Invalid argument
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: https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/478761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985573] [NEW] package libsane 1.0.22-7ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the
*** 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 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 12:08:27 2012 DuplicateSignature: Unpacking libsane:i386 (from .../libsane_1.0.22-7ubuntu1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsane_1.0.22-7ubuntu1_i386.deb (--unpack): './lib/udev/rules.d/40-libsane.rules' is different from the same file on the system ErrorMessage: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the system InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) SourcePackage: sane-backends Title: package libsane 1.0.22-7ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the system UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2012-04-12T17:28:48.380162 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- 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: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/985573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985573] Re: package libsane 1.0.22-7ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the s
*** 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: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/985573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899642] [NEW] gdb crashed with SIGABRT in raise()
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 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Dec 3 16:27:11 2011 ExecutablePath: /usr/bin/gdb ProcCmdline: gdb --batch --ex file\ /usr/bin/nautilus --ex core-file\ /tmp/tmpWOpACt --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ (char*)\ __abort_msg Signal: 6 SourcePackage: gdb StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () internal_verror () Title: gdb crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash oneiric -- 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: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/899642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899642] Re: gdb crashed with SIGABRT in raise()
-- 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: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/899642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 831249] Re: tracker version 0.10.19-1 failed to build in oneiric
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 https://bugzilla.gnome.org/show_bug.cgi?id=654824 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/831249 Title: tracker version 0.10.19-1 failed to build in oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/831249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353008] Re: tracker indexes all the time even though only one folder with one file configured for indexing
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 index. Generally the important ones are: IndexRecursiveDirectories, IndexSingleDirectories, IndexRemovableMedia and IndexOpticalDiscs. they all seem to be sensible here though. -- tracker indexes all the time even though only one folder with one file configured for indexing https://bugs.launchpad.net/bugs/353008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355499] Re: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data()
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305739] Re: trackerd should detect corrupt index and reindex
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 for this. -- trackerd should detect corrupt index and reindex https://bugs.launchpad.net/bugs/305739 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346912] Re: Tracker does not stop indexing
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 their databases and they need to reindex everything (if they don't do it from the applet or some graphical interface). -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354567] Re: tracker-indexer crashed with SIGSEGV in g_closure_invoke()
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() https://bugs.launchpad.net/bugs/354567 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354362] Re: tracker-indexer crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
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 remove items from the indexer's queue and stop any extraction going on for a file on a removable media. This should be fixed using the latest and greatest of GVFS and Tracker. Tracker 0.6.92 should have the initial code there for that and there have been some improvements in TRUNK since, but I think we are waiting for a newer GVFS for this. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354236] Re: tracker-indexer crashed with SIGSEGV in IA__g_cclosure_marshal_VOID__OBJECT()
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 | carlosg | 2009-04-01 13:15:36 +0100 (Wed, 01 Apr 2009) | 5 lines 2009-04-01 Carlos Garnacho car...@imendio.com * src/tracker-indexer/tracker-indexer.c (mount_pre_unmount_cb): Check that there's actually a current item before checking whether it's inside the mount. We expect this weeks release of 0.6.93 to fix this issue. -- tracker-indexer crashed with SIGSEGV in IA__g_cclosure_marshal_VOID__OBJECT() https://bugs.launchpad.net/bugs/354236 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355982] Re: trackerd crashed with SIGSEGV in fclose()
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346912] Re: Tracker does not stop indexing
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 happens and a reindex is the only way to fix it. If it keeps happening, we would like to know if it is ONE file which causes this or something else? This should be resolved once we move to SQLite FTS (i.e. remove QDBM). That won't be until 0.7.x though. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346912] Re: Tracker does not stop indexing
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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334386] Re: tracker-extract crashed with signal 5 in g_malloc()
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348885] Re: tracker stops indexing, 100% cpu load
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 https://bugs.launchpad.net/bugs/348885 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303129] Re: tracker shows wrong results
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 instead of an INSERT to manually store statistics. - We now calculate stats based on volumes being mounted or not (before if you unmounted a volume, it would still report them). - We now don't report stats for 0 count items - We now have a cache for stats to improve performance while indexing (1 minute cache before renewal and of course we get updates from the indexer when it is finished too so we don't have to do it after we are finished). I would like to know if this issue is still apparent in 0.6.92. I can't reproduce it at least. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352252] Re: trackerd crashed with SIGSEGV in strlen()
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164006] Re: Tracker, wrong parameters for dcraw
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 https://bugs.launchpad.net/bugs/164006 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353267] Re: tracker-extract crashed with SIGSEGV
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350629] Re: Places - Search files... doesn't start
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350629] Re: Places - Search files... doesn't start
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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350910] Re: tracker hangs while indexing pidgin logs
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! -- tracker hangs while indexing pidgin logs https://bugs.launchpad.net/bugs/350910 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218230] Re: gtk file dialog blocks on trackerd (via dbus) for 25s for users with NFS homedirs
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 https://bugs.launchpad.net/bugs/218230 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346413] Re: tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()
*** 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 processors) for tracker-extract processes and we seem to be getting SIGSEGV because of that It think. This is at least one possible reason. NOTE: tracker-extract is allowed to crash, it is a separate process because some extensions we use to get metadata are buggy and we can not guarantee stability when integrating with so many different libraries to get file metadata. As such we expect a lot of crashes with tracker- extract. We are of course trying to tidy those all up as much as possible. So if you can reindex and get it to crash again, great. Set the verbosity to 3 in $HOME/.config/tracker.cfg and then see which file causes it in $HOME/.local/share/tracker/tracker-extract.log so we can play with that file and figure it out. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354601] Re: Tracker's Evolution module misplaced
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354601] Re: Tracker's Evolution module misplaced
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348885] Re: tracker stops indexing, 100% cpu load
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352822] Re: tracker-extract crashed with SIGSEGV in g_utf8_validate()
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353008] Re: tracker indexes all the time even though only one folder with one file configured for indexing
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 have data constantly changing in that directory. -- tracker indexes all the time even though only one folder with one file configured for indexing https://bugs.launchpad.net/bugs/353008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335911] Re: Tracker's Evolution mail indexation hangs Evolution
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335911] Re: Tracker's Evolution mail indexation hangs Evolution
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 *should* be available in the Jaunty release. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353010] Re: tracker applet doesn't show what directory/file it currently indexes
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 the dark. I suppose we could include the current folder that is being processed. You will have to wait for this sort of feature though since it changes APIs which are stable right now. 0.7 is probably the earliest time we can do this. -- tracker applet doesn't show what directory/file it currently indexes https://bugs.launchpad.net/bugs/353010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352441] Re: file index is too big - discontinuing index
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346912] Re: Tracker does not stop indexing
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346912] Re: Tracker does not stop indexing
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331679] Re: tracker-extract crashed with SIGSEGV in tracker_extract_get_metadata()
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, extractor fixes are constantly being applied upstream, so 0.6.92 may already have a fix for this. -- tracker-extract crashed with SIGSEGV in tracker_extract_get_metadata() https://bugs.launchpad.net/bugs/331679 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303129] Re: tracker shows wrong results
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340055] Re: tracker-extract crashed with signal 5 in g_malloc()
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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 353480] Re: Please merge tracker 0.6.92-1 (main) from Debian unstable
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 required b-deps are not there yet. Right, I haven't been able to test it yet either. Martyn, Philip, will the old-style evolution plugin be deactivated automatically? It is already disabled, Philip did it recently due to all the problems Ubuntu users were reporting. From what I can see in configure.ac, there is Evolution extracter (data-pull):yes (old)(thus always on???) I think so. and in src/tracker-indexer/Makefile.am, libtracker-module-evolution.la is built unconditionally, thus always installed. That's confusing me a bit We should fix this and just remove the whole evolution module stack. Carlos, Philip, any problems with that? -- Forwarded message -- From: Chris Coulson chrisccoul...@googlemail.com Date: 2009/4/1 Subject: [Bug 353480] Re: Please merge tracker 0.6.92-1 (main) from Debian unstable To: mbi...@gmail.com And here is the diff to the current version in Ubuntu ** Attachment added: tracker_0.6.92-1ubuntu1 Ubuntu diff.patch http://launchpadlibrarian.net/24650747/tracker_0.6.92-1ubuntu1%20Ubuntu%20diff.patch -- Please merge tracker 0.6.92-1 (main) from Debian unstable https://bugs.launchpad.net/bugs/353480 You received this bug notification because you are subscribed to tracker in ubuntu. -- Regards, Martyn -- Please merge tracker 0.6.92-1 (main) from Debian unstable https://bugs.launchpad.net/bugs/353480 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346413] Re: tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335911] Re: Tracker's Evolution mail indexation hangs Evolution
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335911] Re: Tracker's Evolution mail indexation hangs Evolution
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324381] Re: trackerd ingores SIGINT when scanning Evolution email for junk
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 Tracker instead and this will be enabled for release 0.6.92 coming this week. -- trackerd ingores SIGINT when scanning Evolution email for junk https://bugs.launchpad.net/bugs/324381 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346421] Re: tracker-extract crashed with SIGSEGV in IA__g_utf8_validate()
*** 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() https://bugs.launchpad.net/bugs/346421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346912] Re: Tracker does not stop indexing
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335911] Re: Tracker's Evolution mail indexation hangs Evolution
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 responding. We have a new method which involves Evolution pushing data to Tracker instead and this will be enabled for release 0.6.92 coming this week. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148207] Re: Thunderbird and Kmail indexing has been disabled
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 want to disable evolution if you are finding you have email issues right now you should be able to do this with the tracker- preferences application or by running trackerd -d evolution or by changing the config file. -- Thunderbird and Kmail indexing has been disabled https://bugs.launchpad.net/bugs/148207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347352] Re: trackerd crashed with SIGSEGV in strcmp()
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 crashed with SIGSEGV in strcmp() https://bugs.launchpad.net/bugs/347352 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346912] Re: Tracker does not stop indexing
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163544] Re: tracker search tool shows no results
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. We have some code in place now to actively unindex content in our idle time. Hopefully this case will be minimised. We also will be moving to FTS soon and that should also improve our situation vastly. -- tracker search tool shows no results https://bugs.launchpad.net/bugs/163544 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148207] Re: Thunderbird and Kmail indexing has been disabled
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 not adding anything useful to this bug report. -- Thunderbird and Kmail indexing has been disabled https://bugs.launchpad.net/bugs/148207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 343752] Re: tracker-extract crashed with SIGSEGV in FcDirCacheLoad()
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282308] Re: tracker-applet crashed with SIGSEGV in g_closure_invoke()
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210967] Re: trackerd indexes when on battery
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 on battery unless it is an initial index. If you want something different as a default, then that's another problem entirely. -- trackerd indexes when on battery https://bugs.launchpad.net/bugs/210967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282308] Re: tracker-applet crashed with SIGSEGV in g_closure_invoke()
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() https://bugs.launchpad.net/bugs/282308 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339445] Re: tracker-extract crashed with SIGSEGV in gst_iterator_next()
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 fixed in TRUNK. Better yet, if you could test with TRUNK, that would be really helpful. We are planning a release this week. It would be great to fix this if it is still an issue. -- tracker-extract crashed with SIGSEGV in gst_iterator_next() https://bugs.launchpad.net/bugs/339445 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339560] Re: stack smashing detected with tracker-indexer
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 we can test against it? Thanks again for filing the bug! -- stack smashing detected with tracker-indexer https://bugs.launchpad.net/bugs/339560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339445] Re: tracker-extract crashed with SIGSEGV in gst_iterator_next()
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 tracker-extract (the --help should provide you with information on how to use it). Thanks -- tracker-extract crashed with SIGSEGV in gst_iterator_next() https://bugs.launchpad.net/bugs/339445 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210967] Re: trackerd indexes when on battery
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 on battery if it is a first time index. Are you able to confirm what your config is using? -- trackerd indexes when on battery https://bugs.launchpad.net/bugs/210967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210967] Re: trackerd indexes when on battery
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210967] Re: trackerd indexes when on battery
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. -- trackerd indexes when on battery https://bugs.launchpad.net/bugs/210967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163544] Re: tracker search tool shows no results
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 directory. There are no results, but the search tool says there are on the left in the categories. We are currently working on improving this, but right now, unindexing content is far too slow to be done on delete events. The fix for this is to remove hits when they are searched for and the data has gone from the main database. This is currently broken too and we are in the process of fixing it this week. Regarding the unindexing being too slow, this is something that will improve after the next release (next week 0.6.91) which will have support for SQLite FTS and should be much faster than the QDBM database we are currently using (which we estimate is taking up 75% of the time we spend indexing). -- tracker search tool shows no results https://bugs.launchpad.net/bugs/163544 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163544] Re: tracker search tool shows no results
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 linux kernel (i.e. 26k files) and search for kernel, that's a big number to be out by. It isn't that hard to be out. NOTE: Carlos Garnacho, committed his patch today which corrects this slowly over time, so for big removals it will be noticeable, for small deletes it should work properly now. Romano, it may well be that we don't handle .tex files properly - I would need a file to test with and to add it to my local monitored directories to see what happens with it to test that. Sounds like a simple case of just not indexing that file type. -- tracker search tool shows no results https://bugs.launchpad.net/bugs/163544 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47768] Re: Mount Root Files System Failed
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 system ... -- And that is it, nothing further, I waited at least 10 minutes. If I run in single user mode I see these lines before it stops: -- [12.344000] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [12.344000] ata3.00: ata_hpa_resize 1: sectors = 625142448, hpa_sectors = 4385456 [12.344000] ata3.00: ATA-6: WDC WD3200JD-22KLBO, 08.05J08, max UDMA/100 [12.344000] ata3.00:625142448 sectors, multi 16: LBA48 -- These lines refer to my one and only SATA hard disk. I can still boot with 2.6.20-13. It looks like the SATA controller may have changed between -13 and -14, is there any way (if so) to change it back temporarily until a fix is in place? -- Mount Root Files System Failed https://bugs.launchpad.net/bugs/47768 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106260] Boot hangs with Waiting for root file system since kernel 2.6.20-14
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 ... Running /scripts/local-top ... OK Waiting for root file system ... -- If I run in single user mode I see these lines before it stops: -- [ 12.344000] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 12.344000] ata3.00: ata_hpa_resize 1: sectors = 625142448, hpa_sectors = 4385456 [ 12.344000] ata3.00: ATA-6: WDC WD3200JD-22KLBO, 08.05J08, max UDMA/100 [ 12.344000] ata3.00: 625142448 sectors, multi 16: LBA48 -- These lines refer to my one and only SATA hard disk on /dev/sda3. I have spent some time looking around for other people with this issue and just wanted to clarify that my /etc/fstab is using UUIDs instead of /dev/hda or /dev/sda devices (which seemes to be a common issue for some people). I can still boot with 2.6.20-13. It looks like the SATA controller may have changed between -13 and -14. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- 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 contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106260] Re: Boot hangs with Waiting for root file system since kernel 2.6.20-14
** 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 contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
