glade2script crashed with SIGSEGV in gtk_render_icon_pixbuf()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glade2script |
Expired
|
Undecided
|
Unassigned |
Bug Description
Failed to start Ubuntu GNOME 13.10
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: glade2script 3.2.2~ppa47~saucy [origin: LP-PPA-
ProcVersionSign
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
ComputerArchi: CPU op-mode(s): 32-bit, 64-bit
CrashDB: glade2script
Date: Thu Oct 10 18:15:06 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-10-10 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
InterpreterPath: /usr/bin/python2.7
LsbRelease: Ubuntu Saucy Salamander (development branch)
MarkForUpload: True
OsProber: /dev/sda2@
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f20d1fcd1f7: cmp %rax,(%rdi)
PC (0x7f20d1fcd1f7) ok
source "%rax" ok
destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Session: not-live
Signal: 11
SourcePackage: glade2script
StacktraceTop:
?? () from /usr/lib/
gtk_render_
gtk_icon_
?? () from /usr/lib/
?? () from /usr/lib/
ThirdParty: True
Title: glade2script crashed with SIGSEGV in gtk_render_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
Thank you for the report.
Does the crash occur every time you try to launch Boot-Repair ?
When the crash occurs, does the Boot-Repair menu (with the "Recommended Repair" button) appear anyway?