Ubuntu
zenity package

zenity crashed with SIGSEGV in g_closure_invoke()

Bug #649861 reported by dokuro
184
This bug affects 41 people
Affects Status Importance Assigned to Milestone
zenity (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: zenity

after ubuntu started, i saw the crash icon and I submitted the bug...

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: zenity 2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Sep 28 09:40:43 2010
ExecutablePath: /usr/bin/zenity
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcCmdline: zenity --warning --text <big><b>Ubuntu\ está\ funcionando\ en\ un\ modo\ gráfico\ de\ baja\ resolución</b></big>\\n\\nNo\ se\ han\ podido\ detectar\ correctamente\ su\ monitor,\\nsu\ tarjeta\ gráfica\ o\ su\ dispositivo\ de\ entrada.\ Tendrá\ que\ configurarlos\ usted\ mismo.
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
SegvAnalysis:
 Segfault happened at: 0xf05474 <g_closure_invoke+340>: mov (%eax),%ecx
 PC (0x00f05474) ok
 source "(%eax)" (0x0001fff8) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: zenity
StacktraceTop:
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
 gdk_display_open () from /usr/lib/libgdk-x11-2.0.so.0
Title: zenity crashed with SIGSEGV in g_closure_invoke()
UserGroups:

Revision history for this message
dokuro (dario-soto) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_error_get_type () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_handlers_unblock_matched ()
 g_signal_handler_find () from /usr/lib/libgobject-2.0.so.0
 gdk_window_get_composite_drawable (drawable=0x0,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in zenity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Pedro Villavicencio (pedro)
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in zenity (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in zenity (Ubuntu):
status: Incomplete → Invalid
Crashogre (john-finkphoto)
Changed in zenity (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in zenity (Ubuntu):
status: New → Confirmed
Revision history for this message
Steffen Goetz (steffengoetz) wrote :

I'm on
Description: Ubuntu precise (development branch)
Release: 12.04
Codename: precise
current updates from April 10th 2012

In the terminal try this command:

zenity --list --radiolist --column "check" --column "option" TRUE "1" FALSE "2"

After choosing an option in the radio list zenity produces a Segmentation fault (core dumped)

Hope this helps to reproduce the bug.

Revision history for this message
maccus (maccus) wrote :

I'm on Debian wheezy (from which Precise is derived). After upgrading to Zenity 3.4.0 I got the segfault as well. After downgrading to zenity 3.2.0 everything works OK.

Revision history for this message
Steffen K. (sk-gobuki) wrote :

I'm on Ubuntu 12.04 and played around with zenity.

i ran "zenity --list foo bar --text dialogtext --column=foocol --column barcol" when it happened.
It opens and i can select entries, but it segfaults every time when i click cancel, ok or the close button.

syslog shows this:
kernel: [ 5108.760429] zenity[29367]: segfault at 5e ip 000000000040e33d sp 00007fffcbdd0680 error 4 in zenity[400000+15000]

Revision history for this message
agenkin (agenkin-p) wrote :

This bug in zenity affects other packages that use it to ask user a question. In our case, the freenx server is affected - users are unable to save their NX sessions because of this bug.

Revision history for this message
tekstr1der (tekstr1der) wrote :

Seeing this crash on daily build of 12.04 Precise Pangolin when closing Input Method Switcher.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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