glade2script random crash at startup

Bug #1104461 reported by Rik
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
glade2script
Expired
Undecided
Unassigned

Bug Description

This happens after startup, when loading.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: glade2script 3.2.2~ppa45~precise [origin: LP-PPA-yannubuntu-boot-repair]
ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35
Uname: Linux 3.2.0-36-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
Blkid:
 /dev/sda1: LABEL="OSDisk" UUID="DC68A45668A430E6" TYPE="ntfs"
 /dev/sda2: LABEL="Recovery" UUID="3C08A57108A52ABA" TYPE="ntfs"
 /dev/sda5: UUID="7d9adec5-0005-47cd-92e9-9d622e4a3871" TYPE="ext4"
 /dev/sda6: UUID="853c87d1-4b3c-4680-92ee-fd17442c0f21" TYPE="swap"
ComputerArchi: CPU op-mode(s): 32-bit, 64-bit
CrashCounter: 1
CrashDB: glade2script
Date: Wed Jan 23 21:52:08 2013
ExecutablePath: /usr/bin/glade2script
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
InterpreterPath: /usr/bin/python2.7
LsbRelease: Ubuntu 12.04.1 LTS
MarkForUpload: True
OsProber: /dev/sda1:Windows Vista (loader):Windows:chain
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
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb653645b <gdk_window_get_frame_extents+11>: mov 0xc(%eax),%edx
 PC (0xb653645b) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Session: not-live
Signal: 11
SourcePackage: glade2script
StacktraceTop:
 gdk_window_get_frame_extents () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 atk_component_get_extents () from /usr/lib/i386-linux-gnu/libatk-1.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/gtk-3.0/modules/libatk-bridge.so
 ?? () from /usr/lib/i386-linux-gnu/gtk-3.0/modules/libatk-bridge.so
ThirdParty: True
Title: glade2script crashed with SIGSEGV in gdk_window_get_frame_extents()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Rik (rufn) wrote :
YannUbuntu (yannubuntu)
information type: Private → Public
Revision history for this message
YannUbuntu (yannubuntu) wrote :

Thank you Rick for your report.

1) Do you get this crash window systematically each time you start Boot-Repair ?

2) After you get this crash, does the Boot-Repair main window appear ? if yes, please click the "Create BootInfo" button and indicate the URL that will appear.

Revision history for this message
Rik (rufn) wrote :

Sorry it took so long to respond. I'm new to bug reporting.
I ran the program again from the dash and had no problem.
but when I run it from a terminal <sudo boot-repair> it returns asking me to file a bug report.
the Boot-Repair main window does not appear after the bug reporting.
the times I have been able to run Boot-Repair I have the "Create BootInfo" "http://paste.ubuntu.com" I have 3 of them.
In addition I get the following information from the terminal.
Please see the attached text file. "glade2script_Bug #1104461.txt".
I hope this helps, I will monitor the bug and respond to any questions you may have. Thank you for your help.
Rk

Revision history for this message
YannUbuntu (yannubuntu) wrote :

Thanks Rik.

Please could you run :
1) 'sudo boot-repair' from a terminal
2) 'boot-repair' from a terminal
3) 'gksudo boot-repair' from a terminal
4) 'sudo boot-repair -d' from a terminal
5) Boot-Repair from the Dash

and tell me which bugs, and which launch Boot-Repair successfully ?

Please redo 1) then 2) , 3), 4) and 5) several times in order to double-check.

Revision history for this message
Rik (rufn) wrote :

I closed and opened a terminal each time I did a command
1) 'sudo boot-repair' from a terminal (Returned error each of 2 runs)
 2) 'boot-repair' from a terminal (Returned an error 1st time but worked 2nd time)
 3) 'gksudo boot-repair' from a terminal (Boot-Repair successful 2times Did not return error)
 4) 'sudo boot-repair -d' from a terminal returned error see attached txt files. http://paste.ubuntu.com/1571507/
 5) Boot-Repair from the Dash no error

I then tried all 5 commands again for a (3rd) and (4th) time and all worked fine!
I hope this all helps
Rik

Revision history for this message
YannUbuntu (yannubuntu) wrote :

Thanks Rik.
The crash is not systematic, so it will be hard to solve...

@Ansuz, any idea?

Revision history for this message
Rik (rufn) wrote :

Thanks again Yan,
I have no idea what happened but if I get any additional information I will share it with you.

YannUbuntu (yannubuntu)
summary: - glade2script crashed with SIGSEGV in gdk_window_get_frame_extents()
+ glade2script random crash at startup
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.