nautilus crashed with SIGSEGV in g_object_unref() when opening unexisting folder

Bug #1216625 reported by Lockal
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

nautilus crashes when opening unexisting folders. For example, type "nautilus /test" in console and you will see an empty messagebox-sized window and then nautilus will crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: sep3_10 pax nvidia
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Sun Aug 25 21:31:54 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'927x1027+65+24'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'231'
InstallationDate: Installed on 2012-02-05 (567 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
MarkForUpload: True
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f42f0c37bcc <g_object_unref+92>: scas %es:(%rdi),%al
 PC (0x7f42f0c37bcc) ok
 source "%es:(%rdi)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_unref (_object=0xaaaaaaaaaaaaaaaa) at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c:3099
 ?? ()
 run_in_thread (job=<optimized out>, c=<optimized out>, _data=0x451240) at /build/buildd/glib2.0-2.37.6/./gio/gsimpleasyncresult.c:879
 g_simple_async_result_complete (simple=0x7f42a0004870) at /build/buildd/glib2.0-2.37.6/./gio/gsimpleasyncresult.c:762
 ?? ()
Title: nautilus crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to saucy on 2013-05-19 (98 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Lockal (lockal) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_object_unref (_object=0xaaaaaaaaaaaaaaaa) at /build/buildd/glib2.0-2.37.6/./gobject/gobject.c:3099
 hostname_proxy_new_cb (source_object=<optimized out>, res=<optimized out>, user_data=0x160c9b0) at nautilus-places-sidebar.c:3264
 run_in_thread (job=<optimized out>, c=<optimized out>, _data=0x451240 <hostname_proxy_new_cb>) at /build/buildd/glib2.0-2.37.6/./gio/gsimpleasyncresult.c:879
 g_simple_async_result_complete (simple=0x7f42a0004870) at /build/buildd/glib2.0-2.37.6/./gio/gsimpleasyncresult.c:762
 ?? ()

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 :

The bug is quite old and the code changed since, also there has been no new report of that specific problem nor activity for some years so assuming it has been resolved and closing the ticket. If you still get issues in newer versions feel free to open a new report though.

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
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.