nautilus crashed with SIGSEGV in update_dbus_opened_locations()

Bug #1922290 reported by Manfred Hampl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Immediately after booting and log-in

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: nautilus 1:3.38.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 1 22:25:47 2021
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2021-01-23 (68 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200720)
ProcCmdline: nautilus --version
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f972063b414: mov 0x20(%rdi),%rax
 PC (0x7f972063b414) ok
 source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 update_dbus_opened_locations ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
UpgradeStatus: Upgraded to hirsute on 2021-01-23 (68 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

usr_lib_nautilus:
 evince 3.39.2-1
 file-roller 3.38.0-1
 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
 nautilus-share 0.7.3-2ubuntu3

Revision history for this message
Manfred Hampl (m-hampl) wrote :
Revision history for this message
Manfred Hampl (m-hampl) wrote :

executing the command

nautilus --version

in a terminal window also crashes.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Manfred Hampl (m-hampl) wrote :

For verification I downloaded ubuntu-21.04-beta-desktop-amd64.iso (Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)) started it in VirtualBox ("Try Ubuntu") and also experience a crash for the "nautilus --version" command, see attachment.

Revision history for this message
Manfred Hampl (m-hampl) wrote :

Is this still Bug #1820859 ?

Revision history for this message
Sebastien Bacher (seb128) wrote :

The original description is confusing, it states after login but the recorded command is

 ProcCmdline: nautilus --version

so yes it does sound like bug #1820859

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Manfred Hampl (m-hampl) wrote :

to the "confusing description":

Maybe a misinterpretation on my side. I booted the system, logged in, and immediately received a pop-up informing me of a crash. This might have been caused by the presence of a not-yet-reported crash file from an earlier session, although I cannot remember that I have executed "nautilus --version" earlier.

Only upon seeing the crash report and the bug report that has been created, I executed "nautilus --version" (or maybe executed it again) and with that command I reliably can produce that crash again.

Meanwhile I have downloaded the hirsute-beta-iso from March 31.
Booting it in "Try Ubuntu" mode in VirtualBox also reliably crashed when running "nautilus --version".

Revision history for this message
Sebastien Bacher (seb128) wrote :

right, thanks for the command and indeed the version argument is broken

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.