nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #618607 reported by jdstrydom
278
This bug affects 65 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: nautilus

was copying files from local hard disk to external usb drive when crash occured

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.6-0ubuntu3.1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Aug 16 12:49:33 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100810)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x49f226: mov 0x18(%rdi),%r12
 PC (0x0049f226) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
jdstrydom (jdstrydom) wrote :

as yet still unable to duplicate; will upload as soon as it happens again.

thanks

Revision history for this message
Nikita (namenick87) wrote :

it crashed when I open thrash where was some archives(7z, rar) with names in wrong encoding(cp1251). I click on thrash icon and instead to show me list of files it wait for some time(about 30 seconds) and crashs.

Revision history for this message
Andrea Caminiti (nrayever) wrote :

Nautilus crashed when i unmounted a usb memory stick. i'm using 10.10 amd64. Hope this gets solved soon.

Revision history for this message
John M (jwmwalrus) wrote :

Nautilus is having trouble with some of my CDs.

Some of them are shown as "Blank CD-R Disc", and even though they're not blank. Nautilus only shows no contents, only the CD/DVD Creator message with the Write to Disc button. When I mount those CDs using Disk Utility (palimpsest), I can access their contents through one of the two "Blank CD-R Disc" entries on the Places panel.

Some other CDs are not shown as blank, but those are the ones that cause the crash when I try to access them.

On the same computer, I checked the same CDs under Red Hat (EL5.5), and they're mounted just fine, so it's not a hardware problem.

$ lsb_release -rd && uname -srvmo && apt-cache policy nautilus
Description: Ubuntu maverick (development branch)
Release: 10.10
Linux 2.6.35-19-generic #28-Ubuntu SMP Sun Aug 29 06:34:38 UTC 2010 x86_64 GNU/Linux
nautilus:
  Installed: 1:2.31.90-0ubuntu3
  Candidate: 1:2.31.90-0ubuntu3
  Version table:
 *** 1:2.31.90-0ubuntu3 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Erik B. Andersen (azendale) wrote :

@jdstrydom:
Did this happen after you unmounted or ejected something, like the USB stick? I had a very similar to this bug error happen when I unmounted a internal hard drive partition.

Revision history for this message
jdstrydom (jdstrydom) wrote :

Hi Erik,

the ext disk was already mounted, but dismounted itself while copying and then the crash occurred.

-----Original Message-----
From: "Erik B. Andersen"
Sent: 05/09/2010, 02:43
To: <email address hidden>
Subject: [Bug 618607] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

@jdstrydom:
Did this happen after you unmounted or ejected something, like the USB stick? I had a very similar to this bug error happen when I unmounted a internal hard drive partition.

--
nautilus crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/618607
You received this bug notification because you are a direct subscriber
of the bug.

Status in “nautilus” package in Ubuntu: Incomplete

Bug description:
Binary package hint: nautilus

was copying files from local hard disk to external usb drive when crash occured

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.6-0ubuntu3.1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Aug 16 12:49:33 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100810)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x49f226: mov 0x18(%rdi),%r12
 PC (0x0049f226) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/618607/+subscribe

Revision history for this message
Erik B. Andersen (azendale) wrote :

Ok, I think it is the same bug as what I had. It seems to happen when you unmount/eject something. I'm attaching a valgrind log, and I also have a backtrace that I'll attach.
@Nikita Did you open the archives with the archive mounter and then unmount them, and then unmount them?

Revision history for this message
Erik B. Andersen (azendale) wrote :
Revision history for this message
Erik B. Andersen (azendale) wrote :
Revision history for this message
Erik B. Andersen (azendale) wrote :
Revision history for this message
Nikita (namenick87) wrote :

no, I open them with file-roller

Revision history for this message
Erik B. Andersen (azendale) wrote :

Well, I'm going to set this bug to confirmed--hopefully the information I provided was enough.
@Nikita
I went back and re read the comments. I originally skimmed over your comment and thought you were saying that the problem was when you had the archives open. But now I get what you were saying. You might have a different bug, especially if it only happens with names with the wrong encoding.
(I also reread my comment, "Did you open the archives with the archive mounter and then unmount them, and then unmount them?" I must have been tired. I only meant unmounting them once :)

Changed in nautilus (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Nikita (namenick87) wrote :

I try to mount archive(with name in wrong encoding) and it's crash after 1 second after mounting. Apport can't take info about this crash, but I think it's same problem you talking about.

Revision history for this message
bobrownik (tolive-is-todie) wrote :

this happened to me after i unmounted a ntfs drive(sata), while a new drive was coming online, also ntfs but in a usb enclosure

Revision history for this message
Andy Branscomb (droolingsheep) wrote :

This happens to me when I unmount a DVD. An ext4 drive is also mounted via usb.

Revision history for this message
Tim Penhey (thumper) wrote :

I got this trying to unmount a normal FAT USB key using the eject icon next to the USB key image in the left hand side panel.

Revision history for this message
Patrick le Roux (pleroux-gmail) wrote :

I got this crash whilst trying to unmount a USB drive.

Revision history for this message
LSL (spesialstyrker) wrote :

Unmounting a drive causes this crash for me as well.

Revision history for this message
Kim d'Audretsch (kimda) wrote :

Mine also crashed after moving a whole lot of files from my home folder to another partition.

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.