On Wed, 2017-02-22 at 11:09 +0100, Carlos Garnacho wrote: > Hi Chris, > Good morning Carlos
> > sincerely apologize. I've been experiencing this - tracker-store > > crashed with SIGSEGV in g_slice_alloc() almost daily since > > 12/31/2016. > > It's listed here - https://bugs.launchpad.net/ubuntu-gnome/+bug/165 > > 3392 > > still shown as new and assigned to nobody. Here is some version > > information: > > Strange, that link doesn't work here, just says "page not found". > Anyway, SIGSEGV when allocating memory is a pretty good indicator of > memory corruption. Valgrind could be of help there, you can run > tracker-store through valgrind with: > Ubuntu Launchpad has the bug info marked as 'Private' for some reason. Here is the information initially entered: Have no idea what causes this however another issue I keep seeing in my syslog is tracker-extract.desktop[3406]: (tracker-extract:3406): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: tracker 1.8.2-0ubuntu1~xenial3 [origin: LP-PPA-gnome3-team- gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sat Dec 31 17:20:14 2016 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-10-24 (799 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/lib/tracker/tracker-store ProcEnviron: XDG_RUNTIME_DIR=<set> SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f696f421a9a <g_slice_alloc+426>: mov (%rax),%rdx PC (0x7f696f421a9a) ok source "(%rax)" (0x69617274736e6f63) not located in a known VMA region (needed readable region)! destination "%rdx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_copy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-store crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo > killall -15 tracker-store; valgrind --leak-check=full --num- > callers=25 > --log-file=~/not-indexed-folder/tracker-store-valgrind.txt > /usr/lib/tracker/tracker-store > > This will make tracker-store real slow (and all re-indexing process > in > chain effect), but it should catch and log invalid frees/writes into > that log file. When the first crash happened the following files were created and uploaded to the bug report: CoreDump.gz; CrashDB.txt; Dependencies.txt; Disassembly.txt; JournalErr ors.txt; ProcMaps.txt; ProcStatus.txt; Registers.txt; Stacktrace.txt; T hreadStacktrace.txt Other than the CoreDump.gz which is 2.4mb the others are small test files which I could put up on pastebin if any would help. In Jan of this year a comment was made to the bug You could ppa-purge the GNOME3 Staging PPA if you want a more stable Ubuntu. Or you could update to Ubuntu 16.10 which has GNOME 3.20 but without that new version of tracker yet. Since 16.10 is not a LTS release, you'll need to update for every release until the next LTS, 18.04. That's something I'd much rather not do since I went through that years ago with Mandrake and Mandriva always having to update the whole system when a new release came out. > > Oh, also make sure you have debug packages for tracker, I forgot what > the ubuntu way is for that. > I've got the page for 'debugging Ubuntu' bookmarked, I'll take a look. > > > > Distributor ID: Ubuntu > > Description: Ubuntu 16.04.2 LTS > > Release: 16.04 > > Codename: xenial > > > > chris@localhost:~$ apt-cache policy tracker > > tracker: > > Installed: 1.8.3-0ubuntu0~xenial1 > > Candidate: 1.8.3-0ubuntu0~xenial1 > > Version table: > > *** 1.8.3-0ubuntu0~xenial1 500 > > 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubu > > ntu > > xenial/main amd64 Packages > > Hmm, however, 1.8.x is slightly old now, you should perhaps try first > with the 1.10.x stable branch which has been out for a few months > now. Not really sure how I'd go about updating to the 1.10x branch since I'm using the Ubuntu PPA. > Although I tbh don't remember recent tracker-store memory corruption > bugs, nor having seen anything like that fixed recently. > GDM3 version chris@localhost:~$ apt-cache policy gdm3 gdm3: Installed: 3.20.1-1ubuntu2~ubuntu16.04.1 Candidate: 3.20.1-1ubuntu2~ubuntu16.04.1 Version table: *** 3.20.1-1ubuntu2~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages > If after updating the bug still persists, please file a bug at > https://bugzilla.gnome.org/enter_bug.cgi?product=tracker with the > valgrind info and we'll take it from there. > > Cheers, > Carlos > Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 08:10:05 up 11:31, 1 user, load average: 0.45, 0.25, 0.38 Description: Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic
signature.asc
Description: This is a digitally signed message part
_______________________________________________ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
