nautilus crashed with SIGSEGV in pango_context_get_base_dir()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ground Control |
Triaged
|
Critical
|
Unassigned | ||
nautilus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
This crash has nothing to do with the default Lucid packages, but is bug #518548, and caused by Ground Control.
It crashed when Ground Control was finalising the downloading of a branch that had been requested with "Fix Bug".
ProblemType: Crash
Architecture: amd64
Date: Mon Feb 8 21:11:01 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelMo
Package: nautilus 1:2.29.2-0ubuntu4
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=
LANG=nl_NL.utf8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7fb58aa82119 <pango_
PC (0x7fb58aa82119) ok
source "0x28(%rdi)" (0xaaaaaaaaaaaa
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
pango_
get_alignment (layout=<value optimized out>,
pango_
gtk_label_
IA__g_
Title: nautilus crashed with SIGSEGV in pango_context_
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev postgres pulse-access sambashare src staff users video www-data
Changed in groundcontrol: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
status: | Confirmed → Triaged |
visibility: | private → public |
Moving back to private since my CoreDump.gz is still attached. Whoops.
I'm afraid we'll have to wait for the retracer to go over this since the Python part of the crash isn't very useful at the moment. However, I'm afraid it won't become much more useful since Ground Control has no debugging symbols and is not available in the default install, which means the retraces can't understand it.