nautilus crashed with SIGSEGV in build_file_list_from_uris()

Bug #1283426 reported by Tomás Manzano Galán
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Medium
gtk+3.0 (Ubuntu)
Fix Released
High
Unassigned
Wily
Fix Released
High
Unassigned

Bug Description

I was trying to copy a file out of a VMware Player virtual Windows 7 guest runnning in a window to nautilus, drag-and-dropping. The reverse operation (From nautilus to virtual machine's desktop) is executed fine.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 22 13:16:46 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2014-02-15 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f36910aa0b9: mov (%rdi),%rdi
 PC (0x7f36910aa0b9) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

Revision history for this message
Tomás Manzano Galán (tomasmgalan) wrote :
information type: Private → Public
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 : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
summary: - nautilus crashed with SIGSEGV in g_closure_invoke()
+ nautilus crashed with SIGSEGV in build_file_list_from_uris()
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 :

That's easy to trigger by doing a dnd from e.g a file in evolution to the nautilus sidebar, reported upstream to https://bugzilla.gnome.org/show_bug.cgi?id=756303

Changed in nautilus (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → Confirmed
affects: nautilus (Ubuntu) → gtk+3.0 (Ubuntu)
Changed in gtk+3.0 (Ubuntu):
status: Triaged → Fix Committed
Changed in nautilus:
status: Confirmed → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+3.0 - 3.16.7-0ubuntu5

---------------
gtk+3.0 (3.16.7-0ubuntu5) xenial; urgency=medium

  * debian/patches/git_non_uri_dnd_segfault.patch:
    - placessidebar: do not crash if uris is NULL, (lp: #1283426)
  * debian/patches/git_screenshot_hidpi.patch:
    - gdk_pixbuf_get_from_window: honor device scale, that fixes screenshots
      not looking right on hidpi screens, thanks Lars (lp: #1512290)

 -- Sebastien Bacher <email address hidden> Mon, 02 Nov 2015 15:10:07 +0100

Changed in gtk+3.0 (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Tomás, or anyone else affected,

Accepted gtk+3.0 into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.16.7-0ubuntu3.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in gtk+3.0 (Ubuntu Wily):
importance: Undecided → High
status: New → Fix Committed
tags: added: verification-needed
Mathew Hodson (mhodson)
Changed in nautilus:
importance: Medium → Unknown
status: Invalid → Unknown
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Tomás, or anyone else affected,

Accepted gtk+3.0 into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.16.7-0ubuntu3.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

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

resolves the segfault indeed

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+3.0 - 3.16.7-0ubuntu3.3

---------------
gtk+3.0 (3.16.7-0ubuntu3.3) wily; urgency=medium

  * debian/patches/git_screenshot_hidpi.patch:
    - revert that change for now, it creates a regression

gtk+3.0 (3.16.7-0ubuntu3.2) wily; urgency=medium

  * debian/patches/git_non_uri_dnd_segfault.patch:
    - placessidebar: do not crash if uris is NULL, (lp: #1283426)
  * debian/patches/git_screenshot_hidpi.patch:
    - gdk_pixbuf_get_from_window: honor device scale, that fixes screenshots
      not looking right on hidpi screens, thanks Lars

gtk+3.0 (3.16.7-0ubuntu3.1) wily; urgency=medium

  * debian/patches/unity_rbga_tooltips.patch:
    - GtkTooltip: set always an rgba visual when running in Unity (LP: #1508357)

 -- Sebastien Bacher <email address hidden> Tue, 08 Dec 2015 15:32:58 +0100

Changed in gtk+3.0 (Ubuntu Wily):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote : Update Released

The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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