glade2script crashed with SIGSEGV in gtk_style_context_get_valist()

Bug #1319345 reported by MA Hayat
38
This bug affects 7 people
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-yannubuntu-boot-repair]
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
Blkid:
 /dev/dm-0: UUID="65fb5469-03e1-49d3-a566-b740709cdf9b" TYPE="ext4"
 /dev/sda1: UUID="5b6f8728-6883-4850-8d72-8898240f7086" TYPE="ext2"
 /dev/sda5: UUID="SPT1Pj-HQX0-gEsU-XXtc-qJYz-36Px-1xWHNM" TYPE="LVM2_member"
 /dev/mapper/it--vg-swap_1: UUID="130e5768-169a-4a84-a778-544196873ffd" TYPE="swap"
 /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/glade2script
InstallationDate: Installed on 2014-01-05 (128 days ago)
InstallationMedia: It
InterpreterPath: /usr/bin/python2.7
LsbRelease: Ubuntu 14.04 LTS
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/glade2script -g ./boot-sav.glade -s ./boot-repair.sh --combobox=@@_combobox_format_partition@@col --combobox=@@_combobox_bootflag@@col --combobox=@@_combobox_ostoboot_bydefault@@col --combobox=@@_combobox_purge_grub@@col --combobox=@@_combobox_separateboot@@col --combobox=@@_combobox_efi@@col --combobox=@@_combobox_sepusr@@col --combobox=@@_combobox_place_grub@@col --combobox=@@_combobox_add_kernel_option@@col --combobox=@@_combobox_restore_mbrof@@col --combobox=@@_combobox_partition_booted_bymbr@@col
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/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_style_context_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_style_context_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_style_context_get_border () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
ThirdParty: True
Title: glade2script crashed with SIGSEGV in gtk_style_context_get_valist()
UpgradeStatus: Upgraded to trusty on 2014-04-18 (25 days ago)
UserGroups:

Revision history for this message
MA Hayat (mahayat-51) wrote :
Revision history for this message
YannUbuntu (yannubuntu) wrote :

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?

information type: Private Security → Public
Changed in glade2script:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for glade2script because there has been no activity for 60 days.]

Changed in glade2script:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.