nautilus crashed with SIGSEGV in mainloop_proxy_func()

Bug #944624 reported by John Belton
574
This bug affects 68 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Fix Released
High
Chris Coulson
Precise
Fix Released
High
Chris Coulson

Bug Description

This occured when coping a file from documents to UbuntuOne after upgradeing ubuntu 12.04 Beta this morning. One upgrade was to Nautilus, the copy seems to have completed (I'll know when I check my other computer later).
John

TEST CASE:
1. Launch nautilus
2. Select a file
3. Copy/Paste the file; CTRL+C/CTRL+V

ACTUAL RESULT:
This crash

EXPECTED RESULT
The file is copied without a crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Fri Mar 2 08:10:59 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+53+188'
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3290fa43bf: mov %eax,0x8(%rbx)
 PC (0x7f3290fa43bf) ok
 source "%eax" ok
 destination "0x8(%rbx)" (0x7f3200000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2012-03-01 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
John Belton (jbelton1950) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mainloop_proxy_func (data=0x7f3200000000) at /build/buildd/glib2.0-2.31.18/./gio/gioscheduler.c:286
 g_main_dispatch (context=0x2009de0) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:2510
 g_main_context_dispatch (context=0x2009de0) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:3047
 g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x2009de0, self=<optimized out>) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:3118
 g_main_context_iterate (context=0x2009de0, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:3055

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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_main_context_dispatch()
+ nautilus crashed with SIGSEGV in mainloop_proxy_func()
tags: removed: need-amd64-retrace
Revision history for this message
John Belton (jbelton1950) wrote :

Just to confirm, it did transfer OK.
John

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
visibility: private → public
Changed in nautilus (Ubuntu):
importance: Medium → High
Changed in nautilus (Ubuntu Precise):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
tags: added: qa-manual-testing rls-mgr-p-tracking
description: updated
tags: added: bugpattern-needed
Revision history for this message
Martin Pitt (pitti) wrote :

I copied a few files using Ctrl-C/Ctrl-V into my Ubuntu One folder on today's precise, and it's working fine. Can you reliably reproduce this every time? Which kind of file are you copying? (document type, size, etc.)

Revision history for this message
Franck (alci) wrote :

I would tend to say it happens whenever you try to copy from one device to another.

This happened here at least in these cases :
- from a smb share to local desktop
- from usb key to local desktop

Revision history for this message
Franck (alci) wrote :

Tested the other way around :

- from local folder (~/Images) to smb share
- from local folder to usb key

This triggers the bug each time here.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

It occurs with any type of file and without copying to ubuntu one.

Revision history for this message
Vladislav (9-b) wrote :

Yes, even in the same folder.

Revision history for this message
Tayroni Alves (tayroni-alves) wrote :

This bug applies for me too.

Even on copying files on some place on home folder nautilus crashes

Revision history for this message
digio.space (digiospace) wrote :

Me too. Crashes on any copy and paste, any type of file from/to any location

Revision history for this message
digio.space (digiospace) wrote :

--a little more info: Nautilus does not close until all of the files are done copying. So if I past several files, I can watch the progress bar until complete and then crash.

Moving something to the trash does not crash. Adding files from a different source, such as saving from FIrefox to a folder does not crash nautilus.

Hope that helps

Revision history for this message
Tayroni Alves (tayroni-alves) wrote :

Result of sudo tail /var/log/syslog

Mar 2 21:37:12 copernico nautilus: [N-A] Nautilus-Actions Tracker 3.1.4 initializing...
Mar 2 21:37:12 copernico nautilus: [N-A] Nautilus-Actions Menu Extender 3.1.4 initializing...
Mar 2 21:37:22 copernico kernel: [ 1737.322836] nautilus[4727]: segfault at 7f2300000008 ip 00007f23513723bf sp 00007fffb2fd5160 error 6 in libgio-2.0.so.0.3118.0[7f2351313000+155000]

Revision history for this message
zzecool (zzecool) wrote :

When ever you try to copy something to the desktop folder will also trigger the bug.

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

Thank you for your bug report, I can't confirm that here, could somebody having the issue:
- install nautilus-dbg (and maybe the glib and gtk dbg as well)
- run "nautilus --quit"
- run "G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log nautilus"

trigger the issue

add valgrind.log to the bug report

Revision history for this message
Tayroni Alves (tayroni-alves) wrote : Re: [Bug 944624] Re: nautilus crashed with SIGSEGV in mainloop_proxy_func()
  • valgrind.log Edit (736.6 KiB, text/x-log; charset=US-ASCII; name="valgrind.log")

On Sat, Mar 3, 2012 at 8:20 AM, Sebastien Bacher <email address hidden> wrote:

> Thank you for your bug report, I can't confirm that here, could somebody
> having the issue:
> - install nautilus-dbg (and maybe the glib and gtk dbg as well)
> - run "nautilus --quit"
> - run "G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
> --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
> nautilus"
>
> trigger the issue
>
> add valgrind.log to the bug report
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/944624
>
> Title:
> nautilus crashed with SIGSEGV in mainloop_proxy_func()
>
> Status in “nautilus” package in Ubuntu:
> Confirmed
> Status in “nautilus” source package in Precise:
> Confirmed
>
> Bug description:
> This occured when coping a file from documents to UbuntuOne after
> upgradeing ubuntu 12.04 Beta this morning. One upgrade was to Nautilus, the
> copy seems to have completed (I'll know when I check my other computer
> later).
> John
>
> TEST CASE:
> 1. Launch nautilus
> 2. Select a file
> 3. Copy/Paste the file; CTRL+C/CTRL+V
>
> ACTUAL RESULT:
> This crash
>
> EXPECTED RESULT
> The file is copied without a crash
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: nautilus 1:3.3.90-0ubuntu4
> ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
> Uname: Linux 3.2.0-17-generic x86_64
> ApportVersion: 1.93-0ubuntu2
> Architecture: amd64
> Date: Fri Mar 2 08:10:59 2012
> ExecutablePath: /usr/bin/nautilus
> GsettingsChanges: org.gnome.nautilus.window-state geometry
> '800x550+53+188'
> ProcCmdline: nautilus -n
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7f3290fa43bf: mov %eax,0x8(%rbx)
> PC (0x7f3290fa43bf) ok
> source "%eax" ok
> destination "0x8(%rbx)" (0x7f3200000008) not located in a known VMA
> region (needed writable region)!
> SegvReason: writing unknown VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
> UpgradeStatus: Upgraded to precise on 2012-03-01 (0 days ago)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/944624/+subscriptions
>

--
"Só se conseguirá a paz na ponta da lança".

Santa Joana D'Arc

Revision history for this message
Tayroni Alves (tayroni-alves) wrote :

File valgrind.log added.

Revision history for this message
Tayroni Alves (tayroni-alves) wrote :

I executed the same command again and trigger the issue.

File valgrind-2.log added.

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

Thanks, the logs don't have a lot of infos over the stacktrace though :-(

Could you try to reinstall the debs from the previous version:
https://launchpad.net/ubuntu/+source/nautilus/1:3.3.90-0ubuntu3/+build/3252050
or
https://launchpad.net/ubuntu/+source/nautilus/1:3.3.90-0ubuntu2/+build/3231502 (the previous one)

(should be basically downloading the lib and nautilus debs and dpkg -i those)

then restart nautilus (nautilus --quit; nautilus) and see if that's still an issue?

The duplicates here are all on amd64, I wonder if thats 64bits specific

The valgrind log also has quite some dbusmenu errors (set image) but that lib didn't change recently...

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

Comment #15 is interesting as well, is everyone here using nautilus-action?

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

@seb128: I am not using nautilus-actions, and seeing this crash too. 1:3.3.90-0ubuntu2 and 1:3.3.90-0ubuntu3 are working fine.

Revision history for this message
Tayroni Alves (tayroni-alves) wrote :

I tested the packages of 3.3.90-0ubuntu2 version and there is no issue
on copy and paste, even on removable devices.

That's a regression on version 3.3.90-0ubuntu4. On upgrading issue
comes back again.

Revision history for this message
Tayroni Alves (tayroni-alves) wrote :

There is no issue on copy and paste on the 3.3.90-0ubuntu3 version too.

It's likely a regression.

Martin Pitt (pitti)
Changed in nautilus (Ubuntu Precise):
assignee: Canonical Desktop Team (canonical-desktop-team) → Sebastien Bacher (seb128)
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This crashes for me on every file operation. It's introduced by the zeitgeist patch, but I'm not entirely sure why just yet

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Ok, I've disabled the zeitgeist patch for now. I don't really want to figure out what's going on on a Saturday evening :)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nautilus - 1:3.3.90-0ubuntu5

---------------
nautilus (1:3.3.90-0ubuntu5) precise; urgency=low

  * Disable the zeitgeist logging patch until we figure out why it causes
    nautilus to crash (LP: #944624)
    - update debian/patches/series
 -- Chris Coulson <email address hidden> Sat, 03 Mar 2012 20:09:45 +0000

Changed in nautilus (Ubuntu Precise):
status: Confirmed → Fix Released
Changed in nautilus (Ubuntu Precise):
status: Fix Released → Triaged
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is caused by stack corruption because the extra code in copy_job_done is sticking a pointer in to an int (which is why it works on 32-bit but not on 64-bit)

Changed in nautilus (Ubuntu Precise):
assignee: Sebastien Bacher (seb128) → Chris Coulson (chrisccoulson)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nautilus - 1:3.3.90-0ubuntu6

---------------
nautilus (1:3.3.90-0ubuntu6) precise; urgency=low

  * Fix LP: #944624 - Don't stick a pointer to an int, as it causes stack
    corruption on 64-bit architectures
    - update debian/patches/zg_activity_logging.patch
  * Turn on the zeitgeist logging patch again
    - update debian/patches/series
 -- Chris Coulson <email address hidden> Sat, 03 Mar 2012 23:53:38 +0000

Changed in nautilus (Ubuntu Precise):
status: Triaged → Fix Released
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/946431

tags: added: iso-testing
Revision history for this message
Diogo Costa (dmoraiscosta) wrote :

Hello everyone

This bug just ocurred with me. I have no idea how to fix it. Since I updated Ubuntu to 12.04 version, my netbook (asus eee pc 1005 HA) crashes constantly and randomly (sometimes when I am on the Internet or when I'm doing something on Libreoffice). As you might understand I'm being tired of this situation as I don't have a clue about this crash.

I would like to ask you if you have know how to fix this.

Thank you

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.