nautilus crashed with SIGSEGV in nautilus_window_slot_get_window()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
I clicked the red X when the image preview was created.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.4-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 1 12:42:57 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x4861c5: mov 0x30(%rax),%rax
PC (0x004861c5) ok
source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
#0 0x00000000004861c5 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fffe66c0d78
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 13 (LWP 4553):
#0 0x00007f7bbd9ca03b in ?? ()
No symbol table info available.
.
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-01-27 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
summary: |
- nautilus crashed with SIGSEGV + nautilus crashed with SIGSEGV innautilus_window_slot_get_window() |
summary: |
- nautilus crashed with SIGSEGV innautilus_window_slot_get_window() + nautilus crashed with SIGSEGV in nautilus_window_slot_get_window() |
Changed in nautilus (Ubuntu): | |
status: | New → Confirmed |
status: | Confirmed → New |
Thank you for your bug report, what did you click on exactly?