Canonical and Adobe collaboration project

nautilus crashed with SIGSEGV

Reported by BlueT - Matthew Lien - 練喆明 on 2012-03-27
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
adobe-isv
Undecided
Unassigned
nautilus (Ubuntu)
Undecided
Unassigned

Bug Description

Re-Produce:

1. Install adobeair from https://launchpad.net/~dajhorn/+archive/adobeair
2. Download the AIR Presentation file http://goo.gl/jZCSE from https://groups.google.com/d/msg/cloudtw/JYUEA3ckiNs/Za2YR83XVc8J
3. Install tts.air and launch
4. After the long buzz the screen showup, BUT whole desktop got frozen
5. try to kill the AIR Update process and .air application from Ctrl-Alt-F1 console BUT nothing help
6. only restart X Window can bring my desktop back.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1.2
ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23
Uname: Linux 2.6.32-40-generic x86_64
Architecture: amd64
Date: Tue Mar 27 19:57:07 2012
Disassembly: => 0x7f274e4fa91b: Cannot access memory at address 0x7f274e4fa91b
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=zh_TW:en_US:en
 PATH=(custom, user)
 LANG=zh_TW.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f274e4fa91b: Cannot access memory at address 0x7f274e4fa91b
 PC (0x7f274e4fa91b) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x00007f274e4fa91b in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers

Stacktrace:
 #0 0x00007f274e4fa91b in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

Changed in nautilus (Ubuntu):
status: New → Invalid

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for udisks: package version 1.0.1-1ubuntu1 dbgsym version 1.0.1-1build1
package gcc-4.5-base does not exist, ignoring
libssl0.9.8 version 0.9.8o-5ubuntu1 required, but 0.9.8k-7ubuntu8.8 is available
libstdc++6 version 4.5.2-8ubuntu4 required, but 4.4.3-4ubuntu5.1 is available
outdated debug symbol package for libstdc++6: package version 4.4.3-4ubuntu5.1 dbgsym version 4.4.3-4ubuntu5
gvfs version 1.6.2-1ubuntu1~ppa1 required, but 1.6.1-0ubuntu1build1 is available
package multiarch-support does not exist, ignoring
package python-gobject-2 does not exist, ignoring

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
visibility: private → public

Is this still an issue for you?

If yes please update your system and set back the status to "new"

thanks

Changed in adobe-isv:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers