GNOME Bugzilla – Bug 687108
tracker-miner-fs crashed with SIGSEGV in g_str_hash()
Last modified: 2012-10-29 18:03:42 UTC
Original description from: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1031753 this bug affects 18 people ---------------------------------------------: On starting the external program catoscape 2.8.3 from command line with this crash happends. --------------------------------------------- Terminal input/output: user@user-HP-655-Notebook-PC:~$ java -jar Software/cytoscape-2.8.3/cytoscape.jar cytoscape.CytoscapeInit[INFO]: CytoscapeInit static initialization cytoscape.CytoscapeInit[INFO]: Parent_Dir: /home/user/.cytoscape created. cytoscape.CytoscapeInit[INFO]: Config file: /home/user/.cytoscape/cytoscape.props created. cytoscape.CytoscapeInit[INFO]: Config file: /home/user/.cytoscape/vizmap.props created. cytoscape.plugin.PluginManager[INFO]: Creating directories for /home/user/.cytoscape/2.8/plugins cytoscape.plugin.PluginTracker[WARN]: Plugin tracker file: /home/user/.cytoscape/2.8/track_plugins.xml cytoscape.CytoscapeInit[INFO]: Log information can now be found in the Help->Error Console menu cytoscape[INFO]: starting delete action cytoscape[INFO]: ending delete action cytoscape[INFO]: PreferenceAction()... cytoscape.actions.BookmarkAction[INFO]: BookmarkAction()... -------------------------------------------- You can get cytoscape from: chianti.ucsd.edu/Cyto-2_8_3/cytoscape-2.8.3.tar.gz when the download is not working directly, please try it with http://cytoscape.org/download.php or http://cytoscape.org/ ---------------------------------------- Steps to reproduce: 1.Download Cytoscape from one of the links given above 2.Extract it. 3.start Cytoscape from terminal with java -jar /...your directory.../cytoscape-2.8.3/cytoscape.jar 4.See the terminal output also given above. 5.See apport collecting a crash of tracker-miner during start of Cytoscape. 6Done. This seems to happen only of the very first run of Cytoscape. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: tracker-miner-fs 0.14.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-7.7-generic 3.5.0 Uname: Linux 3.5.0-7-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Wed Aug 1 14:20:47 2012 ExecutablePath: /usr/lib/tracker/tracker-miner-fs InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722) ProcCmdline: /usr/lib/tracker/tracker-miner-fs ProcEnviron: PATH=(custom, no username) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fba8a476590 <g_str_hash>: movsbl (%rdi),%edx PC (0x7fba8a476590) ok source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libtracker-miner-0.14.so.0 ?? () from /usr/lib/libtracker-miner-0.14.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
StacktraceTop: g_str_hash (v=0x0) at /build/buildd/glib2.0-2.33.6/./glib/ghash.c:1730 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x7fba780044c0) at /build/buildd/glib2.0-2.33.6/./glib/ghash.c:401 g_hash_table_lookup (hash_table=0x7fba780044c0, key=key@entry=0x0) at /build/buildd/glib2.0-2.33.6/./glib/ghash.c:1074 check_ignore_next_update (fs=fs@entry=0xe0c030, queue_file=queue_file@entry=0xf53400) at tracker-miner-fs.c:1689 item_queue_get_next_file (priority_out=<synthetic pointer>, source_file=<synthetic pointer>, file=<synthetic pointer>, fs=0xe0c030) at tracker-miner-fs.c:1815
Created attachment 227520 [details] stacktrace
Created attachment 227521 [details] threadstacktrace
I am pretty sure this is already fixed and if Ubuntu would upgrade Tracker it likely wouldn't be an issue any longer. I am going to mark this as dup for now. IF this is not happening with 0.14.3 please reopen. Thanks. *** This bug has been marked as a duplicate of bug 675786 ***