zenity crashed with SIGSEGV in g_cclosure_marshal_VOID()

Bug #981731 reported by Florin Broasca
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zenity (Ubuntu)
New
Undecided
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: zenity 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Sat Apr 14 01:05:34 2012
ExecutablePath: /usr/bin/zenity
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120322)
ProcCmdline: zenity --list --radiolist --title Failsafe-X --width 600 --height 300 --text What\ would\ you\ like\ to\ do? --column --column Choice --column TRUE LOW_RES_MODE Run\ in\ low-graphics\ mode\ for\ just\ one\ session FALSE RECONFIGURE Reconfigure\ graphics FALSE TROUBLESHOOT Troubleshoot\ the\ error FALSE EXIT_TO_CONSOLE Exit\ to\ console\ login --hide-column 2
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x40e33d: testb $0x8,0x5e(%rdi)
 PC (0x0040e33d) ok
 source "$0x8" ok
 destination "0x5e(%rdi)" (0x0000005e) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: zenity
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID(int0_t, void) () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: zenity crashed with SIGSEGV in g_cclosure_marshal_VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Florin Broasca (florin.broasca) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #969031, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.