Bug 1705050

Summary: [abrt] gjs: tracker_offsets_function(): gjs-console killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Tim Waugh <twaugh>
Component: gjsAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: fzatlouk, gnome-sig, mr.marcelo.barbosa, mvwa, otaylor, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/deb45333758698f29888272f123e727923a4969d
Whiteboard: abrt_hash:f7a1f5bad3af57ac22525ef7d55618cd78b0861d;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-26 16:02:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Tim Waugh 2019-05-01 09:55:00 UTC
Version-Release number of selected component:
gjs-1.56.1-2.fc30

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
crash_function: tracker_offsets_function
executable:     /usr/bin/gjs-console
journald_cursor: s=dc70aeba87244116b17756552de0de42;i=137b9;b=59ff9be19b4e43c684b139c6c26ddb1b;m=10a212d55;t=587d05c154c86;x=f4f24594e53e4ec3
kernel:         5.0.9-301.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 tracker_offsets_function at ../src/libtracker-fts/tracker-fts-tokenizer.c:259
 #1 fts5ApiInvoke at sqlite3.c:215351
 #2 fts5ApiCallback at sqlite3.c:18775
 #3 sqlite3VdbeExec at sqlite3.c:90279
 #4 sqlite3Step at sqlite3.c:81338
 #5 sqlite3_step at sqlite3.c:15865
 #7 stmt_step at ../src/libtracker-data/tracker-db-interface-sqlite.c:1350
 #8 db_cursor_iter_next at ../src/libtracker-data/tracker-db-interface-sqlite.c:2816
 #9 tracker_db_cursor_iter_next_thread at ../src/libtracker-data/tracker-db-interface-sqlite.c:2571
 #10 g_task_thread_pool_thread at ../gio/gtask.c:1404

Comment 1 Tim Waugh 2019-05-01 09:55:05 UTC
Created attachment 1560697 [details]
File: backtrace

Comment 2 Tim Waugh 2019-05-01 09:55:06 UTC
Created attachment 1560698 [details]
File: cgroup

Comment 3 Tim Waugh 2019-05-01 09:55:08 UTC
Created attachment 1560699 [details]
File: core_backtrace

Comment 4 Tim Waugh 2019-05-01 09:55:09 UTC
Created attachment 1560700 [details]
File: cpuinfo

Comment 5 Tim Waugh 2019-05-01 09:55:11 UTC
Created attachment 1560701 [details]
File: dso_list

Comment 6 Tim Waugh 2019-05-01 09:55:14 UTC
Created attachment 1560702 [details]
File: environ

Comment 7 Tim Waugh 2019-05-01 09:55:15 UTC
Created attachment 1560703 [details]
File: exploitable

Comment 8 Tim Waugh 2019-05-01 09:55:16 UTC
Created attachment 1560704 [details]
File: limits

Comment 9 Tim Waugh 2019-05-01 09:55:18 UTC
Created attachment 1560705 [details]
File: maps

Comment 10 Tim Waugh 2019-05-01 09:55:19 UTC
Created attachment 1560706 [details]
File: mountinfo

Comment 11 Tim Waugh 2019-05-01 09:55:22 UTC
Created attachment 1560707 [details]
File: open_fds

Comment 12 Tim Waugh 2019-05-01 09:55:24 UTC
Created attachment 1560708 [details]
File: proc_pid_status

Comment 13 Matt W 2019-07-06 16:42:36 UTC
Similar problem has been detected:

The problem occurs when the screen was turned off (automatically, after a period of inactivity). 
The login screen is completely frozen, only the mouse pointer moves. 
It is possible to login to tty with 'alt'+'ctrl'+'F2'

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
crash_function: tracker_offsets_function
executable:     /usr/bin/gjs-console
journald_cursor: s=3836cd3c30764c8f90c18048c849f6f6;i=2865;b=71f6c8c4f6df4b9797598c4282fd2f2f;m=135b53665;t=58cff87134feb;x=4554f613a3d8a347
kernel:         5.1.16-300.fc30.x86_64
package:        gjs-1.56.2-4.fc30
reason:         gjs-console killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Ben Cotton 2020-04-30 21:37:23 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Ben Cotton 2020-05-26 16:02:34 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.