nautilus crashed with SIGABRT in g_assertion_message()

Bug #1795136 reported by corrado venturini
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Entered some characters on nautilus window to search. works on 'Home' window, does not work on 'Computer' window

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 29 15:12:50 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+721+205'"
InstallationDate: Installed on 2018-09-27 (2 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
ProcCmdline: /usr/bin/nautilus --gapplication-service
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 is_recursive_search ()
 ?? ()
Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

Revision history for this message
corrado venturini (corradoventu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x563211839100 <__func__.70025> "nautilus_file_new_from_filename", message=<optimized out>) at ../../../../glib/gtestutils.c:2596
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x563211836830 "../src/nautilus-file.c", line=line@entry=594, func=func@entry=0x563211839100 <__func__.70025> "nautilus_file_new_from_filename", expr=expr@entry=0x563211832a60 "NAUTILUS_IS_DIRECTORY (directory)") at ../../../../glib/gtestutils.c:2619
 nautilus_file_new_from_filename (self_owned=<optimized out>, filename=0x7f168c031b90 "os-probes", directory=<optimized out>) at ../src/nautilus-file.c:594
 nautilus_file_get_internal (location=location@entry=0x7f16d015ac20, create=create@entry=1) at ../src/nautilus-file.c:775
 nautilus_file_get (location=location@entry=0x7f16d015ac20) at ../src/nautilus-file.c:796

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
summary: - nautilus crashed with SIGABRT in g_assertion_message_expr()
+ nautilus crashed with SIGABRT in g_assertion_message()
tags: removed: need-amd64-retrace
information type: Private → Public
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
Jeremy Bícha (jbicha) wrote :

In my brief testing, this appears to be fixed by the same fix for LP: #1795028 so I'm marking it a duplicate of that bug. I've added a Test Case there that resembles this bug's description.

The fix needs to be manually approved by the Ubuntu Release Team since the archive is partially frozen in preparation for Ubuntu 18.10's release soon.

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.