glade2script crashed with SIGSEGV in gtk_style_context_get_valist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glade2script |
Expired
|
Undecided
|
Unassigned |
Bug Description
After upgrade from 13.10 to ubuntu 14.04, the system was found quite effecient. Then some files of certain directories were deleted just to clean the extra mplogs and tmp files. The next time upon boot, the system did no go beyand login screen whic kept on looping until today. I have done many tricks/updates etc through internet as a guest user since it booted as guest session. Today I tried got to the /dev/boot/ directory and updated grub and then upon booting it did not looped on loging screen and thats it I am reporting this issue.
Thanks!
With Best wishes for all of u!
MA Hayat
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: glade2script 3.2.2~ppa47~saucy [origin: LP-PPA-
ProcVersionSign
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
Blkid:
/dev/dm-0: UUID="65fb5469-
/dev/sda1: UUID="5b6f8728-
/dev/sda5: UUID="SPT1Pj-
/dev/mapper/
/dev/sdb1: LABEL="MULTIBOOT" UUID="0F0B-0C2E" TYPE="vfat"
ComputerArchi: CPU op-mode(s): 32-bit, 64-bit
CrashDB: glade2script
Date: Tue May 13 23:33:35 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-01-05 (128 days ago)
InstallationMedia: It
InterpreterPath: /usr/bin/python2.7
LsbRelease: Ubuntu 14.04 LTS
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f457e67d657: cmp %rax,(%rdi)
PC (0x7f457e67d657) 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/
?? () from /usr/lib/
gtk_style_
gtk_style_
gtk_style_
ThirdParty: True
Title: glade2script crashed with SIGSEGV in gtk_style_
UpgradeStatus: Upgraded to trusty on 2014-04-18 (25 days ago)
UserGroups:
hello
When did the "glade2script crash" window appear?
just after you ran Boot-Repair? after the loading window of Boot-Repair appeared? after the main window (the one with the big logo) of Boot-Repair appeared?