nautilus crashed with signal 5 in g_settings_get_value()

Bug #1712229 reported by Section Zy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Incomplete
High
Unassigned

Bug Description

Happen randomly, no route to find the source cause.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.25.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 22 09:26:10 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-06-10 (72 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: nautilus /home/username/Downloads/RLinux5_x64.deb
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
Title: nautilus crashed with signal 5 in g_settings_get_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Section Zy (sectionzy) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_settings_schema_get_value (schema=0x360205ae30, key=0x3600d91922 "fts-default") at ../../../../gio/gsettingsschema.c:967
 g_settings_schema_key_init (key=key@entry=0x7ffc78ae22a0, schema=0x360205ae30, name=name@entry=0x3600d91922 "fts-default") at ../../../../gio/gsettingsschema.c:1246
 g_settings_get_value (settings=0x360205ae10, key=key@entry=0x3600d91922 "fts-default") at ../../../../gio/gsettings.c:1203
 g_settings_get_boolean (settings=<optimized out>, key=key@entry=0x3600d91922 "fts-default") at ../../../../gio/gsettings.c:2127
 nautilus_search_popover_init (self=0x360241c1f0) at ../src/nautilus-search-popover.c:914

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report

Could you use that command and copy the output here?
$ sudo /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas /usr/share/glib-2.0/schemas

information type: Private → Public
Changed in nautilus (Ubuntu):
importance: Medium → High
status: Confirmed → Incomplete
Revision history for this message
Zhenqing Hu (huzq85) wrote : Re: [Bug 1712229] Re: nautilus crashed with signal 5 in g_settings_get_value()
Download full text (5.1 KiB)

hi,

Thank you for following up.

This is the message after I executed the cmd:

=============================================================================

No such key 'Gtk/IMModule' in schema
'org.gnome.settings-daemon.plugins.xsettings' as specified in override
file '/usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override';
ignoring override for this key.
*** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas':
double free or corruption (fasttop): 0x000000eba61cdd00 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7f549cd230bb]
/lib/x86_64-linux-gnu/libc.so.6(+0x82c6a)[0x7f549cd2cc6a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f549cd30d5c]
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x4046)[0xeba3fa0046]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f549ccca421]
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x409a)[0xeba3fa009a]
======= Memory map: ========
eba3f9c000-eba3fa6000 r-xp 00000000 08:06 524524
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
eba41a5000-eba41a6000 r--p 00009000 08:06 524524
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
eba41a6000-eba41a7000 rw-p 0000a000 08:06 524524
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
eba5f7a000-eba61ec000 rw-p 00000000 00:00 0
[heap]
7f5498000000-7f5498021000 rw-p 00000000 00:00 0
7f5498021000-7f549c000000 ---p 00000000 00:00 0
7f549c171000-7f549c187000 r-xp 00000000 08:06 786610
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f549c187000-7f549c386000 ---p 00016000 08:06 786610
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f549c386000-7f549c387000 r--p 00015000 08:06 786610
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f549c387000-7f549c388000 rw-p 00016000 08:06 786610
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f549c388000-7f549c819000 r--p 00000000 08:06 263544
/usr/lib/locale/locale-archive
7f549c819000-7f549c831000 r-xp 00000000 08:06 786501
/lib/x86_64-linux-gnu/libpthread-2.24.so
7f549c831000-7f549ca31000 ---p 00018000 08:06 786501
/lib/x86_64-linux-gnu/libpthread-2.24.so
7f549ca31000-7f549ca32000 r--p 00018000 08:06 786501
/lib/x86_64-linux-gnu/libpthread-2.24.so
7f549ca32000-7f549ca33000 rw-p 00019000 08:06 786501
/lib/x86_64-linux-gnu/libpthread-2.24.so
7f549ca33000-7f549ca37000 rw-p 00000000 00:00 0
7f549ca37000-7f549caa9000 r-xp 00000000 08:06 786969
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
7f549caa9000-7f549cca8000 ---p 00072000 08:06 786969
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
7f549cca8000-7f549cca9000 r--p 00071000 08:06 786969
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
7f549cca9000-7f549ccaa000 rw-p 00072000 08:06 786969
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
7f549ccaa000-7f549ce66000 r-xp 00000000 08:06 786486
/lib/x86_64-linux-gnu/libc-2.24.so
7f549ce66000-7f549d065000 ---p 001bc000 08:06 786486
/lib/x86_64-linux-gnu/libc-2.24.so
7f549d065000-7f549d069000 r--p 001bb000 08:06 786486
/lib/x86_64-linu...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.