nautilus crashed with SIGSEGV in gtk_icon_info_get_attach_points()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned | ||
nautilus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
was working in firefox with Synaptic running on a seperate screen when crash occurred.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.8.1-
ProcVersionSign
Uname: Linux 3.8.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
CrashCounter: 1
Date: Wed Jun 12 22:30:10 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
b'org.
InstallationDate: Installed on 2013-06-10 (3 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f996d4503c2 <gtk_icon_
PC (0x7f996d4503c2) ok
source "0x4(%rsi)" (0x3f00000004) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
gtk_icon_
?? ()
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in gtk_icon_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Status changed to 'Confirmed' because the bug affects multiple users.